The team is so darned small. They're great, but *wildly* understaffed. Apple could solve this by allowing better engines, or by investing reasonably. Doing neither gets you what we'v got: slow rot.
-
-
Replying to @slightlylate
“Better” is subjective, based on your priorities. What in particular do you think is “rotting”? As a web dev, I can’t think of something that I’m excited about using in a real world project that I’m only waiting on Safari to implement. IMO they’ve kept up pretty well.
2 replies 0 retweets 1 like -
Replying to @devongovett
That statement is worryingly circular, and part of how the architecture of control works: by withholding APIs for years, developers don't consider other widely-implemented features "available". We collectively lower our sights in response. Deadweight loss.
1 reply 0 retweets 6 likes -
Replying to @slightlylate
Ok, can you point to an example? Thinking back a few years, I can’t remember waiting to use a feature, or at least not for very long.
3 replies 0 retweets 0 likes -
-
-
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
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
-
-
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 - 5 more replies
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.