I'm not sure I understand your wording right... Are you saying that devs creating PWAs are "free?" Because it's well-known that PWAs has been stunted by Apple and Google. The technology is well behind its potential. PWAs could do significantly more if they had better access to system APIs.
It is not well-known. It is well-believed.
I don't believe Apple has intentionally crippled Safari just to prop up their native platform. Google are the ones who invented the PWA buzzword and spend all their devrel effort on pushing. It's hard to believe they would also try and hamper that.
Once you deny it access, you have to go into settings to change it - just like any other app.
How much money do you think Apple makes when the same probably free website is a free app?
Not every website I visit needs to know my location.
Not every website with a map needs access to my location.
Only websites I specifically allow to access my location should have access.
On the iPhone and specifically safari I've never had an issue or a steep learning curve to showing someone how to long press the reader view (AA) in the url then select _allow location_ or whatever.
I wonder if you sample all had something in common. Did they not regularly use this web app? Was this an event specific web app? If so it would be nice if the web app detected mobile browser by user agent and displayed instructions for activating location. Might help reduce confusion.
There’s pretty much no reason why 99.999% of any apps in existence need my precise location.
It’s not broken at all.
I think any complaint directed towards Apple's development on Safari can also be directed towards their actual native platform. Terrible/non-existent documentation, frequently breaking APIs, and a completely hostile app store and bug reporting/feedback process.
In the history of computing there has never been a cross platform general purpose GUI framework that didn’t suck.
Not to mention most Android devices in the wild are low end and don’t handle complex web pages well
What conspiracy?
They have huge economic disincentives to further PWAs - there is no need for any conspiracy.
In the first presentation of the iPhone, Steve Jobs laid out a vision where the smartphone would run web apps, using fundamental web technologies (HTML, CSS, JS). He quickly backtracked when he realised Apple could impose a 30% tax on transactions in the platform.
> Maybe web technologies just aren’t as good as native?
No one said they are, but that's no excuse to drag your feet in implementing simple things like push notifications.
> In the history of computing there has never been a cross platform general purpose GUI framework that didn’t suck.
What GUI framework? I barely even know what we are talking about anymore. You don't need one with PWA - again, you're using fundamental web technologies, and enabling them to make system calls.
> Not to mention most Android devices in the wild are low end and don’t handle complex web pages well
So that's another excuse to not further PWAs, huh?
Let me ask you this then. Name one cross platform framework that wasn’t meant to build command line tools that hasn’t sucked?
QT? Java Spring? React Native? Electron?
> In the first presentation of the iPhone, Steve Jobs laid out a vision where the smartphone would run web apps, using fundamental web technologies (HTML, CSS, JS). He quickly backtracked when he realised Apple could impose a 30% tax on transactions in the platform.
He “backtracked” because his “sweet solution” wasn’t good and everyone wanted native apps and web apps were called “a shit sandwich” by developers.
Do you know the history of creating “applications” using “web technologies”? They failed for RIM, Microsoft, and Palm. Web apps suck not to mention the clusterfuck of the front end ecosystem.
Every single platform that went down the “we can do great web apps” backtracked. They have never been good enough.
> So that's another excuse to not further PWAs, huh?
You mean making an app that’s actually performant on the majority of phones out there?
Sure, the 30% cut of all sales was just a sweet coincidence.
> You mean making an app that’s actually performant on the majority of phones out there?
Twitter and Uber have PWAs for countries where low-end devices are the majority of phones.
> They have never been good enough.
Complete bollocks, there are plenty of excellent web apps out there, and it's one of the most important mechanisms for software delivery nowadays, in both the enterprise and consumer spaces. You are a fundamentalist and there is no point discussing anything here anymore
Besides that, most of the biggest players like Netflix and Spotify don’t even allow in app purchases.
Where are all of the great web apps for mobile? Have you tried using any of these web apps on Firefox for Android or is Firefox also involved in the conspiracy?
No one is clamoring for cross platform web apps accept web developers who want to foster a shitty Electron like experience on mobile.
And look at all of the server side work that Uber had to do.
https://www.uber.com/blog/m-uber/
And this wasn’t done to avoid the “30% tax” since Uber doesn’t use in app purchases. You do have Apple Pay as an option. But that’s a standard credit card transaction.
Isn't the whole point of PWAs that they're easy because they're just web apps? If you start using system/OS specific APIs you lose all of the benefits except for the instant install time.
Just look at how reviled Electron is compared to native applications.
A couple of years ago I worked on an app that ran on 5 platforms (iOS, Android, Windows, macOS, ChromeOS). Initially we used Phonegap and Electron but then we created our own native wrapper that used the OS webview.
Our macOS app went from 100MB to 5MB of download size and the memory usage also went down considerably. IIRC correctly it consumed like 15MB of memory.
It certainly didn't look native but for our use case (education) that was not an issue. We were able to target 5 platforms with a very small team and the GUI was a single codebase made with InfernoJS and MobX.
https://9to5google.com/2021/10/10/google-ios-apps-native/
Facebook moved away from cross platform web based frameworks for its apps years ago.
Microsoft’s mobile and desktop apps (besides Teams which also sucks and VSCode which is pretty good) are not using web frameworks.
And most apps that would be suitable for PWAs are in fact free. How would Apple or Google benefit financially?
Besides most of the App Stores’s revenue comes from games
What happens when either Apple or Google introduce a new feature to their native platform?
I would definitely not use the ElectronJS Slack app if I had a choice.
People prefer Electron because it gives them a consistent environment across operating systems, OS versions/update patch numbers, browser versions etc.
If you write your app to work in all possible combinations of the above - like you'd write a web page - you can use OS web view.
But not everybody wants to do that because it's not as straight forward as just writing your app and being able to fully rely on your environment. Perhaps you actually need features that aren't universally available in the OS web view yet, and performance degradation because of polyfills is not acceptable.
Also, OS web view is usually locked down more than Electron. It's basically a browser without the UI around it. Then you need to hack your own native bridge instead of just using whatever Electron made. I guarantee your version is going to be worse, you simply don't have the combined resources of the Electron open source project.
People don’t prefer an application that takes up more memory, drains battery life and that’s not consistent with their other apps. Developers may prefer it.
How many users are switching back and forth between Windows and Macs?
The same applies in the other direction. When I was a Windows user, I hated the iTunes interface because it felt like a bad Mac port. I was a former Mac (and current) Mac user so I could tell.
Even before that, the Windows QuickTime Player felt like a bad port.
Software development is not just about the users. Many Electron apps are single dev ventures. It's not easy to maintain multiple different platform specific apps even for a large enterprise. The larger the app the more difficult it becomes.
And this says a lot about why people prefer commercial alternatives.
Except for all those popular Electron apps with lock-in effects, like Discord and Slack.
There are no alternatives to the Slack ElectronJS Desktop app. That's the whole point: they don't want to maintain native apps. And they don't open their API to let others do it, I guess because that may hurt their lock-in benefits.
I don't notice any issues with Obsidian which I use every day.