Well tattoo is ok but the 'dev tools app' doesn't work on it, which
prevents you from doing certain dev work
http://groups.google.com/group/android-developers/browse_thread/thread/9c57df28e4164737/b20202476f6b02f3

Dan

On Mar 11, 5:39 pm, Jim Blackler <jimblack...@gmail.com> wrote:
> If you want to see what your app looks like with QVGA (and appears in the
> Market for QVGA users) get a Tattoo. I strongly recommend developing on a
> low-end phone. If it works on that, it's all a bonus thereafter. Tattoo is
> currently on 1.6.
>
> To test (relatively) low RAM, and 1.6, get a G1.
>
> To test handsets still in the wild with 1.5, get a Hero. This will also help
> you test against Sense UI (HTC proprietary extensions). There are tons of
> Heros out there, and they have their own radio quirks so this is a useful
> phone to have.
>
> For the 2.*, slightly flaky radio (in my experience) and Motorola extensions
> get a Droid.
>
> For the LG extensions you could also get a GW620 but these are pretty rare.
> The LG handsets also have low RAM.
>
> For high res screens and 2.* there is of course the beautiful Nexus One.
>
> Re. versions of course you can flash anything onto anything but there is no
> substitute for the actual binaries consumers are using.
>
> This chart is a very useful resource:
>
> http://www.androphones.com/all-android-phones.php
>
> Jim
>
> On 11 March 2010 16:35, Yahel <kaye...@gmail.com> wrote:
>
> > Just to add a nuance here, any phone will do but some are noticibly
> > more prone to weird behaviors like the Motorola Droid for example
> > which for a lot of us is a nightmare but is one of the most used in
> > the US according to the statistics of "Radar Now".
>
> > So I'm not sure how to handle that, you should either just avoid it.
> > Will making your app works on the Droid automagically makes it work on
> > more standard devices(hero, magic) or will it break on those.
>
> > Just like when developing for the web, if you write your code against
> > IE then it will usually works on other browsers, but not the other way
> > around :D
>
> > I would think that the fact that the Droid has more constraints it
> > makes you write better, no not better, more compatible code across all
> > devices.
>
> > But just wanted to let you know.
>
> > Have fun coding.
>
> > Yahel
>
> > --
> > 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<android-developers%2bunsubscr...@googlegroups.com>
> > For more options, visit this group at
> >http://groups.google.com/group/android-developers?hl=en

-- 
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

Reply via email to