Firefox

17907 readers

25 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago

MODERATORS

[email protected]

353

Apple limits third-party browser engine work to EU devices (www.theregister.com)

submitted 6 months ago by [email protected] to c/[email protected]

49 comments fedilink hide all child comments

The Register has learned from those involved in the browser trade that Apple has limited the development and testing of third-party browser engines to devices physically located in the EU. That requirement adds an additional barrier to anyone planning to develop and support a browser with an alternative engine in the EU.

It effectively geofences the development team. Browser-makers whose dev teams are located in the US will only be able to work on simulators. While some testing can be done in a simulator, there's no substitute for testing on device – which means developers will have to work within Apple's prescribed geographical boundary.

... as Mozilla put it – to make it "as painful as possible for others to provide competitive alternatives to Safari."

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 66 points 6 months ago (2 children)

And people ask me why I de-appled...

[–] [email protected] 1 points 5 months ago (1 children)

I'll de-apple when we get a viable alternative to Android. As is Google has far too much control over the entirety of that ecosystem to call it workably open, and if I'm going to choose between two proprietary vendors I'm going to choose the more reliable one with a business built around consumer interest instead of ad-company interests.

[–] [email protected] 0 points 5 months ago (1 children)

Try GrapheneOS. It has some quirks but it's a good alternative. Been using it for two years on a phone and I'm considering getting it on a tablet.

[–] [email protected] 0 points 5 months ago

Google still owns the ecosystem. They want to roll a new packaging system that depreciates apks and forces play store installs or Google based certificate pining? They'll have 90% market capture in a year. It's like using Opera/Edge/Etc and feeling safe from the decisions Google makes because of it, but they're writing and designing Chromium upstream so they still own the agency and the choice (See Manifest v3). Given two companies both preventing me from owning agency of my own device, I'll pick the lesser of the two evils and in my eyes that is currently Apple. I do hope to have a mobile operating system akin to Linux someday, but graphine os or any android dirivitive is not the solution, it just takes away my agency while they further the problem.

[–] [email protected] 10 points 6 months ago* (last edited 6 months ago) (4 children)

So who did you go with? Because stock android ain’t much better privacy wise.

[–] [email protected] 8 points 6 months ago

no, but on android you have firefox.. and you have f-droid with tons of OSS applications - and a lot of them are really good, so you can ignore everything made by google.

[–] [email protected] 4 points 6 months ago

GrapheneOS running on Pixel phone.

[–] [email protected] 19 points 6 months ago (1 children)

I'd recommend using GrapheneOS. (i'm using it, and it is a breath of fresh air)

[–] [email protected] 3 points 6 months ago (1 children)

On what phone?

[–] [email protected] 4 points 6 months ago* (last edited 6 months ago) (1 children)

What phone I have? Pixel 8 Pro (I bought it specifically for GrapheneOS, otherwise I wouldn't have bought a Pixel, als the original Pixel ROM is laggy as fuck)

Supported Devices are all Pixels since the Pixel 5a. https://grapheneos.org/faq#supported-devices

[–] [email protected] 6 points 6 months ago (2 children)

My Pixel 4a is slower with GrapheneOS than stock. Disabling GrapheneOS' Secure App Spawning helps noticeably.

With newer hardware it's likely not noticeable. (The 4a is old and even only receives security updates by GrapheneOS (no firmware updates by Google), so I really should replace it at some point.)

[–] [email protected] 1 points 6 months ago

Yup it's not noticable on the Pixel 8

[–] [email protected] 4 points 6 months ago (1 children)

So a 4 year old phone isn’t supported by Google anymore?

[–] [email protected] 2 points 6 months ago (1 children)

Yeah, only starting with the Pixel 8 they promised 7 years of support

[–] [email protected] 1 points 6 months ago

Let's see how that will go in 4 years...