No, I'm not disputing those numbers at all.
What I meant is - it wasn't a weird phone made by a fringe manufacturer.
The phone a Motorola Backflip - AFAIK, it still runs 1.5 outside the US,
and the 2.1 update in the US was not an OTA, so perhaps not everyone who
could update actually did.
I think the only major phone in the US still on 1.5 is the CLIQ XT
(the one with the keyboard) and there should be an update for that one
as well soon.
I put a very large warning on top of my What's New pop-up that comes
up with every release warning users and to e-mail if they are on 1.5
and
Hi,
I still have an (non carrier branded) HTC Hero (gsm version) with
V1.5, it is from a different region than me, it has only been offering
an OTA update to V2.1 just in the last few weeks. Anyway some users
may never be in a position to update from V1.5 even if its available.
Regards
On Jan
Hi,
No you are not obligated by the Distribution Agreement regarding
support or updates by my reading.
I just interpret some of it as suggesting that support of your apps is
desirable. And Dianne mentioned stuff that I was not aware. ( Nothing
could be supported for perpetuity ;-)
Version 1.5
That cannot be right. That would mean you have to forever support
every version of Android. And does the Distirbution Agreement talk
about having to give the users updates and supports for perpetuity? I
doubt you are even required to give even a single update to your app.
On Jan 19, 2:49 pm,
Why isn't it documented clearly somewhere? Because Google still
believes in that strange myth they got caught up in while designing
their entire development philosophy for Android (and what else?):
throw up early-alpha code and let the community document it for Google
in blogs and mailing lists
Nor is this the only reason we should not put TOO much faith in the
dashboard. There are other reasons that sampling might be skewed.
That said, I am no longer so interested in maintaining 1.5 users
either, since even if the dashboard figure was off by 100%, there just
aren't that many 1.5 users
You say, I believe. But as TrekKing already implied with his
question, this is important enough that it should be documented
somewhere without such a cautionary qualification -- if it is in fact
true. And if it turns out not to be true, then you should post a
follow up to your own comment
This is interesting: according to the dashboard, less than 5% of
individual phones connecting to the Google Android Market are still
running 1.5. Yet you call that 1.5 phone, a certain quite popular
phone.
How could this be? I am curious to hear how either 1) the dashboard
sampling could be that
On Wednesday, January 19, 2011 6:49:12 AM UTC, gjs wrote:
I'd also suggest rereading the Android Market Distribution Agreement
if you are withdrawing V1.5 paid apps your support for them -
particularly given Dianne's comments about just bumping minSDK old
versions still being available.
http://developer.android.com/resources/dashboard/platform-versions.html
You can target 1.6 and still enjoy the speed boost of 2.2 if that's the
version you are running on...
Unless you are using Version-Specific API calls, I would try to target
the lowest version possible (but not lower than
How does the analytics API handle offline scenarios? is it possible to store
all the interaction of the user offline, and post it in a single bulk
request to the analytics server?
I know they support bulk submission, but the API states that the entire bulk
will be registered with the same time
Hi,
I'd also suggest rereading the Android Market Distribution Agreement
if you are withdrawing V1.5 paid apps your support for them -
particularly given Dianne's comments about just bumping minSDK old
versions still being available.
I think you may still have to provide refunds under some
Hi,
I still like targeting V1.5 because it lets you artificially limit the
screen resolution on higher res devices - for a free version of your
app.
And then charge for your V1.6+ version with the supported device
resolutions.
Regards
On Jan 19, 5:49 pm, gjs garyjamessi...@gmail.com wrote:
I'm not your app user, but I'm curious about this situation. Will 1.5
users be able to download your current app version in the future or
will it just dissappear? I always wondered about what happens when one
decides to stop supporting old Android versions. It would be good if a
version for 1.5
That's a good point. Current 1.5 users would still need to be
redownload the app for whatever reason. I might release a version for
Android 1.5 users only and never update it.
On Jan 17, 6:00 pm, DraganA dand...@gmail.com wrote:
I'm not your app user, but I'm curious about this situation. Will
For my own apps, I don't have a problem supporting 1.5, and I figure that an
extra 5% is nothing to sneeze at. But then, I've yet to run into anything
that was really problematic for me to support on 1.5. Some of the resource
handling is kind of annoying, but not really a big deal.
If I had
On Mon, Jan 17, 2011 at 7:07 AM, String sterling.ud...@googlemail.comwrote:
For my own apps, I don't have a problem supporting 1.5, and I figure that
an extra 5% is nothing to sneeze at. But then, I've yet to run into anything
that was really problematic for me to support on 1.5. Some of the
I've been tempted to drop 1.5, partly because it tends to be installed
on low-end devices where people will not have a very good experience
of my app, but recently my percentage of 1.5 users has gone up instead
of down on some apps.
There's a big difference between dropping (loyal) 1.5 users and
Is there a site that shows the number of users for each version?
I'd rather target 2.2+ now.. just because its the version that brought in a
big speed boost, making a lot more apps much smoother. I still have the
Droid 1 and I thought that was one of the lower end devices out there? Being
that
Is this what you are looking for?
http://developer.android.com/resources/dashboard/platform-versions.html
--
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
I recently ran into some 1.5 issues with my widgets that were caused by a
certain quite popular phone that still runs 1.5 ignoring @dimen values.
So supporting 1.5, understood as some kind of pure Platonic form, is no
problem at all, but dealing with bugs in particular firmware versions is not
Not absolute numbers, but rather percentages, can be seen here:
http://developer.android.com/resources/dashboard/platform-versions.html
-- Kostya
2011/1/17 Kevin Duffey andjar...@gmail.com
Is there a site that shows the number of users for each version?
I'd rather target 2.2+ now.. just
Indeed. Good info to have. So looks like 2.1+ is the target.
On Mon, Jan 17, 2011 at 7:19 AM, Laks laks.pendy...@gmail.com wrote:
Is this what you are looking for?
http://developer.android.com/resources/dashboard/platform-versions.html
--
You received this message because you are
I started development during 2.1 so i never went there.
I'm moving all new code up to minimum 2.2 because thats were 60% of my
customer base is.
That said, I'll support the one app I have thats 2.1 for as long as I
have greater than 10% users.
On that note. It's bogus that the Market doesn't give
Its shameful, but the Market doesn't give us any useful data on that
(which makes giving quality product a problem).
I got my data through AppBrain, but its certainly not ideal.
There is a lib for Google Analytic, but I looks a bit chunky, so I
haven't tried to use it yet.
- Brill Pappin
On Jan
Thats fine, but doesn't give you any stats on your own app, which is
very important for maintaining customer loyalty.
We intend to make the company a truste name (not just the apps) in the
market with quality product, so we really want to know what *our*
users are doing.
- Brill Pappin
On Jan
My stats are from Google Analytics. If you use it and explain what you
are doing in your terms of service or license agreement, you are
likely to get at least a few comments from users who think you are
spying on them, but in some cases it is worth it because you have a
better picture of how your
On Monday, January 17, 2011 3:27:02 PM UTC, Kostya Vasilyev wrote:
For now, both my apps continue to support 1.5, but a new project I'm working
on will only run on 1.6+ - because that's the first version with
multi-resolution support, and one really needs that these days.
What are you doing
I'm using @dimens quite a bit, not because I have different values for
different screen sizes / resolutions, but because it lets me tweak my
layouts more easily during development.
After seeing them not work on a certain 1.5 device (even though that's part
of API level 1), I've decided that the
By @dimens do you mean the dp unit in layouts?
If there is something not working on a device, we'd like to know about it
because it is not compatible with the CDD which is a requirement for having
Market.
On Mon, Jan 17, 2011 at 9:40 AM, Kostya Vasilyev kmans...@gmail.com wrote:
I'm using
Oh and I believe on Market that if you put up a new version of your app with
a higher minSdkVersion, the most recent older version will still be visible
to older devices. That is, the .apks you upload are never deleted; a new
version just supersedes an older one for the devices it is compatible
No, I mean defining a value like this:
dimen name=some_value140dp/dimen
and then using it like this:
RealtiveLayout . android:layout_width=@dimen/some_value
I used this for widget sizing, and had a default fallback dimens.xml in
res/values (without alternate qualifiers).
Based on my
On Mon, Jan 17, 2011 at 12:18 PM, Dianne Hackborn hack...@android.comwrote:
Oh and I believe on Market that if you put up a new version of your app
with a higher minSdkVersion, the most recent older version will still be
visible to older devices. That is, the .apks you upload are never
Holy crap - why is awesome information like this not clearly documented
somewhere!? (Or is it ...?)
You crystalized my thoughts...although I usually find I just didn't
read the documnetation deeply :)
--
You received this message because you are subscribed to the Google
Groups Android
That's strange, I don't see why that wouldn't work. This is the code in
1.5:
http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=core/java/android/view/ViewGroup.java;h=e686d1c20bd21eaa050ff3bf9187b549ee7b1355;hb=refs/heads/cupcake-release#l3319
Which boils down to:
On Jan 17, 11:33 am, Ken H hunt1...@gmail.com wrote:
Holy crap - why is awesome information like this not clearly documented
somewhere!? (Or is it ...?)
You crystalized my thoughts...although I usually find I just didn't
read the documnetation deeply :)
This was news to me too, and I swear
FWIW, I had the same experience, now that you mention it. Using @dimen
references in widget layout XML doesn't work on 1.5.
Bit of a PITA, but I just went ahead and created a few more layouts (rather
than resizing them based on dimens) and moved on. It didn't seem like a big
enough problem to
Huh. Well it could well be, that was so long ago it is hard to remember. :}
On Mon, Jan 17, 2011 at 2:42 PM, String sterling.ud...@googlemail.comwrote:
FWIW, I had the same experience, now that you mention it. Using @dimen
references in widget layout XML doesn't work on 1.5.
Bit of a PITA,
39 matches
Mail list logo
