Yash Ghelani
banner
yashghelani.com
Yash Ghelani
@yashghelani.com
www.yashghelani.com
Reposted by Yash Ghelani
For a detailed breakdown of the MSCA and what it means for browser competition:

/5
open-web-advocacy.org/blog/japan-a...
Japan: Apple Must Lift Engine Ban by December - Open Web Advocacy
open-web-advocacy.org
August 6, 2025 at 7:25 AM
Reposted by Yash Ghelani
The act also forces Apple (and Google) to offer equivalent API access to third-party browser vendors, similar to Article 6(7) of the EU DMA.

/4
August 6, 2025 at 7:25 AM
Reposted by Yash Ghelani
This matters as Apple is still blocking rival browser engines in the 🇪🇺 EU, despite the DMA:

/3
open-web-advocacy.org/blog/apples-...
Apple's Browser Engine Ban Persists, Even Under the DMA - Open Web Advocacy
open-web-advocacy.org
August 6, 2025 at 7:25 AM
Reposted by Yash Ghelani
Apple will no longer be allowed to impose technical or financial barriers that effectively block third-party browser engines on iOS.

/2
August 6, 2025 at 7:25 AM
Reposted by Yash Ghelani
Reposted by Yash Ghelani
👉If the UK government is serious about supporting business, it must back the CMA in enforcing pro-competition rules decisively, especially when those rules are essential to giving startups and smaller companies a fair shot at innovation and growth.
July 23, 2025 at 11:49 AM
Reposted by Yash Ghelani
Functionality limitations in web apps stem from Apple’s own restrictions on web browsers, undermining their ability to compete with native apps.
July 23, 2025 at 11:49 AM
Reposted by Yash Ghelani
No Browser Engine Competition on iOS
July 23, 2025 at 11:47 AM
Reposted by Yash Ghelani
👉 Read all the details here:
open-web-advocacy.org/blog/apples-...

📺 Watch the video
open-web-advocacy.org
July 14, 2025 at 6:46 AM
Reposted by Yash Ghelani
“And for whatever reason, they have chosen not to do so.”

This is simply false.
July 14, 2025 at 6:46 AM
Reposted by Yash Ghelani
We asked Apple:

💬The DMA has been in force for 15 months. No browser vendor has ported their engine to iOS. Not because they can’t, but because Apple’s rules make it nearly impossible. Why is Apple insisting vendors lose their existing EU users? (abbreviated)

Apple’s reply?
July 14, 2025 at 6:46 AM
Reposted by Yash Ghelani
The DMA has been in force for over 15 months. Not one browser with its own engine has made it to iOS.

Not because they can’t. Because Apple won’t let them.
July 14, 2025 at 6:46 AM
Reposted by Yash Ghelani
Apple could solve this today.

They could let browser vendors ship two versions of the same app, one for the EU, one for the rest of the world, under the same bundle ID.

Apple just refuses.
July 14, 2025 at 6:46 AM
Reposted by Yash Ghelani
One barrier stands out most of all, Apple won’t let browsers update their current app to use their own engine in the EU.

Instead, they must publish a brand new app and rebuild their user base from scratch
July 14, 2025 at 6:46 AM
Reposted by Yash Ghelani
So what’s standing in the way?

🚫 Apple forces browsers to abandon all current EU user
🧪 No way to test EU browser features for global devs
✈️ No clarity on updates for EU users who travel
📄 One-sided legal terms and contracts
July 14, 2025 at 6:46 AM
Reposted by Yash Ghelani
This lets Apple control what web apps can do, and stops them from threatening the App Store. No other gatekeeper does this. Only Apple bans competing browser engines.

⚠️Vendors want to ship their REAL browser to iOS, not be forced to produce a separate one with Safari's engine.
July 14, 2025 at 6:46 AM