That all makes sense. I was under the assumption that my application could listen for said "pushes" and then create it's own custom push if the originating application was part of a watch-list. It seems that the Intents are required for this to work, and I think you're correct in assuming that not many applications do that.
Thanks On Mar 31, 6:19 pm, Mark Murphy <[email protected]> wrote: > Matt wrote: > > With all of your water pouring > > :: glug, glug :: > > > you mentioned not being able to > > identify which applications have notification services, but do you > > think there is a way to manually add applications to said list? > > I am not quite sure what you mean by this. > > Notifications are "push", in that an application has to have code in it > to raise a notification when something of interest occurs (e.g., > messages are waiting to be read/viewed/listened to). > > There are probably some applications that broadcast Intents about stuff > and do not show Notifications, where you might add value by listening on > those Intents and raising suitable Notifications. I cannot imagine very > many apps fitting that description, though. > > If I am misunderstanding what you meant by that, I apologize. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > _The Busy Coder's Guide to Android Development_ Version 3.0 > Available! -- 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 To unsubscribe, reply using "remove me" as the subject.
