During a client demo, I got stuck on an iPhone
Last Thursday afternoon, I was demoing my mobile web tool to a client in a Hangzhou café. Everything worked on my computer, but the client said, “I usually use an iPhone. Send me the link so I can see it on my phone.” I opened Safari twice and tested the page. Nothing broke, but I still felt uneasy: if I wanted to build a browser that didn’t depend on Safari, or even run a service in the background, would that path actually work?
I don’t have a technical background. I’d just realized that an apparently ordinary browser business could sit behind a wall of platform rules.
This Isn’t Just About Building Web Pages
Mozilla says that on iPhone, browsers other than Safari still cannot use their own core engine. A browser is more than a window for displaying pages; underneath it is a set of foundational capabilities for rendering the web. Mozilla argues that Apple’s long-standing restrictions have made it harder for iPhone users to choose alternative browsers and left web security updates dependent on Apple alone.
Who is already using these capabilities? Ordinary users use Safari to open web pages every day. Developers also rely on browser-engine capabilities Apple permits for sign-in, payments, and identity verification.
Take Chen Mo, an independent developer in Hangzhou. In November 2024, he used an iPhone to demo a back-office management system at a client’s office. Although he was using Safari, that didn’t allow him to move Safari’s core capabilities into his own browser.
Mozilla’s Firefox is a mature browser, but the same rule prevents it from fully using its own core engine on iOS.
What Would It Cost to Replicate This Path?
If I only wanted to build a mobile web page for a client, the prototype would cost roughly RMB 0–300 and take one to three days. The technical barrier would be knowing how to use mobile web-testing tools. The first step would be opening the URL on a phone and checking sign-in, payment, and page redirects separately.
Developing an independent browser engine would cost dramatically more in money and time. The public benchmark is tens of millions of dollars, a team of dozens, and several years of work, with specialist engineers forming a hard barrier. The first step wouldn’t be writing code; it would be confirming whether my business model could run using only the web capabilities Apple allows. Not every indie founder needs to tackle this, and it’s fine not to try now.
Here’s How I’d Choose by Stage
If I were just starting and didn’t have stable customers, I’d first build a web page that runs properly in Safari rather than rush into browser development. I’d spend one day checking whether clients were willing to pay.
If I already had one or two clients, I’d record the phones they used and their sign-in and payment flows before deciding whether iPhone-specific optimization was worth it. I wouldn’t spend big money on scale I was only imagining.
If I were scaling and preparing to make a browser or system-level service my core product, I’d first talk through the legal and platform-policy questions with advisers, then prepare for a long-term commitment. Beyond the engineering, there are App Store reviews and rule changes to account for.