Skip to main content

More Android Usability Issues

Second post in a series of problems and solutions for Android usability. I'm writing these because I love Android, and if these usability issues are fixed, it'll be even mo betta'. =)

1) No notification on receipt of SMS that needs to be downloaded.

WTF? I had a nice argument with the Android team when I was still at Google about something likely related to this. If you receive an MMS that your Android phone can't display, then there's no notification. None. You only notice the new message if you explicitly go into Messages to look for it (or more likely, receive a totally unrelated SMS that alerts you to check Messages). I was told by the Android team that no notification is better than a notification when you can't see a preview of the message. I got far too frustrated arguing with someone who actually believed this to be self-evident, and just gave up (one of many super detailed Android bug reports that never made it past the Android usability gatekeepers).

Analogy - you won the lottery, but they didn't alert you, since they couldn't send an envelope with the amount of the check visible through the envelope window. You only know that you won if you call up the lottery to ask.

Clearly the notification delivers useful information, and should be delivered regardless of whether the message can be previewed. If nothing can be previewed, at least the sender can be shown, which is very useful in and of itself.

Obvious fix here is to have a notification on receipt of any SMS/MMS, even if no preview can be shown.

2) Multitouch is ... suboptimal.

Multitouch works way better on iOS than Android, at least my Nexus One. I'm told it's because multitouch is "simulated" on Android but is "real" on iOS. One of the way this manifests for me at least is that when using the phone with one hand, if I'm holding the phone too tightly, then some skin touches the outer edge of the screen, disabling all other touch actions on the screen. Seems pretty easy to detect with software....

3) Phone numbers aren't localized.

In Korea and Japan, a mobile number looks like 333-4444-4444. That is, a group of three numbers, followed by two groups of four numbers each. In America, numbers look like 333-333-4444, or three, three, four. On the stock Android OS, Korean and Japanese numbers show up as 333-333-55555. Many locals think something's wrong with my phone if they see it.

Fix: Localize phone numbers.

That's it for today! Looking forward to Android continuing to get better in upcoming iterations. Go Android!

Comments

Popular posts from this blog

English Lesson: "한국에 오신지 얼마나 됐어요?"라고 영어로?

I've lost count of how many times Koreans have asked me the question, "How long do you stay in Korea?" in those words or something very similar. Clearly this question is taught in every English class in Korea, because I hear it over and over again, so I just wanted to be very clear about something here:

DO NOT USE THIS EXPRESSION. IT IS INCORRECT.

This phrase is incorrect for a few reasons, but primarily because it sounds ambiguous to native English speakers. Specifically, there are probably two different questions that you really want to ask:

1) How long have you been in Korea? (한국에 오신지 얼마나 됐어요?)
2) How long will you stay in Korea? (한국에 얼마나 있을 거예요?/한국에 얼마동안 있을 계획이에요?)

Nearly always the intended question is number 1, "How long have you been in Korea?", followed afterwards by number 2, "How long will you stay in Korea?". But the incorrectly stated question ambiguously sounds somewhere in between number 1 and number 2. So, don't ever use it again. T…

Stuttering in Korea

I had given up on English. It's my native language, but I figured after 30 some-odd years of disfluent speech, it was time to try something else. So I signed up for language classes in Korean, rationalizing that if I was going to try to teach myself how to speak, I might as well learn a new language along the way.

This might seem completely insane, but when the prevailing theme of your conscious thoughts for multiple decades is some variant of "Why can't I say what I want to say?", you come up with lots of crazy ideas.

For background, I've been a person who stutters for my entire life. I wrote about it on this blog a few years ago, so I think it's time for a followup. I've learned a lot since then, about myself and about stuttering, but in this post I simply want to give some insight into what it's actually like to stutter, and how my speech has changed over time.

After the last stuttering post, the predominant reaction I got from friends was either &…

Why Korean Is Hard For Native English Speakers

A couple of days ago, as an experiment, I wrote my first blog post ever in a non-English language. It was an attempt to explain some of the reasons that Korean is hard to learn for native English speakers, so I figured I might as well try to write it in Korean. Those of you who actually read Korean can see how awkward the attempt was =).

In any case, the post came from an email conversation I had with The Korean from Ask a Korean, a fantastically well-written blog about all things Korea from the perspective of a Korean who moved to the United States during high school. Since I tend to geek out on language things, I figured I might as well post part of that conversation. An edited version follows.

---------

Out of the languages that I've attempted to learn so far, Korean has been the hardest. I've done a lot of meta thinking about learning Korean, and I think there are a number of reasons it's difficult for non-Koreans (and especially Westerners) to learn:

1) Obviously, the…