If you DO care about this, implementing this regulation as is will only make the software worse, not better. Apple did a good job so far keeping developers in check.
I think Apple users are underrepresented here, more developers here.
- Any case where Apple builds a competing product and charges a cut to the competitor that makes them structurally unable to compete is blatantly anti-competitive, i.e. Spotify vs Apple Music - Any case where the margins of the business do not support Apple's 30%, i.e. Kindle (let me buy my damn books in the app) - Any case where Apple has prohibited something for seemingly no reason, i.e. game emulators till about a month ago under regulatory pressure - Any case where Apple's unilateral control of pricing meant that certain business models couldn't be tried, i.e. subscriptions for a long part of the App Store's history, upgrade pricing today etc - Any case where Apple has prohibited anyone from competing with it. iOS Safari is bad and Apple has insulated it from competition by prohibited third-party browser engines. Note this hurts both users who'd rather use Chrome or Firefox and users who use Safari who don't benefit from Apple having to compete.
I don't disagree that there are benefits to Apple's approach. I just think that they should be heavily scrutinized because of iOS's import.
Allowing engines while sounds good, in today's reality will result in absolute Chrome (Google) domination. They will be setting web standards unopposed. And they are an Ad company. So again, this is good for me.