4 ms·
PWAs to me sound like "we want everyone to use the same OS (in this case something like ChromeOS), because that's more productive for us". I get that Google pu
by palata 3y ago
PWAs to me sound like "we want everyone to use the same OS (in this case something like ChromeOS), because that's more productive for us".
I get that Google pushes for PWAs because that's how they conquer the OS world. But why do individuals push for that? Because they don't know anything other than webtech and don't want to learn? Have a look at Kotlin and Swift guys, it's kinda cool!
- marvinblum 3y ago> But why do individuals push for that? Because we don't have the resources to build a native app for every OS out there.
- palata 3y agoAre you using Windows? I am happy that the people who contributed Linux/BSD/Android/iOS did not have your mentality, otherwise I would be forced to use Windows everywhere.
- marvinblum 3y agoI'm on Fedora. Of course, there has to be a native UI, but I'm running a two-person company for example. How on earth are we supposed to manage three or more platforms (browser, Android, iOS)? We're not lazy but limited by our mortality. > Because they don't know anything other than webtech and don't want to learn?
- palata 3y ago> How on earth are we supposed to manage three or more platforms (browser, Android, iOS)? Are you sure you need three or more platforms? In my experience, when I ask small companies what they need, they say "everything". If I listen to them, they even need to run on a Gameboy. Then most startups fail, so apparently the problem was not the number of platforms. It feels like many times, selecting the platforms may be fine.
- marvinblum 3y agoIn our case, it's a SaaS (pirsch.io) and browser first. But people and I like having an icon on our phones that we can click to open a dashboard quickly. Of course, this could just be a regular link, but it saves resources because PWAs will cache files (2 MB or something JS bundles for example).
- palata 3y ago> But people and I like having an icon on our phones that we can click to open a dashboard quickly. Doesn't make it necessary. Just like analytics, actually: people like to have them, yet most of the time they don't do anything meaningful with them. (Don't get me wrong: you are perfectly entitled to sell something people like, and people love spending time looking at analytics)
- sccxy 3y agoYeah, only privileged white people can build apps. Web is free and people can build and release web apps they want.
- palata 3y ago> only privileged white people can build apps. Android is free, isn't it? Most smartphones use Android. Then writing Desktop apps is free, too.
- andrei_says_ 3y agoI’m looking to release two web apps as PWAs. This will make the experience close to native on iOS and android without going through the app stores.
- palata 3y agoHow do you release them? You don't have to go through the Play Store to release an Android native app, and I think the EU is making it change for iOS.
- andrei_says_ 3y agoBy Release I mean Create on the web, make downloadable as a PWA. No App Store necessary. The PWA functionality will be fairly simple, mostly around reminders and badges.
- davidy123 3y ago"Cool" is not a great reason. Only having to develop something once that serves all users is great, though. Personally, I cannot stand apps, I only use them when absolutely required, using a PWA gets you all the security of the browser (relatively speaking, but it's a lot more secure than a from scratch black box, and look at goon moves like Facebook embedding a browser that retains third party site interactions) and as a developer and user I can use my own extensions and general browser features.
- palata 3y ago> Only having to develop something once that serves all users is great, though. Cross-platform usually sucks in some way. If the app is not worse, the development is: "write once, debug everywhere". Web is solving that by forcing everybody to use the same (Google-controlled) renderer, so that there is no need for cross-platform anymore: just use the Google thing. I don't want that.
- davidy123 3y agoDebug everywhere or google controlled, those things seem diametrically opposed. Aside from the murky area of cookies, chrome isn't straying much from web standards. There's really not much reason to not use a browser, the compatibility issues are pretty much a thing of the past on any browser, unless you're doing something esoteric. Installing a special app should be unusual.
- palata 3y ago> Debug everywhere or google controlled, those things seem diametrically opposed. That's what I said. > the compatibility issues are pretty much a thing of the past on any browser Because there is only one meaningful browser left: Chromium. It is not a solution to cross-platform, it is just pushing for a monopoly. Just like a few years ago you could have been advocating for supporting exclusively Internet Explorer: that solves the compatibility issues too. Now PWAs are not trying to kill other browsers (it's done already), but other platforms. That's just the next step.
- bad_user 3y agoThe biggest reason, as I see it, is that the web is a free market, whereas on Android's and iOS's app stores you're beholden to Google's and Apple's taxes, restrictions and whims. The second reason is the resources available. Going web first means your app is instantly available everywhere, even if not perfect. We can learn Android and iOS development for sure, but how about both? And have you ever seen shops with the same developers targeting both iOS and Android with their native stacks? I haven't. Besides the web, you're limited in available options for reusing existing code and knowledge, such as React Native, and using cross-platform toolkits may be more risky than targeting the open web.
- palata 3y ago> is that the web is a free market Controlled by Google with Chromium, right? > The second reason is the resources available. I guess that's the excuse, yes. But in my experience the native way is not necessarily more expensive. It's just faster to make a prototype in web, I suppose. And most apps end up being prototypes thrown into production nowadays. So yeah: it's cheaper, not better, but that's enough to win.
- bad_user 3y ago> Controlled by Google with Chromium, right? No. We may speak about a hypothetical future, but right now, that's false. You don't need to pay the 30% tax on all sales, you don't need permission to publish a web app, you don't need to obey the rules for what's permissible in an app store, you don't go through a review process, you don't get your appeal judged by a kangaroo court. And while there are ways for Google to ban you from Search or flag your website in Chrome, a vast majority of cases had to do with legal censorship requests, copyright law, or blocking malware. Google doesn't even have that much control because Chromium is FOSS, it already has contributors from companies with deep pockets, it can always be forked, which means Google has to play nice, like all FOSS stewards. Google has some control over the web, but their leeway is vastly overblown, and a bad rhetorical trick. This isn't even a matter of perspective, and if smart, educated individuals can have disagreements on such clear issues, we are in trouble. --- > But in my experience the native way is not necessarily more expensive. We don't share the same experience. If you're speaking about personal projects displaying some simple forms, sure, but all the software companies I know hire separate Android, and separate iOS developers, tripling the frontend cost, with the minimum being one Android developer and one iOS developer. I have in mind companies big or small, start-ups or commercial FOSS even. The one exception I know used React Native, with an emphasis on iOS, the Android experience being terrible.
- int_19h 3y agoExcept Microsoft is also actively pushing for PWAs, and Win11 integration of them is pretty nice.