I don't know how your app declares your activities, if they are public to be 
used by any other component/app installed on the phone.
Let's assume your activities are all private, then there is a way to deliver 
2 apps in one APK. You could do this by creating two separate code-paths for 
the 2 types of apps.


Set you min-sdk-version to the minimum (e,g 4 for 1.6) and 
target-sdk-version for 11 (Honeycomb).

Create a brand new 'Launcher' activity (you can make this one invisible). 
This activity will examine what the OS version is and it will start up the 
old root-activity of your app for 1.6 phones or start up a new activity 
tailored to Honeycomb for 3.0 devives.

You can either write brand-new code for every new activity for 3.0 devices, 
keeping it entirely separate (e.g. a sub-package) from your original 1.6 
code. 
If you decide to re-use code (utilities, data-object, even fragments (see 
posts by Dianna that talks about providing a Fragment library for pre 3.0 
devices)), make absolutely sure that this code won't blow up on 1.6 devices.



-- 
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

Reply via email to