Ouch!

Yeah well Pensacola is like another state. Not even the same time zone...

Sent from my HTC One X using Tapatalk 2
 
I'm pretty sure one of the hacking sites checked, and there is. (I believe they ran a touch app, and it registered a touch when the logo was tapped.)

Sent from my HTC6435LVW using Tapatalk 2
I believe I heard it on an episode of the AC podcast that there wasn't anything back there. I'd be psyched if there was.
 
The way I look at it, if you see a black menu bar in an app, the app isn't worth using. If you stick to well written apps built by developers who know what they're doing, not only will there be no black menu bar, but you'll probably have a more enjoyable experience all around. The only app on my phone with legacy menu button support is the Bank of America app.

This. I actually went back to the drawing board on the app I'm writing to make sure it's Holo compliant and has the menu bar where it should be.
 
My first clue that this was not going to be a serious piece was with the misspelling of "Hideous".
 
My first clue that this was not going to be a serious piece was with the misspelling of "Hideous".

I think it was rubbish, but not because of the spelling. Plenty of smart people are poor spellers.

Sent from my SPH-D710 using Tapatalk 2
 
The way I look at it, if you see a black menu bar in an app, the app isn't worth using. If you stick to well written apps built by developers who know what they're doing, not only will there be no black menu bar, but you'll probably have a more enjoyable experience all around. The only app on my phone with legacy menu button support is the Bank of America app..

You're entitled to look at it your way, of course, but I have quite a few apps that provide strong value to me that haven't been updated, and may never be updated. These are apps that have been around since well before JB, and were provided free of charge. I suspect the original authors have little incentive to go back and rework them. That doesn't change there value to me, and I have better things to do with my time than scour the Play store looking for apps that provide the same function with a different interface. IMHO, HTC should either go whole hog and adopt the standard JB interface, or keep the menu button. It looks to me like the only benefit of HTC's approach is that they got to stick a big HTC logo where the home key should be.

As for the review, it's one man's opinion. He's entitled to it, as everyone else is to their's.
 
I'm pretty sure one of the hacking sites checked, and there is. (I believe they ran a touch app, and it registered a touch when the logo was tapped.)

Sent from my HTC6435LVW using Tapatalk 2

Best way to test it, even on an old phone..
Go to your home screen and start scrolling to the left and as you are scrolling slide down to where the buttons on the screen are. If you slide your fingers on the buttons and the home screen still moves then the whole area is touch sensitive. I would suggest some One owners to try this if they were to slide around on the HTC logo and the screen responded by moving then it could be programed
 
I don't think "reviewers" missed the black bar thing. I just think most of us are smart enough to have known (for how long now?) that that's a side effect of non-compliant applications. If that keeps you from buying the phone? So be it.

If it keeps someone from doing crap "reviews" like that in the future, even better. :-/

Like tapatalk *coughcough*

Sent from my HTCONE using Tapatalk 2
 
Keep the menu button? Why go backwards?

Sigh. For the reason already discussed in this thread: Because there are a treat many apps, probably 10s of thousands, that haven't adopted the current interface guidelines and simply work a lot better with a menu button. But I did say OR. HTC's approach is neither here nor there. Not very compatible with many existing apps, and not compatible with Android standards. There are already two serviceable approaches. Why they created yet another non-standard approach is beyond my ken.
 
Sigh. For the reason already discussed in this thread: Because there are a treat many apps, probably 10s of thousands, that haven't adopted the current interface guidelines and simply work a lot better with a menu button. But I did say OR. HTC's approach is neither here nor there. Not very compatible with many existing apps, and not compatible with Android standards. There are already two serviceable approaches. Why they created yet another non-standard approach is beyond my ken.

It is not htcs problem if developers do not update their apps to be compliant with android standards. Htcs implementation is technically compatible with them but through double use of a key. A phone with a menu button will never be compatible with them.

Sent from my HTC6435LVW using Tapatalk 2
 
I get that, but going backwards is never the right answer.

That is a bit of hyperbole.

I think in some instances backward may be better than sideways, and could be better than forward.

I really don't think it will bother me in either case, and I think too much is made of the dreaded black bar, but blanket statements like "never" are seldom correct. I can see the point of meyerweb.
 
It is not htcs problem if developers do not update their apps to be compliant with android standards. Htcs implementation is technically compatible with them but through double use of a key. A phone with a menu button will never be compatible with them.

Sent from my HTC6435LVW using Tapatalk 2

Who's problem is it then?
It is HTC's problem if it costs them sales. They are in dire need of increasing sales.