Why Developers Shouldn’t Use iCloud Syncing, Even If It Worked
Yesterday the Verge posted Apple’s broken promise: why doesn’t iCloud ‘just work’?
Here’s the thing: if you’re a developer, you shouldn’t use iCloud syncing anyway. I’ll explain.
Android and the web
You may think you’ll never want an Android or browser-based version of your app. But are you sure? Really, really sure?
You hope your app will be a hit. (If not, then quit writing it and choose something else.) If it’s a hit on iOS, it could be a hit on Android too — and you can bet that customers will ask for a web app version.
You don’t want to limit the success of your app just because you didn’t want to write your own server.
And even if you’re sure that you’ll never want an Android or web version, is it possible you’d want a Mac version that isn’t sold on the App Store? (Only App Store builds are allowed to do iCloud syncing.)
We’ve been living in a social world for years. But iCloud syncing is not social: it’s per-user syncing.
If you write your own server, you can write the social bits, so your users can share recipes, weather forecasts (look, Mom, it’s going to be sunny on Thursday!), favorite articles, or whatever-it-is your app does.
People expect social.
If you’re writing an RSS reader, you can’t ask iCloud to download feeds.
There are all kinds of services that make sense on the server side. You could do some of them on a client, but at the expense of timeliness and battery life. If it’s a good idea, and you don’t do it on a server, your competition just has to write a server that does it, and your app is finished.
Learning how people use your app
You shouldn’t look at private data.
With Glassboard we made the decision — there was no debate — to encrypt messages in the database, so that we couldn’t see private data.
But we could still look at aggregate data. It was interesting to know how many boards were created each day, how often people used invitation codes, and so on.
There’s no substitute for learning about how people use your app. You can guess how people use your app. You can — and should — get all the feedback you can via email, Twitter, and App Store reviews.
But seeing actual data makes a real difference, because it helps you figure out where your resources need to go.
It used to be expensive to develop, run, and maintain your own server. You’d buy a machine or a few machines, get them installed in a data center, figure out how Apache works, install MySQL, and write a ton of scripts. Perl or PHP scripts, most likely. (Ugh.)
You’d use Subversion (if you were lucky) or cvs. You’d write your own testing system from scratch. You’d write a bash script that copied the files up to the server.
And you’d spend a bunch of money.
Everything has gotten easier and cheaper. These days you’d run services on Amazon, Azure, Engine Yard, or Heroku. Or get a virtual server on Linode. You’d choose from one of the many excellent systems like Ruby on Rails, Sinatra, Node.js, and Django. You’d deploy via git or Mercurial.
If you can learn Cocoa, you can learn this stuff. (And so much of it is wonderful — you’ll enjoy learning it.)
Tim Wood, CTO of The Omni Group, tweeted the very wise words: Own the Wheel.
Here’s the thing: half the mobile revolution is about designing and building apps for smartphones and tablets.
The other half is about writing the web services that power those apps.
How comfortable are you with outsourcing half your app to another company? The answer should be: not at all comfortable.
Do it yourself.