[rickdeckard]

Beside of the fact that App-Developers don't have the option to "stay on iOS18 or switch to Android", that statement is equivalent to "Stop criticizing my country. If you don't like what it is doing, find yourself another country".

Developers (and users) are citizens of that ecosystem, serving other citizens and contributing to its economy. It is their right to judge and criticize directions being taken.

The owner of that ecosystem must endure and acknowledge this (especially when he continuously makes efforts to increase the difficulty to LEAVE that ecosystem), and other citizens should not take any offense from this at all.

[nozzlegear]

> The owner of that ecosystem must endure and acknowledge this

Do they need to acknowledge it? Ecosystems aren't countries, they're markets, and citizenship doesn't exist here in the same sense – only participation in the ecosystem. Maybe there's some EU chicanery that makes it illegal for American companies to ship a UI that's displeasing to European tastes, but if we pretend that Apple is strictly an American company, would they need to acknowledge this at all if it didn't affect sales?

[rickdeckard]

I'm not sure we have the same understanding of "acknowledge". Apple can acknowledge criticism and still decide not to act on it.

The rest of your comment I don't understand, sorry.

[nozzlegear]

> I'm not sure we have the same understanding of "acknowledge". Apple can acknowledge criticism and still decide not to act on it.

We do, but what I'm suggesting is that Apple might exercise a third choice, which would be ignoring the criticism and pretending it doesn't exist if they don't think it will affect their sales.

[rickdeckard]

That argument is moot, because it's not a third option. Apple won't release iOS 26.1 rolling back any of this. Their path is set, they will tweak forward only.

Towards developers they will apply "acknowledge and ignore" as the communication strategy, towards users they will continue to express the usual confidence to know best what he needs, because that's what their users like and that's the only thing they can do now anyway.

In a grander scheme of things, Apple needs to prepare a transition of their locked-in userbase to AR, because there is a risk that AR replaces the smartphone and their users move away from Apple then. So they have to transfer the stickyness of iOS to AR before that happens, to have a ecosystem headstart against all competitors.

The actual interest of users and developers are secondary, they need to smoothly transfer them to a new world without alienating them too much. The only way is forward.

[nozzlegear]

Agreed, I think we're saying the same thing. Apple's already made up their mind on it and they're going to ship it no matter what at this point. To admit that it's not the best design for non-AR devices, whether rightly or wrongly (I personally don't mind it), would be to admit that their overall strategy is flawed.

[nancyminusone]

But for some reason, discussions of parts pairing, side loading, and app store fees tends to steer towards the "use a different phone, bro" argument.