I have been looking at the way that applications can cross-start classes, and so make themselves to some degree immortal. This behavior has been largely dismissed by the rationalization that the user will delete the program, but I think there is a middle ground. If a 'nag screen' was devised, for example, a trial copy of 'Bejeweled' could block the user from interacting for, say, five seconds.

The question I am having trouble resolving is whether this behavior can be prevented without clipping Android's wings. I think that greater permission granularity would help in this area, such as applications needing permission to re-start themselves, but that could be cludgy and put too much text at installation. If the user sees too many permissions to care, then our system will be useless and confusing.

All in all, I don't think this particular point will be regarded as a 'vulnerability', but it brings my attention to the question. Just thought people might like to share their opinions or hacks they've found, so that maybe someone will think of a way to really abuse the system. Think of it as a QA Exercise.

Better us now than advertisers later, right?