My company is working on an app that will be distributed outside of the Android Market. We plan to preinstall our app on devices and then loan the devices out to customers. We really want the ability to update our app completely automatically, without the customer having to do anything. I can see two options:
1) Use a custom ROM and give our app root permissions 2) Use OSGi Does anyone have experience using OSGi in an Android app? All of the discussions I've found are several years old. My main worries center around possible conflicts between the Android lifecycle and OSGi lifecycle. For example, would there be issues unloading a bundle that contained a layout and replacing it with a different layout? What happens if that layout is currently being used by an activity? I can see similar issues arising around Strings. Android is designed to update an application's components on app version changes; I just don't know if it's wise to use something like OSGi to bypass this process. I can see all sorts of potential for conflicts and memory leaks. What I'd really like to know is if anyone has successfully used OSGi to update Android specific things, like layout files and strings. Thanks for any help, Jesse -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
