Thank you Mark, that is what I was worried about... Does anyone know of any way to hide the downloadable content apps until the main app is installed? 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. 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?
Kristopher, I found this other thread: http://groups.google.com/group/android-developers/browse_thread/thread/1b78381b76bec33a/3b004c7ed2c2577a?lnk=gst&q=dlc#3b004c7ed2c2577a where Dianne Hackborn said to "Just look for the other package by name with the package manager. Ensure its cert is the one you expect to it can't be spoofed. If you want it to cary data about what features you are enabling or whatever, you can use <meta-data> tags under the application to supply whatever you want. " On Wed, Aug 17, 2011 at 10:26 AM, Kristopher Micinski < krismicin...@gmail.com> wrote: > On Tue, Aug 16, 2011 at 6:50 PM, Ryan Routon <ryanrou...@gmail.com> wrote: > > Hey Guys, > > > > 1. Quick question. Our company is exploring different ways to > > implement DLC and I see that there are basically two ways, using the > > in app purchase model with our own server pushing the "content" as is > > described here: > > > > http://developer.android.com/guide/market/billing/billing_overview.html > > > > 2. Or having the DLC offered as a separate app sold in the > > marketplace that we then use from our main app. > > > > My question is this, if we pick the second option can we use the > > <uses-library> filter to prevent the user from seeing the add-ons > > until they have the "main app" which would be the shared library we > > use to filter against? Are there any examples out there of others > > implementing DLC in their apps? > > > > thanks for any insight you might be able to offer, > > Ryan > > > > Ryan, > > If I understand correctly, you're implementing a main app which is a > framework for driving the other apps in your games. So your main app > is the game engine (or at least, something in that spirit), and the > other apps are the things that use the engine, is this correct? > > If this is true and you went wit the second option -- that level of > process separation, at least -- how do you intend for your game apps > to hook up to your main app? aidl? > > Kris > > -- > 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 > -- 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
