I think you are correct. If there were official docs, this post would have been redundant.
You did say this exact same thing when Android was first released and the original Amazon methodology was shared unofficially ... and that worked for a good long time (longer than a few Android functions I've known). Shazam is using this right now. If future updates break it - they will break some pretty substantial apps integrating the architecture. Shifting sands ... functions turned to null. C'est La Vie. The life of an Android programmer ;-) If top-tier Market Apps are doing it, it seems to be accepting a significant disadvantage to refuse to compete with equivalent functionality because the future might require an app update. (See what happens when my questions about the ScheduledExecutorService leaking activities gets moderated into oblivion? I check my silly profile!) -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
