Why Safari can’t just launch from a Home Screen bookmark even if the user has chosen another “default browser”?
PWAs are already a separate “island” of storage and share nothing with Safari App…
Microsoft does it all the time with Edge on Windows.
PWAs are already a separate “island” of storage and share nothing with Safari App…
Microsoft does it all the time with Edge on Windows.
Currently PWA's open in an app that wraps Safari's engine to display the content and provide features but is not normal Safari. They interpret this to violate the browser choice law.
Their solution is to turn that feature off and go back to the icon just spawning the system default browser just like any link since that feature already existed.
To support true PWA's they probably have two choices:
1. Implement a standard WebView API that any engine can support then use that web view api for the PWA shell.
2. Do what Android seems to do and have a api that allows an app to create new launcher icons separate from the main app that starts the main app with parameters like url=https://pwa.com mode=pwa. Then if you create a PWA from Chrome it spawns Chrome if created from Safari it spawns Safari with whatever PWA UI they want. On Android it seems to make a little icon bottom right letting you know the parent app.
#1 is arguably more complex than #2, both are new api's for iOS that don't exist. #2 is on most desktop OS's like MacOS but not on iOS as far as I know.
Apples position is they don't want to put any resources in to creating a new api that could introduce new security surface area unless mandated to. Obviously their motives are not pure but it is a defensible position.
I think #2 would be a good feature adding flexibility to many apps, but the various shenanigans that apps could cause with that would need to be considered.
IIRC this is exactly what it does after the change. It now just launches the bookmark in a normal browser instead of a browser with the UI hidden.
Are there any people who actually prefer no PWAs at all over Safari-engine PWAs?
Personally I don’t care about PWAs at alls. If you want an app, build an actual app.
Are you going to foot the bill for the development cost of building an actual app for a team that doesn't have iOS software dev expertise?
Thought so...
Handwriting a 30 page assessment questionaire, fumbling a camera take relevant photos, and then manually correlating the photos to the assessment questions as it's written up properly... Is somehow better than a PWA?I
PWAs aren't a golden hammer, but they're not as useless as your opinions.
The truth is usually a lot less interesting than the hypothesis.
Being able to install software without needing an OK from the hardware manufacturer has been standard for over 40 years now. People do it on Windows PCs, on Linux PCs, on MacBooks and on Android phones, and that very clearly has not caused the extinction of the dinosaurs yet :)
The document Apple has published to me reads like it's written by a 5 year old that just was served too many sweets shortly before bed time.
IMHO this is about revenge, not about platform security.
I don't think you work in IT if you haven't had an infested windows, android or macOS box before. Hell I just spent the other day cleaning my father's Mac out of two VPN turds fighting with each other he installed after watching crap on YouTube. My daughter's windows machine got destroyed by unsigned crap from a Sims mod. You just don't get that on iOS apart from the odd calendar subscription turd.
As for spotify, they use their own subscription system, not the app store.
The only time in my life where I had an infected devices was in the year 1993 - a boot sector virus on a floppy disk I got from someone.
Luckily my wife is a nerd, too, by sister is trained and has not yet fallen for any of the social engineering tricks before. So no, I do not have to deal with other people's infected boxes either.
If that's a good deal is a matter of perspective ;)
I can totally believe that there is not enough time to re-think and re-architect how to implement push notifications, local storage and whatever other perks PWAs get for non-Safari third-party browser engines running as "apps." They may have lots of money and engineers, but throwing more of them at this problem is not going to build a well designed, thoroughly tested, and secure implementation any faster
[1]: https://developer.apple.com/documentation/browserenginekit/p...
From what I understand, the regulation is about allowing users to install third-party apps including browser and of course PWAs. I doubt they mandate what browser engine the app uses, that's the apps business only.
This is not the case in Safari[1].
Edge on windows, the same edge on windows that got caught slurping up chrome tabs recently?
Browsers are now the same size code base wise, as operating systems. They are in fact tiny OS's with permissions models and execution environments.
I think the author makes the point that safari made a lot of progress, they paid for a lot of work, that they are throwing away. Spite is a reason, but security is also a reason... We have seen how bad things can be when browsers cohabitate on desktops, putting up hard walls now solves the problem before it starts. Phone users aren't loosing (much) of anything, taking away something that they didn't have and didn't exist MIGHT be for security reasons...
See MS stealing chrome tabs.
The browser is bigger than the OS in total LOC.
No one is auditing that.
It is a question of when the video leaks of someone using their phone on the shitter.
If its a Samsung... well were gonna hear google and Samsung blame each other and consumers will be confused till everyone forgets about it.
If it's an apple, consumers blame apple. The buck stops with them.
You have to make a business decision based on this what are you gonna do? Im gonna lock all the doors I can.
When Facebook has a bug/exploit in their app that results in X hacker being able to gain access to files stored within the sandbox of Facebook noone is blaming Apple for Facebooks bug.