On Wed, Aug 17, 2011 at 2:12 PM, Ryan Routon <[email protected]> wrote: > Some form of app dependency is what we were hoping > for, but it looks like there might be no way of actually implementing this > using filters.
Oh, how I wish we had a dependency mechanism on the Market. I suggested this once, and I think I still have the welts where Ms. Hackborn hit me. :-) > We are worried that the user will try to get the > downloadable content before they have the Engine app adding to confusion > down the line. Any ideas? This is totally off the cuff, so imagine a grain of salt approximately 23cm on a side, and take that grain of salt with this approach... Have the DLC have an activity in the launcher at the outset. That activity would see if the engine is installed. If it is, it calls startActivity() on the engine, perhaps with an extra saying "oh, BTW, they clicked on this piece of DLC". You could then, if you wanted, disable the DLC launcher activity via PackageManager, so it won't clutter up the launcher long-term. If the engine is not installed, though, the activity would say "o, hai, I can has engine plz?" and direct the user to the Android Market to get the engine. Personally, I'd want my DLC out of the Market entirely, whether using in-app purchases or some other means. But, lacking a dependency mechanism, something akin to what I described is one possible strategy. You might see how plug-ins work (e.g., Locale and its fleet of plug-ins), to see what strategies they employ in absence of a dependency system, as they will run into the same issue. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 3.9 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
