However your plugin cannot show a UI in the main app's activity. You can either use transparent activities with dialogs, so it just seems like a new window popped up (but not integrated into the main app's activity).
Well, in my case, the main activity needs to show popups over the plugin activity (or vice versa), and, without changing their Z-order, both be able to interact with user input.
What I'm thinking about is a car computer, where the basic framework is little more than an empty shell with a menu, esttings and so on. Then, things like navigation, SMS display, black box, media playing, dashboard instrumentation and so on would be plugins. That way, I could do, for example, a mean, lean media player, while someone else who was better at navigation did a kickass navigator. However, the media player control panel, SMS alerts, nav instructions and miniature dashboard instrumentation could, depending on circumstances, overlay any fullscreen activity. So, for example, if I have a movie going in the media player, the instruments could still be visible at the top, but if a nav instruction appears, the instruction would take their place. Likewise, if an SMS appears, it would pop up on top of any screen. If I switched to navigation, the media player control panel would still be accessible at the bottom of the screen. I think you get the point.
As it is now, it looks like it would probably be easiest to do as a single activity app, but, then I exclude other developers.
I just saw it as an idea for a fun community project. A common framwork, which everyone can plug into with cool functions (and trust me, the list of cool things to do with a car computer is long, very long).