On Thu, Mar 26, 2009 at 6:23 PM, Jean-Baptiste Queru <[email protected]> wrote: > > The problem with your reasoning is that it's far from obvious that > your hypothetical user will clearly understand that launching your > game will prevent their other apps from running (there's plenty of > evidence that users don't understand the consequences of their actions > as well as developers do). Of course, you'd like them to only care > about your game, but you can't assume that this will be the case for > everyone (and the situation gets worse if your game is really good and > they spend a long time playing it).
Not true. Just as the user understands if an application needs to read his contacts, and would deny it, if it's a flashlight application, he'll understand the permission, if explained in the user's language. Users, well, I hope most of them, are not imbeciles. They might not understand a lot of stuff, but you can explain them some things in an easy-to-understand language, and they'll grasp it. > > Please file a feature request for the no-GC feature so that we don't > forget about it. Sure, will do. > >>how is it possible for other apps to trigger GC in my process? > > The system asks every relevant process to GC at different points in > time, especially when it's running low on memory. That's not its only > tool - it can also flush caches or kill processes when that's > appropriate. Got it. > >>Is Android so aggressive about launching as few processes as >>possible, that it won't run my app in a new process, even if the # of >>running proceses is low? > > As a developer, you have control over the way the components in your > apps get spread into processes. If I remember correctly, you can split > an app over multiple processes, and you can have components from > different apps running in the same process. Even without caring about > that level of control, you can still be sure that your apps' > components won't run in the same process as app components from other > developers, since that'd break the entire security model. > > Android currently does keep processes around when it has enough memory > for it - there's a cost/benefit tradeoff, since an empty process takes > space, but having it around saves a lot of time if it can be re-used > to re-launch an application in it. Thanks for the clarification. Cheers --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
