A story about an iPad browser that never was
When we founded Sky Balloon we endeavored to do one thing: make iOS (or, at the time, iPhone) software that we wanted. Because of that, after we successfully shipped our first iPhone app, Rhema, we decided to tackle something a bit more ambitious.
It was May or June of 2010 (I can’t remember exactly) and we were loving our brand new iPads … except for the web browser, Safari. While advancements had been made in terms of its speed, we felt it still lacked in features and experience implementation – or UI. So we had the brilliant idea to make a new browser for the iPad.
Actually, I should say, I had the idea, because I had no idea what it took to build software, and I figured we could do it. You know, with our three-man team that only met for a few hours per week. And because, after all, we were only going to be building a great “frame” around a UIWebView. And Apple already did the hard part by building the renderer. And, how hard could it be? Right?
It turns out that building a browser is curse-word hard, even if you don’t have to worry about the rendering of web pages. At the time, though, we didn’t know this. Well, maybe the other two thirds of our little company did. But they were brave enough to follow me and my naivety into battle anyway, despite their better judgment, and armed only with Xcode and some mockups I had whipped up.
The idea was that we’d create a browser that we would want to use, market to all our internet buddies, hopefully get featured on Daring Fireball or Macworld or MacBreak Weekly or TUAW or some other hugely populated website full of enthusiasts, be spotlighted by Apple as an example of innovation on the iPad (despite competing toe-to-toe with Safari), and make millions. Then we’d keep making apps and stuff. From our yachts.
Come to think of it, I’m not sure we actually had a plan. We just knew we wanted a better browser – one with the features I’m about to outline – and I had imagined one up.
We called it Breeze. Like, “this browser is such a breeze to use” or “wow, browsing with this app is so easy” or “honey, come look at these chumps who made a web browser like Safari and are trying to be cool naming it a one-word, nondescript noun”. The tagline was, “Browse more awesomely on iPad.”
I’m so embarrassed.
Oh, but the features. Check out these features.
First, we’d rid the toolbar of the two distinct input fields – only one omnibox-inspired location bar, capable of both search and URL input.
Next – and this seemed so obvious to us we were sure Apple would steal it for Safari – a history popover when you tap-and-hold the back button. This, as expected, was added to Safari later. We’re still uncertain how Apple hacked into our Dropbox accounts, but they somehow got their hands on the idea. (I think the guys suspect I was responsible, since I have some friends at Apple. But whatever.)
Of course, our UI was going to be cleaner and more refined, since, you know, I’m so much better a graphic designer than those hacks at Apple, Inc. So the polished UI was also to be a feature listed on the App Store description.
Now we come to the good stuff. Our tabs really were something to behol–oh, crap. I forgot, Apple added our tabs to Safari recently. Anyway, this is what they looked like:
Those were coded up, by the way. That’s not a Photoshop mockup. And you have to remember, back then Safari’s tabs weren’t tabs at all. They were a 3x3 grid view of web pages that often needed to be reloaded once switched to.
We only had three tabs shown in the view, but the tab bar was horizontally scrollable to allow for unlimited tabs. We also didn’t show the tab bar until there were two tabs. Gruber would (have) be(en) proud.
For our spotlight feature we were going to include, get this, a “reading mode”. Months prior I had discovered a bookmarklet for Safari on the Mac called Readability, that, when activated, would isolate just the text (and any relevant images) on a web page. We thought this was wonderful, and needed to be on the iPad.
Apparently, Apple thought it needed to be on the Mac too, because only a few weeks after we began development, Safari for Mac shipped with “Reader Mode”, powered by the Readability script.
Although we knew Safari for iPad would likely get Reader Mode, we thought we could either (1) get there first, or (2) do ours better. We designed a couple of really great themes for Breeze’s Reading Mode, and decided that, even if Apple beat us to the punch, our themes might be enough to hedge out a healthy and loyal user base.
Incidentally, I even got in touch with the company behind Readability (now a stand alone product and service), Arc90, and asked if they’d be willing to take a look at Breeze once we were ready to show. Rich Ziade’s reply was enthusiastic, and he agreed. (In hindsight, I’m pretty sure he was humoring me. Roles reversed, I would have.)
Then there were all the features we knew we couldn’t include in Breeze 1.0, but knew we wanted:
- Ad blocking
- Sharing modules (for social sites)
- Built-in child-protection and accountability
- User profiles
- Keyword URL support (m = gmail.com)
- Find on page
There were more, but I’m too embarrassed to share. (Okay, one was “Bing support”. There, happy?)
The sad part is that we really did get a lot of it built. In fact, by the time Apple finally shipped Safari with proper tabs we were readying a private beta.
Safari’s slow-but-steady evolution, coupled with the third-party browser market (which had continued to expand to include great apps like iCab and Grazing), made Breeze’s success harder and harder to imagine. We also realized that not shipping after about 14 months of development meant we’d bitten off more than we could chew. And by then the delusions of grandeur that said we could be featured by Apple, or even John Gruber & Co., had worn off.
We made the hard decision to abandon the project, at what we estimate was 75% in.
We learned a lot, though. Not just about iOS development, but also ourselves, the business of software, and about what we might be capable of if we didn’t have just a few hours per week.
(Also: I can’t wait ‘til you see what we’re working on now.)