When Can I Cut the Cord on iOS App Development?
At Çingleton, Craig Hockenberry spoke about where he saw the future of mobile computing. One gaping void in his talk was a topic of incredible interest to those present: development. iOS is still utterly dependent[1] on a Mac OS X counterpart for full lifecycle app development. I was reminded of both the Newton and the early Macintosh systems.
The early Macintosh couldn’t self-host a development environment. You developed Macintosh applications on a Lisa and installed them via a serial cable. It wasn’t until late 1984 or early 1985 that proper developer tools were made available for Macintosh computers.
The Newton, with the exception of NewtonScript (made spectacularly manifest with NewtDevEnv), was never fully untethered in terms of development.
Now, with apps like Keynote, Pages, Numbers, and Garage Band[2] pushing the limits of what the iPad and iPhone can do locally, coupled with a (mostly) transparent networked storage layer and binary diff delivery, I think I can see a future where self-hosted iOS development is possible:
Taking a cue from Xcode 4, we’d have a singularly focused interaction model with the emphasis on building the UI elements from palettes and inspectors. A robust and richly appointed code editor handles all the tedious typey-typey, while all of the project’s files are hosted on and fetched from an Apple-branded site on top of iCloud, backed, naturally, by the distributed version control system du jour. Compilation, presumably the gating factor on an iOS device, is done remotely in Apple’s data centers, and incremental binary diffs are sent back down to the device, removing unnecessary network overhead. Codesigning and team testing deployment are handled in a model not unlike TestFlight or HockeyApp, tied into iTunes Connect and the Provisioning Portal.
Some people are finding interesting ways[3] of using an iPad for their sole machine. I’d like to share in that future with iOS development.
-
Although projects like Codify and Fusion look incredibly promising for some programming tasks. Thanks to Matt Johnston for pointing out Fusion.
-
And numerous others. For a growing list, see Fraser Speirs’ Ambitious Apps project.
-
Thanks to Mike Shields for bringing this to my attention earlier today. It prompted me to write this.



