Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

> There is a reason Apple does what it does (supposedly to match a real keyboard) but it's not strong and doesn't matter.

Wow. Really? That a silly reason for an otherwise indefensible UI decision. I really wish the iOS keyboard changed case. Ever since iOS 7, I can't tell whether shift is on or off. Maybe I'm just an idiot, but sometimes I fumble with it a half dozen times before getting it right. It's worse than trying to plug in a USB cable.



I see nothing wrong with only showing uppercase letters on the keyboard as they seem easier to read.

The major flailing is the shift key. Right now it's white with a black arrow. That means the sentence started with an initial cap. At any other theme, say mid sentence, it's different again. Mid sentence it's a white arrow on darker gray.

So, in short: about to type cap? Black on White. Mid sentence? white on dark grey. Want to do all caps? Double tap it and get a new version.

I'm not sure how these semantics are different enough from iOS 6 to cause confusion but it does ALL THE TIME.


Good point. I don't remember having this problem with iOS 6. I suppose it's simply a matter of personal preference, but if the keys changed case, I could instantly determine what my keypress would output to the screen. That seems like a UI no-brainer to me.


They're not easier to read

http://en.wikipedia.org/wiki/All_caps


Are you sure that prose and single-character button labels have the same readability characteristics?

The same property that makes "BIG TEXT" more difficult to read than "small text" might make each individual character easier to read. I'm not sure that it does, I just don't think your wikipedia page discusses this at all.


It was fine in iOS 7.0. The problem started in 7.1.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: