On Thu, Mar 10, 2011 at 3:59 PM, Chris Stewart <cstewart...@gmail.com>wrote:
> You'd then need to maintain two sets of Activities in your code base (one > for each view, for each Activity), but at least you're simply implementing > functionality from your service layer in those instead of duplicating > everything if you happened to go with two completely different applications. > That was my initial thought at least. Does this make sense, or am I way > off in my thinking? http://blog.radioactiveyak.com/2011/02/strategies-for-honeycomb-and-backwards.html Relates to: http://android-developers.blogspot.com/2011/03/fragments-for-all.html http://android-developers.blogspot.com/2011/02/android-30-fragments-api.html http://android-developers.blogspot.com/2011/02/best-practices-for-honeycomb-and.html ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- 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
