That will allow you to browse the declared Activities, but you still do not have a reference to them - you simply have their class name. There could be any number of instances of said class.

Maybe I should back up a little.... To show a Dialog explicitly, you need an activity reference. This is going to be tricky if not impossible to obtain just via library code. There are a couple ways you could do this if you're willing to tell the user to add a bit of custom code to their activities - namely to handle some sort of Intent, bind to your service, or to keep registering Activity instances when they spawn new ones. Of course, this is probably less than ideal at this point since you have people already using AppBlade and you don't want to change the API on them.

Alternatively, you can keep a reference to their application context and start your own Activity instead of the dialog (you can specify your Activity is opened over other things, effectively the same as a Dialog) and show the prompt and anything else you may want from there. The issue with this is that the user may have navigated to another application, and popping up over other applications is far from user friendly. Trying to determine whether you're the currently focused app is, again, very dirty/tricky unless you can convince the user to modify all their Activities. Again, not idea.