Essential Mobile Interaction Design

mobile interaction

 

The book is composed by eleven chapters and three appendixes. It is well structured, starting with the basics of the mobile up to advanced concept regarding interaction design.

The first chapter deals with the basics of mobile starting from its natural definition and the minimal definition of “app”. Also the various type of device are described, smartphone and tablet, and the principal giant: Apple and Google.

The second chapter defines the approach by a human for a human, key to understand how to design an ideal and intuitive user interface.

The third chapter defines the various types of interactions that are possible to do with several devices. Click, tap and point are the basis of the classic interaction. The chapter underlines the importance of a common appeal among the different formats of the devices.

Concentrating on a specific platform could simply, in some ways, the work. The way to define an application might not be the same among the various platforms. The fourth chapter defines how to define a workflow for a specific platform, using several tools such as Photoshop or Balsamiq.

The fifth chapter is very interesting, it defines the most classic difference regarding mobile development: native app, web app and hybrid app. Also it defines the various types of principal navigation: single view, tab view, gesture-based, etc.

For an application is important to maintain a certain visual uniformity in order to ensure visual consistency of the application itself. The sixth chapter talks about those concepts, starting from the definition of an icon up to define an unique look for the application itself. To underline, at the end of the chapter the phrase: “so attractive icons help grap attention”.

The seventh chapter introduces the developers. People deal with developers have to have a clear communication for a productive collaboration. Also, the chapter introduces the basic tools for the versioning of code, like Git and various tools for the process of the issue. Maybe the part regarding Git could be avoided. Usually the UX Designer doesn’t use the version of control.

The eighth chapter defines the concept of audience, how to know the destination target and how to define a possible expansion in the market. To underline, the 80/20 rule: about 80 percent of users will use 20 percent of the feature. The final part of the chapter talks about defining a design for users with disabilities, intoducing tools like XScope.

Simplicity is everything for an application. Clarity is a fondamental concept for an intuitive interaction.The nineth chapter defines all the aspects of simplicity ending with the testing of a possible simply design.

The tenth chapter is based on the feedback, an important element to verify the success of an application. To determine the right strategy for the beta test is the right way to give a first verification of the application. Analizing the possible datas from the single module of the application, we could examine where the users focus on and what they use frequently. The resolution of all troubles that occured from beta testing permits the application to be published.

Once this happens you can be dedicated to the future, design in primis. The eleventh chapter talks about the future.

The final three appendixes complete the basic portfolio for an UX Designer.

The whole book is great, not for developers but absolutely for designers. Ideally I don’t know how much UX Designer has to keep up with tools for the version control, process issue, etc, even if to ensure the right management of the processes these tools could be a practical and simple solution.

No Comments

Post a Comment