3 ms·
I'm gonna be the web guy... have we given up on the web completely? Why not improve the signup/payments experience using Web APIs? Why not integrate safari more
by sktrdie 6y ago
I'm gonna be the web guy... have we given up on the web completely? Why not improve the signup/payments experience using Web APIs? Why not integrate safari more closely to what is required with these App Clips?
It seems the only real reason that Apple isn't doing this is because it wants people to build for their App Store so they have control and possible revenue stream.
From a dev perspective this feels like a lock-in: yet another platform to support
- orev 6y ago> It seems the only real reason that Apple isn't doing this is because it wants people to build for their App Store so they have control and possible revenue stream. You say it incredulously as if that’s not a valid reason. Of course that’s the reason. Money is the reason why most companies do things.
- solarkraft 6y agoAll the cynical comments about Apple's ecosystem motivation certainly apply, but there's one much more mundane reason: UX. The best PWA still feels vastly worse than native versions (my reference is Twitter) and for Apple that's a huge factor, which I respect a lot.
- theschwa 6y agoI'd also add reducing friction. It seems the goal here is to reduce the amount of time it takes to get the user to the exact functionality they need in the shortest amount of time with a user experience that makes it feel seamless.
- vxNsr 6y agoA QR code is exactly the same thing. If you wanna talk NFC... how many people do you think are gonna buy apple's proprietary NFC broadcaster? either way though apple could use the same API to call a public website instead of a private call to a handicapped app. They're still downloading MBs of data. Not sure how big most websites are these days but I would surprised if most app clips don't go right up to that 10MB limit.
- nojito 6y agoWeb = Google Searches. Apple doesn't want you to do that anymore.