Following Opera’s iPhone launch success, it’s Mozilla’s turn to negotiate Apple’s complex acceptance authorization.
Apple dictate stringent application development rules for their hallowed devices. There are too many to list here but, in essence, you must use Apple’s tools, stick to published APIs, not override default applications, not provide language interpreters, not create software emulators and do what you’re told. You can’t create a competing browser but Opera were accepted because:
- although it’s faster, Opera is not as seamless and more limited than Safari
- Opera adhered to the rules and publicised their browser’s submission. Apple had no reasonable arguments for rejecting the browser and knew there would be uproar if they did.
Mozilla has taken a different angle. According to their FAQ:
We do not have plans to ship the Firefox browser for the iPhone. Due to constraints with the OS environment and distribution, we cannot provide users Firefox for the iPhone. Firefox is available for other mobile platforms like Maemo and Android.
Instead, the organization has created an app called Firefox Home which lets you access your desktop browser’s history, bookmarks and open tabs on your iPhone. Effectively, it’s a one-way version of Firefox Sync (previously known as Weave Sync) which is available as an add-on but will eventually be integrated into the browser.
The Firefox Home page viewer uses the native iPhone Safari browser. However, it also offers the “Awesome Bar” (I still hate that name!) so you can access frequently-used websites with a few keystrokes.
On the face of it, there’s no reason why Apple should reject Firefox Home. The app could persuade users to stick with Firefox rather than try Safari on their home PC, but I doubt that would concern Apple. That said, Apple have rejected apps for more arcane reasons.
Will Firefox Home be accepted on the iPhone? Would you use it? Will Google and Microsoft be tempted to create similar iPhone apps? Please leave your comments below and cast your vote on the SitePoint home page.
Craig is a freelance UK web consultant who built his first page for IE2.0 in 1995. Since that time he's been advocating standards, accessibility, and best-practice HTML5 techniques. He's created enterprise specifications, websites and online applications for companies and organisations including the UK Parliament, the European Parliament, the Department of Energy & Climate Change, Microsoft, and more. He's written more than 1,000 articles for SitePoint and you can find him @craigbuckler.
Visual Studio Code: End-to-End Editing and Debugging Tools for Web Developers
Your First Year in Code