|
|
|
|
|
by Tarks
1695 days ago
|
|
A lot of young companies are hindered by the pain and overhead of developing and supporting multiple native apps (including patching, tracking & resolving separate bugs etc), spending their precious resources on solved problems rather than user-centric things like better understanding the users by rapidly improving the app and getting feedback etc. Picture a maybe-for-legal-reasons-theoretical app that needs to be supported on android and iOS plus would massively benefit from the ability to preview the mobile app in a supporting Web portal. PWA gives us : - A unified codebase across 2 apps and a Web portal (same project produces the ios, Android and web builds, reuse of css styles, UI components etc) - Significant reduction in effort developing and maintaining 3ish separate codebases for the same functionality (not quite 3x reduction, there are platform specific issues you have to resolve but still really great). - Way easier time resourcing the project, one skillet for the 3 frontends and the team can swarm to the required work (This was amazing in the current high demand market) - Access to the huge array of existing libraries and UI components For larger more established companies then sure go native. But for companies that have to efficiently use capital, any money spent basically building the same thing twice is money not invested in further understanding the user's needs and improving their experience. |
|