> This is genuinely tricky due to battery life and data usage considerations.

Which isn't really any of Apples business if I want to make that sacrifice, but rather something they can promote as a win by using their solution if it turns out that alternative push notification services implement it poorly.

If I take Apple's goodwill (which in this specific case to me is plausible, but whatever ...) the issue with alternate notification channels is that it's quite tough to attribute for users if there are 10 push daemons doing it their way. But the bad press about bad battery life time hits Apple.

Especially if Apple allows others to move it from application layer to system layer (by providing a Kernel interface?) which is required for being really energy efficient.

They already have annoying modals that pop up when apps are using my location in the background, they could easily make these hypothetical "NotificationServiceKit apps" spawn similar modals when they take up a lot of CPU time, memory, or other energy intensive metrics.

Having sane, common sense defaults is pretty much exactly Apples business.

The path you propose inevitably leads to the exact enshittification we’re trying to avoid.

But it's optional enshittification. I should have the option of messing up my device. Apple are free to scare me away from doing so, but the choice needs to be mine as the owner.

Then buy an android if android is what you want.

Stop trying to turn the system WE want into what WE don't. WE don't want android or else we would already be using it.

As soon as you fracture the ecosystem the positive network effects start to fade.

How do I get iMessage on android? If you want the locked down system just dont install 3rd party app stores.

>Push notifications

It is far fetched that it will get any industry wide traction, but unifiedpush.org/ provides a solution