Clockwork Updates

For a while now I’ve been collecting and publishing the iOS version adoption in my Audiobooks apps. Since the introduction of over-the-air updates in iOS 5 the rate of adoption by the general population has become extremely consistent. It seems as though Apple has the process of migrating the majority of their users to the latest OS within a few days down to a science.

I was curious how consistent adoption was over different releases so I took a look at the three most recent broad OS updates: 6.1.0, 6.1.2 & 6.1.3 (I didn’t consider 6.1.1 and 6.1.4 because they are only targeted to a single device). Plotting the adoption rate of these OS versions resulted in a rather stunning graph.

It looks like an OS update can now expect roughly 50% adoption within a week, followed by a gradual but solid growth thereafter. The consistency of this pattern appears remarkably stable.

While an interesting data point to consider on its own I think this is most significant in what it means for next week’s WWDC/iOS 7 announcements. It is widely rumored that Apple has significant overhauls planned for iOS both visually and functionally. If true, this could put developers in an awkward position where supporting older iOS versions will be particularly difficult.

Most previous major OS updates contained changes that were largely additive and served to expand what an application could do. However, iOS 7 may change the user experience so dramatically that having the same code work usefully in both contexts could become a daunting challenge. It is reassuring that adoption across compatible devices will likely be quick enough to make it feasible to go iOS 7 only. I wouldn’t be at all surprised if Apple encouraged this by pushing all their own apps to iOS 7 the day it is released.


If you are curious what the full adoption curves look like for the year-to-date. Here is the full chart.

David Smith




Feed Wrangler, The First Month

One month ago I launched Feed Wrangler. Feed Wrangler is an RSS aggregation platform that I’ve been working on since the start of this year. Google killing off Reader forced me to get my act together and actually ship the product. Here are some notes from the first month of it out in the wild.

Before I launched the aspect of it that I was most worried about was the price I charged. Charging $19/year is a level that I simply didn’t have much experience with before this launch. I am delighted to report that I’ve had little push back on the price. It seems like people generally accept that providing a stable, sustainable platform costs money and are willing to pay to support that. It is a welcome break from the cut-throat world of the App Store.

When I released Feed Wrangler the response I received was far stronger than I was expecting or hoping for. It was picked up by a number of sites in its first week and got a solid adoption right out of the gate. I’ve never built anything that was so difficult to scale out. Most iOS apps scale themselves to some degree. There is often some kind of backend you need to build out but previously for me this was never the core functionality.

Feed Wrangler is its backend. Keeping the feed scrapers scraping, the website loading and the app syncing turned out to be a much more nuanced problem than I had anticipated. The first week or two were full of late night server administration and frantic performance optimization to keep up with the demand. Though I can’t really complain, it is a delightful problem to have.

While completely exhausting this was incredibly interesting work. The most interesting part is the inter-disciplinary nature of the problems you have to solve. I’m not just sitting in Xcode writing Objective-C. I have to jump between low-level Linux kernel optimization, database tuning, application programming and visual design. This stretches you as a developer and can be painful at times but that is how you get better too.

It looks like Feed Wrangler’s next chapter will be focused on helping 3rd Party developers integrate with the API. The range of developers that are working on adding Feed Wrangler support to their apps is stunning. It looks like there will be great coverage across most platforms. While I can’t talk about specific apps quite yet, I don’t think anyone will be disappointed by the integrations coming soon.

Feed Wrangler has grown in its first month of life into something I’m rather proud of. I’ve been able to tame the technical growing pains and now find myself with a solid platform from which to grow. I look toward the July 1 Google Reader funeral feeling comfortable about my preparation for it and hopeful that I’ll be able to provide a smooth transition for my fellow news junkies going forward.


Some interesting facts about Feed Wrangler after a month of usage:

  • 67,457 RSS feeds
  • Which generate an average of 9,844 new articles each hour
  • The scrapers routinely sustain a combined 40Mb/s while pulling feeds
  • A typical user subscribes to around 65 feeds
  • The user with the most subscriptions watches 1,140 feeds
  • The most popular sites are Daring Fireball, Marco.org, TUAW, MacRumors, and MacStories.
David Smith




A History of Selling Out

WWDC 2008

Sold out in 62 days.




WWDC 2009

Sold out in 33 days.




WWDC 2010

Sold out in 8 days.




WWDC 2011

Sold out in 12 hours.




WWDC 2012

Sold out in 100 minutes.




WWDC 2013

Sold out in 90 seconds.




The iPhoneOS SDK was released March 6, 2008.
David Smith




» Human Intervention as a Competitive Advantage

The problem is when business owners see it as a cost, instead of an opportunity. Trying to minimize costs, instead of maximize income, quality, loyalty, happiness, connection, and all those other wonderful things that come from real human attention.

Derek Sivers wrote a great article that I think complements my Human Scale Problems discussion. It isn’t all about scale.

David Smith