4 ms·
In my opinion, it is always the same "cross-platform" discussion. If you hire an iOS/Android mobile dev to write a native iOS/Android app, it means that you hir
by palata 3y ago
In my opinion, it is always the same "cross-platform" discussion. If you hire an iOS/Android mobile dev to write a native iOS/Android app, it means that you hire someone specialized in apps for mobiles. The whole point of a cross-platform framework is the hope that it won't need the specialization: "any web dev can now write a mobile app".
But every cross-platform framework has the same problem: platforms are different, and require work specific to them. As a result, cross-platform is "write once, debug everywhere".
If you don't know better, cross-platform frameworks systematically seem to "get to the same result faster". So many companies go for cross-platform frameworks. But in reality, the different platforms are so different that the only way to make a truly great app is to go native everywhere.
Not that there is not a place for PWAs: "cheaper but not as good" is clearly the trend everywhere. But I don't see PWAs replace "great native apps" anytime soon. If PWAs win, it will just mean that the users got worse apps because the companies spent less money on them.
- jwells89 3y agoI believe PWAs have a place in highly “templatable” things like restaurant pages and online shops. Those I can see adding to my home screen. Anything more complex than those is questionable.
- madeofpalk 3y agoWhy do you need to 'install' a restaurant app/website? That's the perfect usecase for like... a website.
- jwells89 3y agoFor quick access without cluttering browser tabs and bookmarks.
- BobaFloutist 3y agoYou value real-estate on your home screen less than in your bookmarks?
- jwells89 3y agoIt’s more that the number of sites I’d add to my home screen has a hard upper bound that’s not high, management is easy, and if I want one without it being on the home screen I can send it to the app library instead, where it’ll surface with a search. Bookmarks on the other hand are unbounded and suck to manage (no browser has improved meaningfully in this realm in ~20 years for some reason) so the threshold for what gets bookmarked is higher.
- paulddraper 3y agoIt's a spectrum. Some things are important enough for a bookmark, others are important enough for home screen.
- elevatedastalt 3y agoIt just feels a bit of an edgecase to imagine that a menu of a specific restaurant is important enough to occupy a spot in the top 20-25 of your digital real estate.
- paulddraper 3y agoWhat about a movie theater?
- troupo 3y agoI search for installed apps on my phone quite regularly. It's often faster than remembering where the hell it is in my folders on screen.
- julianlam 3y agoYou're able to add websites to your home screen without it being a PWA, but this is on Android. Assuming this is not the case on iOS
- jwells89 3y agoYou can on iOS too, but it opens a browser tab which is undesirable. Sites have to be marked as PWAs to open in their own process.
- madeofpalk 3y agoWhy would you need quick access to one restaurant’s menu? If you go there infrequently, I don’t understand why you would clutter up any part of my phone - bookmarks or Home Screen - with its menu. If you go there frequently… you already know the menu?
- jwells89 3y ago> If you go there frequently… you already know the menu? For most places, but there are a handful that have huge menus. Its name escapes me but for instance when I lived in SF there was a sandwich place I frequented that was one such shop and aside from a couple of favorites I could never remember everything they had. Also, these sites tend to facilitate ordering ahead, ordering delivery etc too so it’s not just a static HTML file.
- perilunar 3y agoAlso if they have online menus or ordering they usually have a QR code on the table or nearby. No need to bookmark or save anywhere.
- DANmode 3y agoFor most uses, "install" = hold my auth and put a bookmark on my home screen. In that regard, webapps work perfectly.
- smoldesu 3y ago> If PWAs win, it will just mean that the users got worse apps If PWAs win, it will be because native apps failed. Android and MacOS both have an enormous community of open source native apps that are more private, functional and accountable than their commercial alternatives. So far, Apple hasn't opened the floodgate for that on iOS. As a result, the interest in sideloading things has been relegated to the most-open part of the OS; the browser. It's not surprising at all. Apple could be enabling a Cambrian explosion of open iPhone apps and killing the case for dinky webapps overnight. Their motivation not to is rooted in a company-wide strategy to make more service revenue.
- palata 3y ago> If PWAs win, it will be because native apps failed. Or because the vast majority of people who "write code that runs on mobile phones" know web technologies and not the mobile ones. Web programming is simply more accessible. The thing is, "more" is not always "better".
- smoldesu 3y agoNone of that really disagrees with what I said. Apple failed to lower the on-ramp for native development to the people that wanted it. Now we're seeing desperate porting attempts to the browser, and Apple's desperate attempt at plugging the gap. > The thing is, "more" is not always "better". In the free market, competition is king. "Better" is decided by pitting it against "more".
- palata 3y agoI wasn't saying I disagree :-). > Apple failed to lower the on-ramp for native development to the people that wanted it. And they don't have to, IMHO. It's not that hard to learn how to do native iOS dev, and Apple is making a ton of money from those who do. Apple not wanting to go out of their way to lower the bar to a point that they don't find profitable is their choice. > In the free market, competition is king. I am not sure I am seeing "free market" and "competition" with PWAs, where people lobby to get laws to help them pass their ideas. The free market alternative would be for PWAs to get so good on Android that Apple decides to embrace them.
- threeseed 3y ago> If PWAs win That's like saying if Linux on the desktop wins in 2024. PWAs have been around for about a decade now. The excuses have run out.
- etchalon 3y agoI think Apple's failure to provide sufficient capabilities for PWAs is a valid excuse here. If PWAs are limited competitively on the platform with the highest ROI for developers … that's a problem.
- palata 3y agoI think it is debatable. Can I make an iOS app in pure Python, and should Apple make it possible? I think Apple has the right to decide what kind of API they provide to their users. Just like nobody is forcing Tesla to allow running Windows "because some developers would like to run Windows apps in their Tesla". I can see a problem with the monopoly on the App Store given the dominant position of Apple. But if Apple decided tomorrow to remove the screen from all their phones and have audio control only, I think it would be their choice.
- smoldesu 3y ago> Can I make an iOS app in pure Python, and should Apple make it possible? Given that neither the browser or iOS runtime can interpret it, no? I think it's reasonable to expect people to write an iOS Python interpreter and expect to get that distributed though. And if the users deliberately install it, what's the problem? > Just like nobody is forcing Tesla Tesla has to certify vehicles as road-safe. Besides FCC compliance (which Android handles just fine), Apple doesn't really have many legal safety obligations to use as a defense. Unlike a Tesla, Apple can let users sideload iOS apps without threatening other users around them.
- palata 3y agoMaybe I did not express myself well. My point was that Apple not embracing PWAs is their choice, I don't see the problem there. I see a problem with the idea that "we did not convince Apple with our PWAs, that's probably because they are evil, so now we'll try to force them with the law".