4 ms·
I think in terms of business apps (not games!) it's better to go PWA first. Check out this really good case study of the Starbucks PWA. The PWA is 233 kb compa
by hilti 9y ago
I think in terms of business apps (not games!) it's better to go PWA first. Check out this really good case study of the Starbucks PWA.
The PWA is 233 kb compared to 148 MB iOS native app.
https://formidable.com/static/Formidable-Case_Starbucks_PWA.864ef9d5.pdf https://formidable.com/static/Formidable-Case_Starbucks_PWA....
- kaycebasques 9y agoWebAssembly (plus PWA) is kind-of promising in terms of games, no?
- madeofpalk 9y agoPromising, maybe. Still not practical. APIs available to the web ecosystem are always going to be one level abstracted or behind their fully native counterparts.
- matthewmacleod 9y agoThis case study is nonsense. There is no case in which a native app will be 148MB in size, while a web app with comparable functionality will be 233kB. None. Quite aside from anything else, the Starbucks PWA is a strictly worse experience than the native application.
- hilti 9y agoInteresting. So please let us know your about your experiences and strategies on maintaining applications across several platforms (iOS, Android, Tablet and Desktop) while keeping binary sizes small with comparable functionality and good user experience. I'm willing to learn and improve on that topic.
- tptee 9y agoI worked on the PWA from its inception until the past few months. The size difference is real, and I'd wager that it was 75% at parity with the native featureset at the time I left :)