this. they simply have to port the version they’re developing for android now and we’re golden. i guess it might find it’s way on non-eu-devices by community builds and testflight.
Yeah it’ll be a big task nonetheless. Firefox for Android needed gecko components to be ready to make use of gecko view, their rendering “engine”. iOS may be need its own version of gecko view, at least the bindings for it, as well as a new set of components for all the UI elements a full fledged browser may need.
I heard about allowing alternative app stores, but I’m not sure if that also removes the browser engine restrictions. (would make sense though, from an anti-monopoly pov)
The restriction is from App Store, and bypassing it removes that hurdle. Microsoft faced the same issue when they were trying to launch their cloud streaming service within their app, not because they technically couldn’t, but because Apple wouldn’t let them to.
That’s going to change in EU as Apple will be forced to allow side loading apps.
this. they simply have to port the version they’re developing for android now and we’re golden. i guess it might find it’s way on non-eu-devices by community builds and testflight.
Yeah it’ll be a big task nonetheless. Firefox for Android needed gecko components to be ready to make use of gecko view, their rendering “engine”. iOS may be need its own version of gecko view, at least the bindings for it, as well as a new set of components for all the UI elements a full fledged browser may need.
I heard about allowing alternative app stores, but I’m not sure if that also removes the browser engine restrictions. (would make sense though, from an anti-monopoly pov)
The restriction is from App Store, and bypassing it removes that hurdle. Microsoft faced the same issue when they were trying to launch their cloud streaming service within their app, not because they technically couldn’t, but because Apple wouldn’t let them to.
Ahhh, that makes sense. Thanks!