241–250 of 268 posts
Earlier quoted context omitted.
> for the best experience, use In this case you’d need “use ”. There’s no alternatives to Safari for PWAs on iOS.
That just changed in the EU: https://developer.apple.com/support/alternative-browser-engi...
PWAs will never be as good as native, definitionally. There is always API drift. There is always runtime cost. Nothing inside a system can ever have parity with its parent container. If it could, it would be the system itself. People's experience with hardware and physical objects matters. If you accept that, you should always want to be closer to the metal at the cost of convenience or portability.
PWAs can absolutely be as good as native, however they aren't being given a chance due to reasons unrelated to technology. I personally believe it is the protection of Apple's fees that is driving its poor implementation of web technologies (even though their original plan was to only have web apps, with a small number of native apps for very specific things). The money they could extract from the app store made them…
To add to your statistics: I am an Android user, and I mostly hate PWAs. I want native apps.
PWAs will never be as good as native, definitionally. There is always API drift. There is always runtime cost. Nothing inside a system can ever have parity with its parent container. If it could, it would be the system itself. People's experience with hardware and physical objects matters. If you accept that, you should always want to be closer to the metal at the cost of convenience or portability.
In theory you are right but in practice you are absolutely wrong.
Still I don't think it's a reason to completely give up on the good ways.
Earlier quoted context omitted.
I just don't really agree, almost all modern JS engines compile to machine code, so it's as "low" as writing Swift or Objective-C.
I think you're not talking about the same thing. What I am saying is that if you depend only on Apple and their framework, then you have all the improvements as soon as they exist and you don't really have the risk that Apple stops developing iOS (or if they do, then iOS is most likely dead). If you depend on, say, Qt-for-iOS, then you need Qt to integrate the new features (with more or less success, taking more or l…
Earlier quoted context omitted.
Apple does not charge for "using their SDK". They charge for installing (commercial) applications to devices they produce and sell. Even if I build an application completely without the Apple SDK, just with open source software, I can't sell it to people without paying the "Apple tax". Your example VS Code is not related to that at all, because Microsoft doesn't prevent installing applications built with other tools.…
> Apple does not charge for "using their SDK". They charge for installing (commercial) applications to devices they produce and sell. The mechanics of how the fee is charged don't determine what it is for. This is like saying Amazon charges you a $49 fee to use their checkout page when ordering a book. > Your example VS Code is not related to that at all, because Microsoft doesn't prevent installing applications buil…
Earlier quoted context omitted.
PWAs can absolutely be as good as native, however they aren't being given a chance due to reasons unrelated to technology. I personally believe it is the protection of Apple's fees that is driving its poor implementation of web technologies (even though their original plan was to only have web apps, with a small number of native apps for very specific things). The money they could extract from the app store made them…
> and they've managed to convince every Apple fan it's for their benefit To add to your statistics: I am an Android user, and I mostly hate PWAs. I want native apps.
Earlier quoted context omitted.
I 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.
I 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…
https://python.plainenglish.io/python-for-ios-the-ultimate-g...
Yes?
Understandable... PWAs are ultimately an alternative path from traditional mobile apps which will take away money from apple/google. But as a web dev community we need to stand firm and build PWAs regardless. If we treat pwas on iOS like we did Internet explorer (i.e. giving it special attention and hack solutions as opposed to just not developing for it) we will lose the fight. I suggest you call out the issues with…
I for one would much rather have native mobile apps that use platform-appropriate controls rather than web apps that use whatever some designer came up with. We’ve already lost this battle on computers because of electron, but iOS is nice precisely because there isn’t an easy way to just ship web technology “apps”.
It is not fundamentally wrong to do custom stuff. I prefer native apps as well but this sound bite needs to go away.
PWAs will never be as good as native, definitionally. There is always API drift. There is always runtime cost. Nothing inside a system can ever have parity with its parent container. If it could, it would be the system itself. People's experience with hardware and physical objects matters. If you accept that, you should always want to be closer to the metal at the cost of convenience or portability.
Earlier quoted context omitted.
I 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…
> 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 comp…
And is this a universal principle of yours?
For instance, would you say the same about malware—that anyone should have the right to develop it, and use whatever shady tactics they want to trick people into installing it—and if they do, that becomes their problem?