Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Android allows you to loosely couple applications together with <code>Intents</code> and <code>ContentProviders</code>, so it should be possible to achieve what you're looking for. The hard part will be planning everything up front, so you have logical divisions of functionality (and so things plug together easily).</p> <blockquote> <p>I want to keep in the database the modules that are installed/present. So I must put sometimes the modules into database, maybe by detecting if there are present at launch time. The main app will work based on these modules.</p> </blockquote> <p>You can register a <code>BroadcastReceiver</code> for <code>ACTION_PACKAGE_ADDED</code>, which will fire whenever a new application is installed. Your main application should be able to use this to determine when additional modules are installed.</p> <blockquote> <p>In what format will I offer the modules?</p> </blockquote> <p>You probably want to still package the modules as apks so they can be uploaded to the marketplace. If you want them to not appear in the launcher (the app drawer), you can always remove the default &lt;intent-filter&gt; and the app will not be launchable (but still be removable).</p> <blockquote> <p>How do I have to create this using Eclipse?</p> </blockquote> <p>Your modules would still be standalone applications.</p> <blockquote> <p>How will the user add/remove modules?</p> </blockquote> <p>From the marketplace or direct downloads off of the web (if you want).</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload