2587
Firefox to become first mobile browser to support desktop extensions later this year
(blog.mozilla.org)
this post was submitted on 13 Aug 2023
2587 points (98.1% liked)
Technology
59627 readers
2979 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
i hope mozilla is already working on an iOS version for the EU market ;)
This is the only reason why I keep using Safari on iOS. If Firefox can get extensions working for iOS I’ll switch over the day it’s available.
i miss(ed) exactly two things on iOS: a proper imageboard reader (fixed, there are now chance and janchan) and stand alone firefox, wich is now just a matter of time.
I don't see how they would, since ios Firefox doesn't use the same rendering engine it uses on other platforms, Gecko. Instead it has to use Safari, just like any other browser on there.
Duplicating support for all existing extensions would be pretty much impossible if you don't control the rendering engine.
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!