Right, because they provide the two things I stated: a default app on the other side that provides fairly liberal access to your schema, and a library that can be used on the client that provides a fairly reasonable API (maybe even CoreData integration; I know some of their competitors do this) to access that API.
Neither of these, however, are that complex to do, and the value of both of these drops dramatically once you start writing server-side logic in Java.
Comments
Except Parse is much more usable and more productive than AppEngine for regular folks who build mobile and web apps.
Right, because they provide the two things I stated: a default app on the other side that provides fairly liberal access to your schema, and a library that can be used on the client that provides a fairly reasonable API (maybe even CoreData integration; I know some of their competitors do this) to access that API.
Neither of these, however, are that complex to do, and the value of both of these drops dramatically once you start writing server-side logic in Java.