What does that even mean?
-
-
Replying to @devongovett @slightlylate
That they allow you like I do on Android to use PWAs the same as installed apps. Just like I am right now on Android to talk to you. A simple Google would tell you what a PWA is
1 reply 0 retweets 3 likes -
Furthermore do you use safari on desktop? Is it actually good? Do you for some reason want apple to do as little as possible? Why? I don't get your angle here. Defend apple at all costs?
1 reply 0 retweets 3 likes -
Replying to @sethreidnz @slightlylate
I'm using Chrome right now to talk to you. I tried the Twitter PWA on iOS for a while actually. It was pretty good, but the UX wasn't quite as smooth as the native app. Not because of something iOS did, just because native UI frameworks make building polished apps easier.
3 replies 0 retweets 1 like -
My question was what PWA features are still missing on iOS? It's been pretty good recently.
3 replies 0 retweets 1 like -
Replying to @devongovett @sethreidnz
Off the top of my head: Nav Preload, storage quota (Safari's is whack), anything worklet based (which is how we will get good UX), push notifications, durable storage, splash screens from manifest...I'm sure I'm forgetting a dozen. Its a huge list, and each one blocks a major org
1 reply 0 retweets 10 likes -
Replying to @slightlylate @sethreidnz
Is it bad that I’m a web dev and I’ve never even heard of most of those features let alone needed them in a production app? I can’t be the only one... Maybe engine priorities aren’t aligned with web dev needs?
3 replies 0 retweets 2 likes -
Thats totally valid imo, people build different things on the web. I will say though, ive talked to dozens of developers building app experiences on the web and Safari seems to always be the "well, this works everywhere but here" browser. Ive seen this harm the web 1/2
1 reply 0 retweets 11 likes -
Replying to @Justinwillis96 @devongovett and
to because teams then decide to go native on all platforms just because Safari does not have support for things their PWA needs, even though its in every other browser.
1 reply 0 retweets 5 likes -
I find it hard to believe that this choice would be made only because Safari didn’t have a few optimizations. You could easily ship a normal web page. There has to be other factors: UX, delivery mechanism, etc.
4 replies 0 retweets 0 likes
At the scale of Google "a few optimisations" is absolutely a launch blocker. And that's only the tip of the iceberg. Major gaps in capabilities block many apps from even trying.
-
-
Replying to @slightlylate @devongovett and
I nearly forgot the big one: you can put PWAs in the Play Store, the Windows Store, and the Samsung Galaxy Store.
?



1 reply 0 retweets 2 likes - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.