What Evo should have been

[6tr6tr]

I really dislike the buttons on Android phones (and the iPhone) and don't understand all the wasted space for buttons when screen buttons would work just as well. Especially since NONE of those buttons work when the screen's off anyways. So....

(It's the one on the left ) Click the thumbnail to see full size pic.

 

[gibsonhtp#IM]

I really dislike the buttons on Android phones (and the iPhone) and don't understand all the wasted space for buttons when screen buttons would work just as well. Especially since NONE of those buttons work when the screen's off anyways. So....

(It's the one on the left ) Click the thumbnail to see full size pic.

Go from a 4.3" screen to a 4.5"....I could go for that. Though for me, I like having those particular buttons there for anytime access.

 

[6tr6tr]

Go from a 4.3" screen to a 4.5"....I could go for that. Though for me, I like having those particular buttons there for anytime access.

Yes, but that could be handled by the UI. The UI could be redesigned to put those buttons at the bottom and make that space unusable by apps (but make them look better than the current ones). But you'd be able to give the user the option to minimize those buttons if needed.

 

[gibsonhtp#IM]

I completely see where you're coming from, though all in due time, there's so many people that still feel the need for physical buttons, even though these are just touch sensitive "buttons" hehe.

 

[Septro]

With taking up so much of the bottom portion of the phone is not really practical, since you would most likely hit the screen with inadvertent touching just holding the phone. Think about where you rest your thumb when holding the phone with one hand to read/view it.

 

[6tr6tr]

With taking up so much of the bottom portion of the phone is not really practical, since you would most likely hit the screen with inadvertent touching just holding the phone. Think about where you rest your thumb when holding the phone with one hand to read/view it.

When I hold my phone or my iPod Touch in one hand, my thumb is on the side of the device (and my fingers behind it and finger tips on the opposite side). I have no idea how you hold it with your thumb at the bottom - I tried it and it is very precarious.

Besides, if a thumb on the bottom was a problem, then the buttons on the current Evo (and Droid) also wouldn't work since they also respond to touch.

 

[glamisfanatic]

I think the only needed key is the home button. Maybe an end call button too. I have a Pre and I hate that it takes me a few presses of the on screen end call button to hang up. Its annoying. I don't know if thats the case for android, but its made me want a few hard keys

 

[cesjr02]

When I hold my phone or my iPod Touch in one hand, my thumb is on the side of the device (and my fingers behind it and finger tips on the opposite side). I have no idea how you hold it with your thumb at the bottom - I tried it and it is very precarious.

I might be wrong but I think Septro meant if you turn your phone in landscape. A very natural way of holding my phone, or ipod touch like this is between my thumb and index finger.

 

[Droid800]

I think the only needed key is the home button. Maybe an end call button too. I have a Pre and I hate that it takes me a few presses of the on screen end call button to hang up. Its annoying. I don't know if thats the case for android, but its made me want a few hard keys

Doesn't google require something resembling those buttons? I know a home button is required, I think the search might be, and the back as well.

Its nice to talk about removing the hardware buttons, but seeing as how Android isn't built to NOT have them, it would be difficult.

 

[6tr6tr]

Doesn't google require something resembling those buttons? I know a home button is required, I think the search might be, and the back as well.

Its nice to talk about removing the hardware buttons, but seeing as how Android isn't built to NOT have them, it would be difficult.

It's not required and Android allows you to alter it (the UI) as you see fit for your device - hence the SenseUI in HTC's devices. And have you seen the guy who put Android on the iPhone? He's mapped it to the iPhone buttons.

 

[yazman666]

If the bottons are include in the sense runing on the device will not be bad at all after all i barely use the bottons right now bot those same bottons could easily be included on the rom ...i guess we will get there so far nobody has taken the step because for some reason everybody loves bottons instead of raimond this time...

 

[6tr6tr]

If the bottons are include in the sense runing on the device will not be bad at all after all i barely use the bottons right now bot those same bottons could easily be included on the rom ...i guess we will get there so far nobody has taken the step because for some reason everybody loves bottons instead of raimond this time...

Does everyone love/prefer hardware buttons? I've yet to see any study on this. I'm not convinced that people would really prefer them if shown the same phone with a larger screen and software versions of the buttons instead.

 

[dwhitman]

For me, it profoundly depends on whether there's any lag.

The beauty of a hardware button is that you get immediate tactile feedback on whether you actually hit it. An on screen button sacrifices that, and typically replaces it with visual feedback - inverting the color, etc. IF the phone is fast enough to ALWAYS instantly give at least some form of visual feedback to button presses, I think on-screen buttons are fine. But any delay, even occasionally, builds some uncertainty into your mind, and you end up waiting to see if something happens, or hitting the button twice.

 

[6tr6tr]

For me, it profoundly depends on whether there's any lag.

The beauty of a hardware button is that you get immediate tactile feedback on whether you actually hit it. An on screen button sacrifices that, and typically replaces it with visual feedback - inverting the color, etc. IF the phone is fast enough to ALWAYS instantly give at least some form of visual feedback to button presses, I think on-screen buttons are fine. But any delay, even occasionally, builds some uncertainty into your mind, and you end up waiting to see if something happens, or hitting the button twice.

Agreed 100%. Here's my experience:

* Droid: tiny bit of occasional lag, occasionally needs extra button press

* iPhone/iPodTouch: 99.5% of the time, it's perfect. I can have a list and quickly slide my finger up and down and it's perfect 99.5% of the time.

* iPad: PERFECT. (I really dislike Apple, but DAMN they make a good tablet)

* Palm Pre: Is never perfect, has definite lag and sliding my finger up/down on a list has very noticeable lag and loss of movement.

So obviously, you'd need iPhone/iPad quality, but clearly it can be done. And the amazing thing? The iPhone/Touch I used both had a 600 MHZ processor!!

 

[Andrew Ruffolo]

I had lag with the iPad in the store with just about everything. I found an ipod touch to be more responsive (i know that makes no sense on paper).

 

[6tr6tr]

I had lag with the iPad in the store with just about everything. I found an ipod touch to be more responsive (i know that makes no sense on paper).

Weird. I wonder if it had virus software on it? I used an iPad and it was incredible. I really, really dislike Apple, but from my experience it was an incredible machine.

 

[Holsum]

Agreed 100%. Here's my experience:

* Droid: tiny bit of occasional lag, occasionally needs extra button press

* iPhone/iPodTouch: 99.5% of the time, it's perfect. I can have a list and quickly slide my finger up and down and it's perfect 99.5% of the time.

* iPad: PERFECT. (I really dislike Apple, but DAMN they make a good tablet)

* Palm Pre: Is never perfect, has definite lag and sliding my finger up/down on a list has very noticeable lag and loss of movement.

So obviously, you'd need iPhone/iPad quality, but clearly it can be done. And the amazing thing? The iPhone/Touch I used both had a 600 MHZ processor!!

its amazing how much easier it is to code a OS for 1 phone as compared to many and to make it run flawless. Might be the reason that iphones/itouches/ipads run so smoothly. but you sacrific your mobile freedoms when going with these said platforms. (no customized backgrounds, widgets, tethering, filesystems, etc) its pure classic that Steve mentioned the other day that Adobe isnt "open" when Apple produces some the most monopolizing software/hardware that has ever been released.

AND the major reason why a lot of developers are leaving and going to Android. Just wait Android will catch and far SURPASS iphone/ipad OS in the next year or so.

 

[6tr6tr]

its amazing how much easier it is to code a OS for 1 phone as compared to many and to make it run flawless. Might be the reason that iphones/itouches/ipads run so smoothly. but you sacrific your mobile freedoms when going with these said platforms. (no customized backgrounds, widgets, tethering, filesystems, etc) its pure classic that Steve mentioned the other day that Adobe isnt "open" when Apple produces some the most monopolizing software/hardware that has ever been released.

AND the major reason why a lot of developers are leaving and going to Android. Just wait Android will catch and far SURPASS iphone/ipad OS in the next year or so.

No, that's not it. Palm does it for their hardware only and it's not so smooth. Blackberry same thing (only talking about their touchscreen device). Apple's devices are so good because THEY are so good at quality control, software-hardware interoperation, knowing what's important, etc.