If you are writing the applications (or otherwise over seeing it) it is not hard have communication between applications, you just have to read up on intent filters for the application's manifest.xml
Correct me if Im wrong, but you should be able to create an application that checks if the other applications in the suite are installed, which version they are etc... This app could also notify you of updates to existing applications and new applications. On your central server you can check the applications version number and refuse the connection if it is not up to date, then prompt the user to install the newest version. (either through the market or straight from the server. The browser sends .apk downloads to the application manager if I remember correctly) -theSmith On Jan 9, 9:46 am, Mark Murphy <mmur...@commonsware.com> wrote: > Eric Crump wrote: > > -Is it possible to push new applications to an Android over a socket > > and install it? > > Only if a user is at the phone at the time and can approve the > installation. SDK applications cannot silently install other > applications. The only way to have this happen without user intervention > would require firmware changes. > > > -How feasible would it be to have my service route communications to > > the appropriate application? That is, if the app is open, send it > > data, otherwise store it, ignore it, launch it, etc. > > That depends a lot on the "suite of applications". If you wrote that > suite, then it may not be that bad. If you are expecting to manage > arbitrary applications that way, I suspect few will be designed with > your architecture in mind. > > > -Can I build a service with a plugin architecture such that I can > > deploy new modules to it on the fly. > > In general, yes. In a secure fashion, not easily. > > > Would it have to restart itself? > > Probably not. You would need to download JARs or scripts (e.g., JRuby, > Beanshell) as your "plugins", and you can probably find ways to reload > those on the fly (e.g., use your own classloader for the JARs). > > You can't have a plugin architecture based on APKs very easily -- see my > response to your first question. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Android Development Wiki:http://wiki.andmob.org
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
