DreadCthulhu posted:

Any general advice, guidelines or guides for how to make your web api not suck over long stretches of time? The web app portion is easy, I can change that whenever and users will get the latest .js files in no time, but the mobile apps might lag behind by weeks if not months, depending on how aggressive the specific OS is about forcing updates (iOS really isn't at this point, not until iOS7).

So how do I start developing APIs that service multiple versions of clients with a 1-2 month margin of backwards compatibility? Test the API with oldest supported client version and newest version at all times, make sure it works? I know I'll figure it out through mistakes, but ideally I'd not not learn it the hard way.