alt Hacker NewsI don't understand it from the app developers point of view. Having to pay app store cuts over basic card processing fees. I understand the appeal of access to a market, like selling on eBay gets you eyeballs. But once you have a customer using their app, what does the app give you that a PWA doesn't unless you need access to specific sensors / file system access patterns etc?
Replies
The vast majority of apps come from companies where the app developer has little to no say in how things work. Amazon, Walmart, Instacart, Uber, Ebay, Shein, etc are certainly not paying Apple 30% for purchases made inside the app. They also operate at a scale where they get bulk rates from MC/Visa on processing fees.
For years, Apple has muffled PWAs under a pillow. No one knows that you can add them to your homescreen or how that unlocks the possibility of getting push notifications. You also lose any stored data when you go from Safari to an homescreen web app.
I recently switched for m the developer mindset of build websites for everything to make apps if I can. My logic is that an app never needs to go back and forth with me, it's something the user can have without me managing hosting and constantly having a relationship with the user.
Don't you need a certain level of convincing for the average person to use a PWA?
Lock-in - and not even some evil thing; just if you're used to using the eBay app you're less likely to go somewhere else.
I think it's somewhat misguided, but companies gonna company.
As an app developer it comes down to the full access to phone APIs and the smoothest app experience. The more biased opinion is rooted in preference for the native language over web languages. And I recognize this is an opinion that is self-preservation in nature but it is what it is.
But I'll also say some apps don't really need to be apps (like ordering food from one specific store) but I won't complain about having those apps if it is a convenience.