Mobile Devs you can now have a single backend for your Android and iOS apps
techcrunch.com
techcrunch.com
What we mean by single backend is you can have one backend and you don't need to know whether you are on an Android or iOS platform. You get the same analytics. You get push sent by username without caring whether it's an Android or iOS. If you are curious to see how it all works read our latest blog post http://bit.ly/onEjgM
> What we mean by single backend is you can have one backend and you don't need to know whether you are on an Android or iOS platform. You get the same analytics.
I can't fathom why a backend service would ever not work this way.
EDIT: Has anybody ever actually used one of this cloud-hosted mobile backend services? Is it really any better than writing/hosting my own backend? Can it move beyond the trivial store-and-retrieve case?
To answer your other questions, I can only answer with my opinion. Obviously I've used some mobile backend platforms and I believe that they offer features beyond the trivial store and retrieval case. The obvious and biggest feature that comes to mind is supporting push notifications out of the box.
But there are a few more that at least StackMob provides, such as the ability to version your API out of the box, run multiple versions concurrently, have a sandbox environment in which to develop, have the option to extend the platform with your own code, and have good analytics for your app. We're always adding new features too.
As an Android & iOS developer before I worked at StackMob, I generally had to do some work to implement all of those things. We're aiming to build these things well so that any mobile engineer can use them and focus on building a great app instead of a great backend.
Hope that helps.