I'm inclined to agree with you. Waiting on Google to release a new system that won't even work with every platform seems stupid. A few other ideas I have are to increase the amount of time between updates (the idea being that less firings of the radio = less battery usage) or to have the server determine if there is an update. With the second option, the server does all the work and tells the phone to notify the user. Do you guys know how to go about this? Basically, to have the server send data to the phone to open an activity.
On Jul 22, 2:58 pm, TreKing <[email protected]> wrote: > On Thu, Jul 22, 2010 at 4:18 PM, KG <[email protected]> wrote: > > That was another major concern, how much will this suck the battery life? > > Depend how frequently you poll. Give the user the option to set the interval > they want, don't try to have a "never-ending" background service. > > > Also, do you know when C2DM is going to be released? > > When Google feels like it? > > On Thu, Jul 22, 2010 at 4:30 PM, Maps.Huge.Info (Maps API Guru) < > > [email protected]> wrote: > > C2DM is going to answer both these concerns, the bigger question is when > > will Google release it to the general developer community? > > Even bigger question: when will (nearly) everyone be on the same platform > version to actually make these new features worthwhile? > > OP: > > According the official platform versions chart, nearly half the phones are > still on 1.5 and 1.6 with absolutely zero indication that they will ever be > updated. So even if Google released C2DM, like today, and even if all 2.1 > phones updated to 2.2 tomorrow, you'd still have to come up with a backup > solution for that very large population of phones that can't take advantage > of these new features. > > If this background updating is central to your app, you're stuck either > eliminating a very large user base that doesn't support the C2DM feature or > rolling your own solution to be backward compatible which basically renders > the new functionality useless, unless you enjoy solving one problem two > different ways. Seriously, what's the point of all these fancy new features > if nearly half the people can't use them? > > IMO: Don't hold your breath waiting for Google to do anything for you - > whether it's been announced or not. If you want to support all platforms, > you're going to have to roll your own solutions regardless, so why waste > your time waiting around? Just do whatever it is you plan on doing now to > make your app work. > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
