Looks like there is no obvious good answer. Comes back to personal taste. Personally I prefer to offer only one edition/version of my app to avoid confusing the user. Keep in mind as devels we're into this, but the regular user may not be aware of all the complications. Having a phone floating around in the pocket should remain a fairly low maintenance affair IMO.
Previewing 1.5 on your own server may not be such a bad idea after all. For the enthusiast. Set up a web site, include a manual and some more information such as a compatibility matrix. Of course you need to steer your users over to the site somehow. Happens I've set that all up (except for an 1.5-based release, has been "broken" by 1.5) and included a "More" button in the "About" dialog. On Apr 30, 8:54 pm, EboMike <ebom...@gmail.com> wrote: > Yeah, I did that, and I had to make minor changes to a TableLayout so > it looked right in an 1.5 environment. > > The real thing is widget support - I really want to add that soon. I > don't want to wait too long, at the same time I don't want to make the > app inaccessible to users with 1.1. I considered hosting the 1.5 > version on my own server, but that's plain whack. And adding two > versions of the app sounds a bit backwards too... then again, some > people add two versions of their apps. > > On Apr 30, 8:34 pm, JP <joachim.pfeif...@gmail.com> wrote: > > > My approach exactly. Plus I recommend you install your 1.1-based apk > > on the 1.5 emulator (or device) to see how it performs. > > Based on test results, I am preparing to release an 1.1-based update > > that disables access to a couple of features that I found crashing or > > hanging when running on 1.5 (BTW regardless whether the apk is a 1.1 > > or 1.5 build). > > > On Apr 30, 8:00 pm, EboMike <ebom...@gmail.com> wrote: > > > > I'd like to add widget support to my app, but I suppose that it'll > > > take quite a while until 1.5 is globally rolled out. > > > > I assume that widget support means that I need to compile against 1.5 > > > and set up the minSdkVersion to 3, so I'll effectively lock out > > > anybody with 1.1. Other than adding a second version of the same app > > > for 1.5, what's the best way to approach this? Wait a couple of months > > > until 1.5 is globally spread? (Assuming that all carriers even decide > > > to roll it out in the first place.) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
