Bad sides of C2dM

Question

We all know that as of Android 2.2 a push notification system exists (C2dM). However, I do not see many developers using it. In my next project I plan (hope so) to use this system. So before I dig into it, I would like to know what are the bad sides of it? Why people do not use it?

It can't be just because of incompatibility with systems older that 2.2.

Answer 1

Nice question. Here is my 2 cents :

1. C2DM is still in beta
2. There is a limit on the number of messages you can send. If you need to send a large number of messages, then you need to explain it to Google and get it approved.
3. The device must have Android market with one google account signed in.
4. The documentation is a bit flaky [My personal opinion]. e.g. The signup form asks for the app package name and the ROLE account ID on the same page providing wrong impression that once signed up, the package name is bound to the ROLE account ID and can only receive messages from it.

I don't think people are not using it. Rather I find most developers are very much interested in it and are implementing it. My C2DM post has the most visitors of all my posts.

However the problem might be for individual developers who develop stand alone apps. They may be reluctant to use it since they will require to maintain a server side component to push messages.

[Will update my ans. if I find anything else.]