Last week we hosted our first 3 hour session on Microsoft Windows Mobile development at NITH in Oslo. The session was split into two topics - usability best practises and developing custom GUI controls. Me and Per Ola split the session where i did the first part and he did the custom control development.
Since this is an introductory class to Windows Mobile development we cannot go too deep into the how’s and why’s but rather give a brief overview with pointers to more information for those wanting to learn more.
The UX session started as i always like to do by introducing “Death to the stylus” as i am a firm believer of that it has no future in the world of mobility. It is an obstacle for efficient use of applications. Following this i talked about that it is not a goal for mobile developers to minimize an existing application or process, but to mobilize.
Mobilize, not minimize
As an example i used a freight letter as an illustration on how badly it would look if you just replicated a form onto a small PDA screen. With this in mind we talked about what you should do, how do you go about mobilizing and not minimizing your application flow?
The first thing you need to gain is (if possible) domain knowledge. You need to know something about the users of your application, How do they work? In what order do they do their work? and even maybe in what environment do they do that work? Are they using gloves? Are they working outside in strong sun? All this is domain knowledge and are important questions to get answered because they influence how your final application will look and feel.
Once you have as much domain knowledge you need to get started it is time to think about the flow of your application. Splitting your applications into work flows. This can be done on paper, in powerpoint or any flow chart application.
Application flow
The next step would be to start prototyping your application. This can also be done in several ways. We did not in this class go into use of user stories, it could have been the perfect introduction to that here, but it is outside the scope of this class.
When prototyping applications our UX designers mostly create a mock design using Powerpoint, but your are free to do it however you are most comfortable with, but the aim is to give the general flow, look and feel of the application. When done with that, it is a good time to show your users/client the draft, they will give you valuable input about the direction you are going. We often find workshops with the users/client really useful in this phase.
Application prototype
We talked about UX and desing for about 30 minutes and also mentioning the importance of giving visual feedback to the users after interaction.
After all the talking we did an exercise for about 30 minutes. I presented the students with a web form for a flckr account and the task was to think about how to mobilize this web form. take special care about the flow and what information to place where.
I found this part of the lecture really fun and it looked like the students liked it too. In the world of mobility the importance correct information at the correct time and usability in the application cannot be underestimated.
We then had a short session on some of the standard .netcf GUI controls. In the context of the UX session i explained that the only really useful components in the toolbox is the Form, Button, Label and Texbox. These are the components that can be used without a stylus.
Because of the time and scope of the day we didn’t touch the gesture and physics engine coming with Windows Mobile 6.5, but i will provide the students with links for self study materials. Hopefully we will be able to incorporate this in next year spring class.
This was my first ever lecture on the topic of UX and GUI design, but the words come easy when you talk about something you really care for. Hope to do it again soon.
Trackbacks/Pingbacks
[...] We have already had the first lecture about GUI and usability (Alexander wrote a post about this lecture). [...]