Perhaps they are not called shared libraries in Java but what I want is to write two separate applications, both available on the Android marketplace. Both applications would leverage a common set of shared code (perhaps a service, a set of classes, an activity, etc.). I want to be able to package the shared code with both APKs so the user doesn't have to install some base application first, then install one of the other two applications. However, if the user has one application installed I don't want them to run into any trouble installing the second application.
Also, how does versioning work in a scenario where the user installs application A, which contains an old version of the common code and then they install application B, which contains a newer version? What if they install B (with the newer shared code) first? My *hope* is that there is a way to provide a service with my applications that all of them can access via intents without having each application be required to spawn it's own copy of the service. -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
