I use the compatibility libraries for that. I have one app that will
work with Android 1.6 through 4.2 with newer features such as page
views. Look into those. I think there are a lot of people who would
like an Android phone but didn't want to pay over $100 for one. They
figure they won't be using the data features that much (just wait) but
still want them to be available as needed. I have a seperate version
for 10" tablets that uses Fragments and Action Bar.
Screen densities, however, are another problem because I think Google's
solution is broken. People with a Nexus 7 should be able to get my app
but it is filtered out. It seems to be filtered as an xlarge device
(which I have a nice tablet layout for 10" devices) when it should be a
large device. It's like they never thought about higher pixel densities
on smaller screens. They should be measuring by diagonal screen size
rather than by screen density. My 10 inch layout would be difficult to
navigate on a 7 inch screen.
On 01/06/2013 02:38 PM, Kevin Duffey wrote:
I should clarify.. when I say "works on 2.3.x how will it work on 4.x".. I
mean the layout.. what I am working on work on both devices.. but my
concern is that it looks good on both versions with missing some of the 4.x
ui/layout capabilities. I'd prefer to use fragments and action bars and
such for a 4.x release while obviously not being able to use action bars
and some other things that 4.x offers.
On Sun, Jan 6, 2013 at 2:29 PM, Kevin Duffey <[email protected]> wrote:
That may be so Brian.. and I thought of that as well.. 2.3.x was a
decent/stable version, and with the help of the backwards compatible code
from 3.x it's possible to do *some* of the code.. fragments in particular.
I'd guess even with those selling now, with so many contracts up in the
coming months and *most* of the devices coming with 4.x now, within a
year's time 4.x will be > 50%, possibly more of the market.
My only issue right now is if I write the app and it works on 2.3.x.. how
will it ALSO work on 4.x if my code doesn't use fragments and action bar
and such. I have a few 4.x and 2.3.x devices, so I will be testing it on
both + emulators to make sure it works right.. just hoping it doesn't
require me doing a lot of extra code to support both.
On that note.. is it possible to, at runtime, figure out the version and
use 4.x features, and if it's not, then use only 2.3.x features? I would
assume that since I target 2.3 - "latest" that compile time won't be an
issue.. although I haven't tried this approach yet. I am not having a fun
time assembling layouts with xml.. having done swing programming and web
layouts in the past.. I tend to lean towards building up my layouts with
code, not xml, so I am not bothered by some extra code that determines the
version it's running on and does layout code based on that at runtime..
just want to make sure I can compile and deploy one application that could
work in both cases, using either 2.3.x or 4.x capabilities at runtime?
On Sun, Jan 6, 2013 at 10:05 AM, Brian Conrad <[email protected]>wrote:
I have some customers who bought some of those inexpensive no contract
Android phones on sale during "Black Friday" and still under $80. Those
only have 2.3 on them and might not be upgradable to 4.x. I'm betting a
lot of those were sold and will continue to be sold. Most are "small
screen" displays too (ugh!).
On 01/06/2013 12:06 AM, Kevin Duffey wrote:
Pete.. that is what I was thinking... for me anyway.. given that I would
guess in a year or so 70+% of the market, if not more should be on 4.x
android, including pretty much all the tablets save maybe a couple %,
that
given that I am pretty sure my app won't be "polished" for at least 6
months before I can release it, I am leaning towards focusing on 4.0. I
suspect 4.0 will hold a share for quite some time, as a lot of devices
were
updated to 4.0.x but will probably get nothing much after that. Seems
most
devices last about 1 year of updates, if that, before carriers decide to
stop updating so that users will upgrade to newer devices so that they
can
keep making money off of the devices. It's a shame.. I can run android 4
on
my original droid from 2+ years ago.. it's not super smooth, but it
works.
There are many 1Ghz single core devices that could benefit from android
4,
but definitely a ton of dual-core devices that are apparently not going
to
get updates to it but could easily handle it. I blame the people (me
included) because most of us just have to have new shiny crap every few
months or so.. and the carriers know it.. so the majority of us just
can't
wait to upgrade to the next greatest thing! Shoot..I got an S3 and I want
the Note 2!!
On Sat, Jan 5, 2013 at 4:02 PM, Pete Perry <[email protected]> wrote:
Within 6 months it will have the lions share as the GB devices come off
contract.
Pete
On Jan 5, 2013 6:44 PM, "anatoly" <[email protected]> wrote:
There is support for multiple APK in the dev console and Google Play so
one is able to maintain multiple APKs and update all of them or the
most
latest.
On Friday, January 4, 2013 9:01:56 AM UTC+2, andjarnic wrote:
From what I can tell, it took about a year for Android 2.3 to push
out
Android 2.2 and 2.1, and it looks like Android 4, which I think hit
devices
around mid year, has moved up to about 27% of the device market
within 6
months.. so is it a safe bet that by mid year, more than 50% of
devices
will be running android 4.0 and later? I'd really like to have my app
focus
on android 4 apis, UI layout design, etc.. but with over 55% of the
market
2.3.x and below, I am just wondering if I plan for my app about 4
months or
so from now, if working on 4.x and later would be worth the risk.
--
You received this message because you are subscribed to the Google
Groups
"Android Discuss" group.
To view this discussion on the web visit
https://groups.google.com/d/**msg/android-discuss/-/**GojkPag51d4J<https://groups.google.com/d/msg/android-discuss/-/GojkPag51d4J>
.
To post to this group, send email to android-discuss@googlegroups.**
com <[email protected]>.
To unsubscribe from this group, send email to
android-discuss+unsubscribe@**googlegroups.com<android-discuss%[email protected]>
.
For more options, visit this group at
http://groups.google.com/**group/android-discuss?hl=en<http://groups.google.com/group/android-discuss?hl=en>
.
--
You received this message because you are subscribed to the Google
Groups
"Android Discuss" group.
To post to this group, send email to
android-discuss@googlegroups.**com<[email protected]>
.
To unsubscribe from this group, send email to
android-discuss+unsubscribe@**googlegroups.com<android-discuss%[email protected]>
.
For more options, visit this group at
http://groups.google.com/**group/android-discuss?hl=en<http://groups.google.com/group/android-discuss?hl=en>
.
--
You received this message because you are subscribed to the Google Groups
"Android Discuss" group.
To post to this group, send email to
android-discuss@googlegroups.**com<[email protected]>
.
To unsubscribe from this group, send email to
android-discuss+unsubscribe@**googlegroups.com<android-discuss%[email protected]>
.
For more options, visit this group at http://groups.google.com/**
group/android-discuss?hl=en<http://groups.google.com/group/android-discuss?hl=en>
.
--
You received this message because you are subscribed to the Google Groups "Android
Discuss" 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-discuss?hl=en.
