This increase competition a lot. I like it. Sure people using iPhone may not like options, but at least some can now.
Technology
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 other!
- 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
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
I wonder what counted as "an EU iPhone"?
The serial number? GPS location of the phone? IP address?
How could one outside of EU region to have an "EU iphone"?
An European iPhone, aka an iPhone which will get these features, is identified by a background process named countryd
, introduced in iOS 16. Its only purpose is to compute and predict the most likely location of the user (as in country/region) and lock down features accordingly.
These are only some of the factors taken into the equation:
- GPS location
- Wi-Fi location
- Wi-Fi hotspot country codes
- Cellular/GSM country codes
- IP address
- Home and roaming operator regions
- Apple Account region
- Device region
- Satellite reachability
countryd
takes in all of these and more as input to provide the most likely country of the user. If that country is in the EU, then 💥 Sideloading, Default Apps, etc etc etc goodies
I was in Corfu last week when the news of the Epic store came about, so tried to install it on my UK registered iPhone. All I got was a notification telling me that my phone isn’t eligible.
So yeah, no Fortnite in my phone for me. Not that I really care about that, I just like fiddling with shit.
Brexit means brexit
The gift that keeps on giving.
Sadly.
IOW, not something that one stuck in Ameristan can realistically override. Damn.
A handful of those factors are fairly trivial, but addressing all of them concurrently sounds like a tall order - especially since presumably one can't talk to countryd
directly and feed it the desired data.
Appreciate the clarity - iOS just isn't a platform I have a need or the tools to code in.
I tried fooling it myself several times with the aim of getting satellite connectivity in my unsupported country, to no avail.
Used a German SIM card (where this feature is supported), went in my basement where there’s no cell service so that it can’t read MNC or MCC from any networks nor can it read GPS precisely (the circle spanned almost all of Western Europe, that imprecise I mean), used a Raspberry Pi as a router with country code as DE, disabled Wi-Fi, used VPN, used the Xcode debugging tools to simulate iPhone location to Germany (this usually fools all apps into thinking I’m in Germany, including Apple’s own Find My), all to no avail. And there’s no way to feed countryd
any custom data.
It’s insane.
This is disgusting.
It would have been easier to just remove these restrictions for everyone.
It's funny, because I've worked on and off in regulation for some of these companies. Leadership always wants a "scalable regulatory solution" and the answer is always "let's be more open" and leadership is always like "no"
It's actually not hard to be compliant with the laws of 220+ regions. It's just being on the edge of each and every restriction is more profitable.
$$$$$$$$
I heard somewhere they'd require a European bank card tied.
It's already trivial to get local banking details from many countries, (e.g., 'multi-currency' debit cards) but as far as I'm aware there's not a practical way to get a foreign debit card without the usual hoops that the full account would require.
Probably because demand for such a thing is low - I can generate disposable card numbers on the fly, but only from my home country. Can't imagine (aside from this specific edge case in question) generating foreign card numbers would be all that useful most of the time.
End-user support for such a thing would also be a challenge - I'm very accustomed to entering the usual data points with my card, but users would forget the associated postal code, or any number of other things, and then call support whining that it's 'broken'.
you'll also be able to switch to a different default for phone calls, messaging
Whoa, this is interesting tbh. I don’t think calls/messages is something they really expose at the moment for developers, do they?
Personally I don’t really care, the default apps are good and I don’t even know what you would want to replace the dialer for, but it’s nice that you can.
Imagine iOS getting the capability to have third party RCS messengers before (non rooted) Android though. Lmao
Google Voice, with built-in dialer, voicemail, etc., was useful once upon a time, from when they acquired GrandCentral (original company) up through a few years ago.
Not so much anymore, just recently ported out the last couple of numbers I was using them for. I don't see much use case for replacing the dialer, except insofar as the ability to do so has value in terms of freedom and open markets.
As a developer, you don’t really get access to any of that.
Mainly, you can’t access any history of calls and messages at all, nor can you automate sending one. All interactions with calling or texting has to be done with user interaction. Namely, calling requires the user to confirm the call, and sending a message requires the user to confirm, and they can also edit the message beforehand.
I don’t think that’s bad, given that messages are some of the most private things on our devices, and personally, I never had to use any of these or required more access. But more choice is always appreciated.
Was always curious why there was an extra step to confirm when making a call through the GV app. Not using it anymore, but I see the logic behind requiring that confirmation.
Sure, it has to be done with user interaction, but that doesn't mean it has to be through the stock apps, which is what the article says you will be able to replace here.
What I'm saying is, for this to actually work, they do have to expose these APIs to allow developers to write a custom dialer and messages app. I think the only thing remotely related there is right now is CallKit which is kind of the other way around (integrates non-phone calls into the stock dialer).