On Wed, Aug 17, 2011 at 2:12 PM, Ryan Routon <[email protected]> wrote: > 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. "
Nice, but, that doesn't really tell me what I wanted : ).. I guess my question was more, if you have two separate apps, what is the communication between them going to be like? If you write your engine code in a separate app, and have the games instrument the engine via rpc, don't you feel like that's going to be quite a bit of overhead? (Then again, the binder does seem to have fairly good perf, so maybe this isn't an issue.) Kris -- 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
