I can more strongly say that today, to be able to ship an Android compatible
phone (and thus have Market), you need to have a touch screen.

If/when at some point in the future devices without touch-screens are
considered to be Android compatible, appropriate work for existing third
party applications will be done, as we have done in the past: either having
some kind of compatibility so that they can still run with a decent
experience (as was done with the new density support), or applying filtering
so that those applications will not be visible to users until specifically
updated to support the new kind of device (as was done for example for
devices with smaller screens).

While making your app work well with a DPAD is nice, I don't recommend
developers go out of their way today to try to make a touch-oriented UI work
without a touch screen.  That time would be better spent on improving the
touch experience.

On Wed, Apr 21, 2010 at 1:20 PM, Zigurd <[email protected]> wrote:

> All current Android phones have touch-screens.
>
> However, Android's UI is designed to be operated using the d-pad,
> moving a "focus" and using a select button as well as by touch. I
> think all the standard apps that are part of most Android phones can
> work without touch.
>
> If, for example, you consider an Android in-car system with steering
> wheel buttons, or an Android TV as possible target platforms, you
> would want your apps to function without touch, too, and should
> include non-touch test cases in your test plan.
>
> On Apr 21, 6:06 am, Sean Hodges <[email protected]> wrote:
> > If you are a beginner, you should really be posting to the
> > android-beginners list.
> >
> > I believe all of the current Android phones have touch screens.
> >
> > On Wed, Apr 21, 2010 at 10:24 AM, [email protected]
> >
> > <[email protected]> wrote:
> > > Hi all,
> > >        a simple question from a beginner - how many of Android phones
> > > support touchscreen applications?
> >
> > > Angus
> >
> > > --
> > > You received this message because you are subscribed to the Google
> > > Groups "Android Developers" group.
> > > To post to this group, send email to
> [email protected]
> > > To unsubscribe from this group, send email to
> > > [email protected]<android-developers%[email protected]>
> > > 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 [email protected]
> > To unsubscribe from this group, send email to
> > [email protected]<android-developers%[email protected]>
> > For more options, visit this group athttp://
> 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 [email protected]
> To unsubscribe from this group, send email to
> [email protected]<android-developers%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
>



-- 
Dianne Hackborn
Android framework engineer
[email protected]

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" 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-developers?hl=en

Reply via email to