On Thu, Oct 7, 2010 at 10:25 AM, { Devdroid } <[email protected]>wrote:> I do not care all of these, just most popular ones. > But then you're leaving out set of users, however small, that will be using the less popular ones. If you're concerned about "one less user" to support, you should cover all your bases, no? A generic solution that automatically identifies any of these apps on a user's device seems like the best solution to me, in terms of coverage and maintainability (what happens when a new task killer that becomes the most popular hits the market? You update your hard coded list and update?) > And what's the point? That's obvious - if at least one user understand the > warning and exclude my app, I will have one "it does not work" user less to > support. > Yes, the point of warning the user is obvious - the point of maintaining a list of select apps when you can programmatically identify them was not. Might just be me though. I do not like popups w/o the real reason, so such warning is already > built-in, but I want to throw it in the face if I detect task killer. > Not sure what "so such warning is already built-in" means, but a one time pop-up explaining the issues with task killers is probably the quickest and easiest way to convey the message. If nothing else you can use it as a stop gap until you come up with a real "solution". ------------------------------------------------------------------------------------------------- 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
