But the bigger the market they can reach, the bigger the reward, and so at some point it may justify investing resources to work around those roadblocks and accept the drawbacks.
But the bigger the market they can reach, the bigger the reward, and so at some point it may justify investing resources to work around those roadblocks and accept the drawbacks.
Those are 3 large jurisdictions, I wonder if that's now a market big enough for Chrome and Firefox to invest into iOS versions of their browser that use Blink and Gecko under the hood. From what I heard this was one of the main reasons they haven't done it yet.
Otherwise, yes it's likely web apps will prompt their user to use a browser with a capable engine on iOS if they exist. Nothing to configure, install and use.
Users will then be able to use capable web apps that take up a tenth of the storage of native apps, that are cheaper and portable across platforms — among many other benefits.
That brings me to this: Chrome extensions are valuable and we know as early as the rumors of Apple being forced to open up, Google started working on iOS port, but really, is there any justification for bringing a browser engine to iOS? I really don't understand how will it be beneficial when the user probably will notice anything.
Also we only have like four players to enter: Google (which will come), Mozilla (broke and miss-managed as hell), GNOME Web (will never come), Ladybug Browser (they are crazy and will definitely come someday, but it takes a long time for them to be an actual player)
So my question is: Will all this effort even fruit?
Apple's WebKit is renowned to be lagging behind, refusing to implement crucial features and being rigged with bugs, hence limiting the capabilities and quality of web apps, and effectively preventing them to compete with native apps.
Getting other browser engines on iOS would be beneficial for developers, businesses and end user by making mobile web apps viable.
VM is EU. Heck, it can be an ephemeral instance on EC2, so it would only cost money while in use, probably tens of cents or something.
If there's a will, there's a way.
Only real devices allow to test these aspects properly.
I'm not 100% sure no other mobile OS allowed this before to be honest, but I'm pretty iOS is the one that popularized it.
Jobs framed it that way, but IIRC, all you could do is create bookmarks. Creating an icon on the Home Screen? Impossible. Reliably storing data on-device? Impossible. Backing up your on-device data? Impossible. Accessing your on-device contacts, photos? Impossible.
Also, Jobs made a vision statement about web apps in June 2007, but Apple announced a SDK only four months later (in October 2007) and shipped it in March 2008.
⇒ I’m fairly sure he knew about that SDK when he made that statement.
Apple invented installable mobile web apps.
Link about the needed metatag: https://www.mobilejoomla.com/forum/4-feature-requests/330-ip...
Steve Jobs introducing web apps as the way to develop apps for the iPhone in 2007: https://williamkennedy.ninja/apple/2024/01/30/steve-jobs-int...
This wouldn't be much of an issue, of course, if Chrome would just run on iOS like it does on any other OS, so Google can implement PWAs themselves.
This was the way developers were supposed to develop apps for the iPhone when it was released, before Apple introduced the App Store.
It's not. Even in the US there is lots of variation between states. Delaware company exists for a reason.
EU is already so harmonized that startups can shop for best corporate structure and law, just like they do in the US and run their business smoothly. Estonia, Netherlands, Ireland, Luxembourg, Sweden, ... pick your favorite. What makes EU more difficult as common market is more different business cultures, languages, and markets. That's not something EU can change from the top.
It's not harmonized at all, it's fully fragmented.
You can't hire someone working from another EU country. You can't raise capital across the EU. You have many different rules, regulations, taxes, etc depending on the state.
Because of the way the App Store works, browser engines segregated by region need to be two different apps. That means maintaining two source trees (EU+UK+JP vs worldwide) and two releases with two reviews.
I expect niche browsers to have a go at porting to iOS at some point (I'd love to see a project like Ladybird be the first non-Safari browser on the app store!) but for the major companies it seems like too much of a hassle at the moment.
Now the question is what's the threshold for this market to be big enough? Maybe Japan's joining in pushes it past that point.