Printing companies, typesetters, and graphic designers have been trying to create beautiful books for readers with the respect for its authors. Unfortunately, years of these people’s efforts have been ignored.

I stopped reading an ebook a couple month ago, because the text size wasn’t consistent between pages. The reading experience wasn’t good. I often see book reviews in ebook sites that say they aren’t happy with the quality of books and talking about reading experiences and not the ebook content itself.

You cannot excuse this. It’s not the same situation as when the Internet has limited type technology.
I hope publishers can fix this problem. And I also think both publishers, readers cannot have all three things: Good, Cheap, Quick.

We only get to choose 2 out of 3.

The Problem With Home

It was very interesting subject that I have been thinking about the back button with Android mobile and Tablet.

I totally agree having 2 levels of home button controls, however, there are apps that don’t define as app-level home screen.

For example, there are 4 main navigation buttons Let’s say A, B, C and D) on top of the screen. When you tap BACK button form this each level is going back to Phone-Level home.
Even you kept tapping them: first A, next C, then B, and then D.
Finally you tap BACK button. That brings to the Phone-level home instead of back to screen B. So in your method, these 4 main screens are all app-level home.

Another app uses the BACK button totally historical data of the application. It works the same as a web browser back button. I think this also totally acceptable as people are familiar and expect how it works.

Now I have to work on Tablet back button…

I agree with the suggestion in the article. The app branding logo takes always user to the App top hierarchy(landing) screen. So we don’t need the indicator arrow on top left with the logo. I thought the arrow will take me to the previous page like we see in computer browsers even the function is doubled up with the physical back button. It is already in the guide lines but I think this indicator arrow is redundant.
The physical back button/on screen back button should work with;
– 1 Go back to previous screen (activity)
– 4 Close on-screen keyboard
– 5 Go to previous page on browser
– 7 Return to previous app when on the last activity and the app was launched through intent from another app

– 2 Dismiss a popup
This should put cancel button on the screen.

– 3 Terminate a long running process
If it’s running in modal, need a cancel button. If user has a choice to do another activity on the same screen (e.g foursquare: while the app is loading the check in list, you can search), back button takes user to the previous page.

– 6 Exit the running app when on the last activity
I agree with Juhani’s thought in the article. The button should be disabled.

These stories are like things we have all experienced, from everyday things with coffee shop loyalty cards (illusion of progress) to why we sometimes regret spending time on Facebook and Youtube. They are all our part of our natural behavior, there is nothing wrong with it. Media has been set up well, to work against our reactions. This is true for internet advertising through to TV commercials.

I have been really enjoying reading these books, hoping that they will help as my design usability decision making references. I say as references, because we can know how we can react in particular situation whatever the test objects are in, but we won’t know these people’s history which may affect the action they take.

I recommend these books to know how our basic behavior in everyday life works. You may find answers for your design project.

Here are a couple of books I have read recently;
100 Things Every Designer Needs to Know About People
by Susan Weinschenk

Brainfluence: 100 Ways to Persuade and Convince Consumers with Neuromarketing

by Roger Dooley

“Scavenger ahoy!” I threw out pieces of bread. They were fighting to get the bread. Others flew in from somewhere. I kept throwing it into them. The birds flew away as soon as the food was gone.

Towards the end, I threw a big pieces of the bread. None of birds came for a while. One came and another came after. This was interesting and it reminded me about Fitts’s law. Why? The bigger buttons are more easily recognized and clicked on a screen.

However, my experience with the birds was if the target was boo big, they were afraid of it. The same thing happens on the screen that if the button or target area is too big to click, the user would miss it was there.

We have to find out appropriate size and position within the vision area on the screen.

Drawing based on a photograph by Kotori Kawashima

I concede that I need more practice.

Television experience has been rapidly changing. We can access better internet environment; speed, bandwidth, and converting to digital broadcasting reinforces the tendency to go back towards television. Audiences have seemed to shift to the Internet once but television’s getting attention as personal entertainment. This is because a home television gets more controllable.

Improving user experience problems on television would be the first step that we can handle and develop. Hardware will absolutely be improved day by day. We will try and want to provide useful functions. Yet some functions are so obscure the user needs to be told about it. These functions would be our challenges to make intuitive for users. On the other hand, we might still have a lot of guesses and expectations about our users. We are hoping that they have a short learning curve for the system to achieve their goals.

We may also encounter many things involved with the presentation of content. We can’t just throw content out to the world without context. We have to present the content in the proper context.

Audiences must not be baffled by television. Television is always in our lives and must not be difficult to use.

Back to basics. Design always has reasons. If your design and layout that come from your feelings, why do you feel so? Are you an artist or a designer?