4 ms·
Your take is what I recall as well. And not just Jobs and Apple on the HTML apps kick, Jon Rubenstein (aka 'the Podfather' for producing the iPod) left Apple t
by Terretta 4y ago
Your take is what I recall as well.
And not just Jobs and Apple on the HTML apps kick, Jon Rubenstein (aka 'the Podfather' for producing the iPod) left Apple to make Palm into a web app powerhouse, developing the webOS platform and the Palm Pre.
This is how mobile devices were supposed to work. The "native apps" jag is a disaster I'd argue was mostly generated by devs not users or manufacturers, and set mobile web back a decade.
- pjmlp 4y agoLooking at Symbian and Windows CE/Pocket PC, not really, it was pretty much native apps.
- mike_hearn 4y agoIf it was how they were meant to work then iOS would have looked like WebOS, with all first party apps written in HTML and JS. The reason devs rejected Jobs' "write web apps" pitch, which was only ever about the SDK, store and APIs not being ready in time, was because it was so clearly not what Apple themselves were doing. Nor could they hope to match the quality of Apple's apps without using the same APIs.
- dmitriid 4y ago> was mostly generated by devs not users or manufacturers, and set mobile web back a decade. This simple fact was true in 2007 and it still is true in 2022: you can't even animate a list item on the web without incurring significant performance costs. Slack eats 20% CPU on an M1 Mac to display a single animated emoji. Web has never been, and never will be a platform for apps. This has nothing to do with "devs vs. users". Users want slick performant apps that don't destroy your battery life. Web cannot and will never be able to offer that. Because the core of the web is, was and will for ever be a system to display static text and images in a single rendering pass.