3 ms·

> PWAs are great. They were literally Steve Jobs' original vision for the iPhone. Was it? I think one of IOSs strength is its operating system and proper nativ

> PWAs are great. They were literally Steve Jobs' original vision for the iPhone. Was it? I think one of IOSs strength is its operating system and proper native apps. PWAs are inaccessible, bloated, slow and awkward to use.

boomskats 7mo ago
> Was it? Yes. Here's a quote for you from the original WWDC 2007 iPhone launch[0]: _"We've come up with a very sweet solution. An innovative new way to create applications... it’s all based on the fact that we have the full Safari engine in the iPhone. And so you can write amazing Web 2.0 and Ajax apps that look exactly and behave exactly like apps on the iPhone! And guess what? There’s no SDK that you need!"_ > I think one of IOSs strength is its operating system one of the OS' strengths is its OS, cool > and proper native apps not what we're talking about here at all > PWAs are inaccessible, bloated, slow and awkward to use. literally the opposite of all those things [0]: https://www.youtube.com/watch?v=p1nwLilQy64 https://www.youtube.com/watch?v=p1nwLilQy64
- Levitating 7mo ago
  > one of the OS' strengths is its OS, cool Woops, messed up the wording there. It's an interesting way to go about it. But I am not sure it's the same as what we get now. We aren't just leveraging the webkit renderer, we are using the browser as a complete OS/runtime for your applications. On top of an OS that already has its own UI libraries. The current standard is that when you visit a webpage you are downloading an application in the tens of megabytes. In 2007 that would barely be possible. When I think of PWAs I think of Microsoft Teams. It's slow as a website and somehow slower as a >100mb "native" app. Anyway thanks for the reference. I am curious how much the current method strays from what Apple envisioned back then.
fennecfoxy 7mo ago
Native apps were never a part of the original iPhone release, all the apps were essentially web apps, running one at a time (no multi-tasking/running in background unlike it being built into Android from the get-go).

boomskats 7mo ago

> Was it? Yes. Here's a quote for you from the original WWDC 2007 iPhone launch[0]: _"We've come up with a very sweet solution. An innovative new way to create applications... it’s all based on the fact that we have the full Safari engine in the iPhone. And so you can write amazing Web 2.0 and Ajax apps that look exactly and behave exactly like apps on the iPhone! And guess what? There’s no SDK that you need!"_ > I think one of IOSs strength is its operating system one of the OS' strengths is its OS, cool > and proper native apps not what we're talking about here at all > PWAs are inaccessible, bloated, slow and awkward to use. literally the opposite of all those things [0]: https://www.youtube.com/watch?v=p1nwLilQy64 https://www.youtube.com/watch?v=p1nwLilQy64

Levitating 7mo ago
> one of the OS' strengths is its OS, cool Woops, messed up the wording there. It's an interesting way to go about it. But I am not sure it's the same as what we get now. We aren't just leveraging the webkit renderer, we are using the browser as a complete OS/runtime for your applications. On top of an OS that already has its own UI libraries. The current standard is that when you visit a webpage you are downloading an application in the tens of megabytes. In 2007 that would barely be possible. When I think of PWAs I think of Microsoft Teams. It's slow as a website and somehow slower as a >100mb "native" app. Anyway thanks for the reference. I am curious how much the current method strays from what Apple envisioned back then.

fennecfoxy 7mo ago

Native apps were never a part of the original iPhone release, all the apps were essentially web apps, running one at a time (no multi-tasking/running in background unlike it being built into Android from the get-go).