• Oh I’m sure there will be. It will be technically difficult (but not impossible) for them to allow other app-stores and sideloading but have the hardware and software be different enough in both markets to not have some slip through.

      I suspect there will be lots of hacky shit for this.

      •  errorlab   ( @errorlab@lemm.ee ) 
        link
        fedilink
        English
        8
        edit-2
        8 months ago

        I remember that there was an identifier based on model number. FaceTime wasn’t allowed in the Middle East for a while, there was a way to tell if the model will support it based on the last character after the / in the model number. Middle East models won’t even have the app at all.

        Propably they’ll do the same for models sold in the EU.

        There are already hardware variants of the same iPhone. I think the US gets an iPhone with all eSIM, and China has two physical SIM slots.

      • I’m sure it will be and I’m also sure Apple will do EVERYTHING to make it almost imposible to do that. They may also block users from using their iPhones if they discover that they are set to EU, but they are actually not in EU.

    • Literally all I had to do to make my phone have a usable performance again was to set the region to France, and the language to English. I should add that it was totally fine before an update.

  • This is actually huge.

    I’m far FAR from an Apple user, but the moment this is available, I’ll be seeing if I can install FireFox with µBlock Origin on my partner’s phone.

  • I wish I was born in europe rn lol. tbh with india’s population the gov could try something similar and apple would likely comply to not lose a huge amount of potential consooomers. Android has always been the dominating mobile os here but apple is slowly gaining numbers and they wouldn’t like to see the graph go down.

  • This is the best summary I could come up with:


    With iOS 17.4, Apple is making a number of huge changes to the way its mobile operating system works in order to comply with new regulations in the EU.

    One of them is an important product shift: for the first time, Apple is going to allow alternative browser engines to run on iOS — but only for users in the EU.

    Apple is clearly only doing this because it is required to by the EU’s new Digital Markets Act (DMA), which stipulates, among other things, that users should be allowed to uninstall preinstalled apps — including web browsers — that “steer them to the products and services of the gatekeeper.” In this case, iOS is the gatekeeper, and WebKit and Safari are Apple’s products and services.

    Even in its release announcing the new features, Apple makes clear that it’s mad about them: “This change is a result of the DMA’s requirements, and means that EU users will be confronted with a list of default browsers before they have the opportunity to understand the options available to them,” the company says.

    Apple argues (without any particular merit or evidence) that these other engines are a security and performance risk and that only WebKit is truly optimized and safe for iPhone users.

    But in the EU, we’re likely to see these revamped browsers in the App Store as soon as iOS 17.4 drops in March: Google, for one, has been working on a non-WebKit version of Chrome for at least a year.


    The original article contains 596 words, the summary contains 248 words. Saved 58%. I’m a bot and I’m open source!