There was a recent blog post describing how you can use 1.5 APIs while
remaining compatible with 1.1.
On Thu, Apr 30, 2009 at 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
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
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
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
Actually... that's not a bad idea. Have the user install the 1.1-based
app from the market, and if the code detects the 1.5 API, it brings up
a dialog and offers an Cupcake version preview for download - that
will bring up a link to the dev's site with the .apk for download.
Downsides, of
On Apr 30, 9:47 pm, EboMike ebom...@gmail.com wrote:
Actually... that's not a bad idea. Have the user install the 1.1-based
app from the market, and if the code detects the 1.5 API, it brings up
a dialog and offers an Cupcake version preview for download - that
will bring up a link to the
6 matches
Mail list logo
