I sure hope this ties into Android's existing account management APIs. The one that already provides push notification support, automatic controllable data synchronization, etc.
Wow, not even 10 seconds and it's been shot at. What am I missing here?
I think Parse user management is aimed at a different use case. The AccountManager is a more heavyweight library that is useful for many complicated things. For example, if you are Facebook or Foursquare and you're implementing your own api for third parties to use and you want third party apps to be able to use your service's account, definitely use the AccountManager. Whereas the ParseUser is designed to be the simplest way to add your own user accounts to your application. They're both useful; use the right tool for the job.
Not only should it tie into the existing account management API's, but I can't figure out why they're offering their own push notification API when Android has one built in!!
We've heard from a lot of people who weren't happy with C2DM. We think our push API is easier to set up and use. It's also compatible with pre-2.2 Android and with Android devices that don't have an attached Google account. You can also can send push notifications to both iOS and Android with one API call. That said, if C2DM works for you there's nothing wrong with using it directly.
As a user, I'd certainly prefer for apps that I download to use the built in system functionality (like C2DM). One of the advantages of C2DM is a standard listener that used by all apps, rather than have multiple listeners (each potentially causing battery life impact). If the C2DM API is hard to use, it makes a hell of a lot more sense to write a helper wrapper around it, rather than add another listener.
No idea why you're getting downvoted. No application that uses their own push technology is as nice to my battery as C2DM is. Facebook and Twitter can't even get push notifications right, though Google refuses to put Google Voice through the push/sync that Gmail/Calendar/Contacts have. It makes no sense to me. It's there, it's easy to use, it's really battery friendly...
Comments
I sure hope this ties into Android's existing account management APIs. The one that already provides push notification support, automatic controllable data synchronization, etc.
Wow, not even 10 seconds and it's been shot at. What am I missing here?
I think Parse user management is aimed at a different use case. The AccountManager is a more heavyweight library that is useful for many complicated things. For example, if you are Facebook or Foursquare and you're implementing your own api for third parties to use and you want third party apps to be able to use your service's account, definitely use the AccountManager. Whereas the ParseUser is designed to be the simplest way to add your own user accounts to your application. They're both useful; use the right tool for the job.
Not only should it tie into the existing account management API's, but I can't figure out why they're offering their own push notification API when Android has one built in!!
We've heard from a lot of people who weren't happy with C2DM. We think our push API is easier to set up and use. It's also compatible with pre-2.2 Android and with Android devices that don't have an attached Google account. You can also can send push notifications to both iOS and Android with one API call. That said, if C2DM works for you there's nothing wrong with using it directly.
As a user, I'd certainly prefer for apps that I download to use the built in system functionality (like C2DM). One of the advantages of C2DM is a standard listener that used by all apps, rather than have multiple listeners (each potentially causing battery life impact). If the C2DM API is hard to use, it makes a hell of a lot more sense to write a helper wrapper around it, rather than add another listener.
No idea why you're getting downvoted. No application that uses their own push technology is as nice to my battery as C2DM is. Facebook and Twitter can't even get push notifications right, though Google refuses to put Google Voice through the push/sync that Gmail/Calendar/Contacts have. It makes no sense to me. It's there, it's easy to use, it's really battery friendly...