From MozillaWiki
Jump to: navigation, search


The goal of our project is to come up with concept for mobile for the future which will improve user experience

Team Members

  • Steven Odarteifio[1]
  • Abdourahmane Toure[2]
  • Ivan Tetteh Digber[3]
  • Derrick Crentsil[4]

Background Research

In the light of technological prowess, mobile manufacturers and mobile application developers have come up with great ideas that have tremendously enhanced user experience. In addition, the future mobile phones should interact with the users in a different way-PET which will bring persuasion, emotion and trust. In order to come up with PET ideas based on mobile for the future we decided to interact with users so as to find their likes and dislikes and most importantly their requirements.

Problem Identified During The Research

* Inadequate spacing between buttons on the keypad making typing difficult.
* Poor battery life.
* Difficulty with phone differentiating similar numbers on different mobile phone networks.
* Issues with deleting a single message out of a conversation of text messages.
* Inadequate memory space for storing numbers and other items.

Fortunately and unfortunately, most of these problems have been solved one way or the other on the different mobile handset companies. As a result, we sought to find out from users what features they would like to have on their phones. The interesting suggestion that came from one user was for the phone to have the ability to detect the mood of the user and respond accordingly. This concept was considered and developed because of a concern raised by one of our interviewees. This user felt there was a need for phones to be personalized according to users; phones should be able to respond to the moods/emotions of users. We found this idea very intriguing and decided to develop the idea. The essence of this project is to enrich the user experience of mobile phones. Having a phone which can react to your mood provides a different dimension to the user experience of mobile phones.

The design problem

To design an innovative application for mobile phone for use in the future.

Understanding needs and establishing requirements

In our data gathering exercise, we interacted with real users to find out likes and dislikes they had concerning mobile phones. This was done through a one-to-one interview. We asked them the following questions:

  1. Activities of phone?
  2. Difficulty using phone?
  3. Where to get help?
  4. Daily Routine?
  5. What you use your phone for?
  6. What would you wish your phone could do?
  7. What you don't like?
  8. What you like about your phone?
  9. What you find easy to do with your phone?

Personas and Scenarios

The personas below were created from the information we gathered during the interaction we had with the users of each brand.


Sheila.jpgSheila Sheila is a 22 year old university student who has a very tight schedule. She has never bought a phone herself; her parents usually give her a phone they may not be using. Sometimes she gets relatively new phones and other times she gets old phones. She sometimes has to compete with her siblings for a phone being given out by her parents. She prefers to have an advanced phone than what she currently has. This gives her more bragging rights over her siblings because of the added functionality of the new phone and she likes to show off. Sheila always finds herself between assignments, field work and extra-curricular activities. She always needs to have access to a laptop to do her work. She is a hard working student who maintains at high sense of time. She uses her alarm to keep track of time if she needs to do anything. She also uses the calendar on her phone to remind her of events and anniversaries. She also synchronizes the events on her phone with that on her computer to ensure she has the same schedule on her computer and phone. It has been a part of her upbringing to be punctual to school and to other functions. This is a skill she learnt from her parents who always ensured she got to her destination early. She also needs to check her mail because information about activities and courses are sent through the mail. Sheila once in while listens to music on her phone. She sometimes listens to music when she is bathing in the mornings, most preferably gospel music. She listens to gospel music because of her strong belief and faith in her religion. It also serves as a source of motivation in everything she does. She pays particular attention to the words of the song. Sheila always wants to feel motivated about everything to do. She also has a strong bond with her parents and siblings. This trait was cultivated when she was growing up. Her parents taught her to put family first in all her activities because her family will be the first point of call if she needed anything. Sheila has lived away from home during senior high school and college. In the absence of her parents, she has had to rely on friends who would sometimes disappoint her. Other times too she had the right kind around her. Sheila has come to an obvious truth that her family will not always be with her and she may also not have the right kind of people around her. Having a phone with which she can interact with all the time she thinks will not be a bad idea.

                            SCENARIO 1

Sheila has a very busy schedule in school. She has four classes in one day and the day gets very hectic. Sheila is able to download a file a file from the internet which she will need for class. She heads to class but no one has the file. She wants to be able to Bluetooth the file to multiple friends via any device which has a network connection. Unfortunately she has to either do it one by one or send it through the emails of her friends. Sometimes Sheila gets home stressed out and she needs to be encouraged or motivated. Since she carries her phone everywhere she goes, she wants her phone to be able to detect her mood and talk to her or play some music. She needs to stay motivated because of the various pressures that exist.


Jon.jpg John is a 25 year old security officer who works with a private security firm. Most of the time he guards the gates and property where he has been assigned. John in new to his job and has been working for about a month. His highest level of education is the senior high school certificate. He did not get very good grades and he comes from a poor family. He has to make ends meet to feed himself and provide for his family. John has been working other jobs but this one seems to be his highest paying job so far. He would take the opportunity to jump at another job if he would get a pay rise. John has one phone with internet connection. This phone is a low end phone. Most of the time, he plays games with his phone. Some of the games he plays include Rapid Roll and Towers of Hanoi. All the games he plays came with the phone. He has not tried downloading any games to add to his current collection. He fears that his phone credit will run if he tries downloading any games. He also checks his mails and contacts friends with his phone once in a while. John spends about 2Ghc a week on call credit. John has a post where he sits. John usually works from 5:45am – 5:45pm. John’s phone has a short battery life. He has power supply to his post therefore he is able to charge it almost all the time. John does not plan on buying a new phone or battery. He hopes to manage with the phone he currently uses. He would prefer to get an original battery which is quite expensive as compared to the fake battery. John has three SIM cards. Then include and MTN, Vodafone and Airtel SIM cards. John usually has a schedule for patrolling and as a result, he tries hard to finish what he is doing before he goes round to patrol. If he is unable to finish what he is doing prior to the patrolling time, he puts his activities on hold, finishes his patrol and continues his activity. After working for a couple of months, John has been thinking of a way to monitor activities going on within the place where he guards. This will afford him some time to play more games on his phone.

                              SCENARIO 1

John has to report for duty very early in the morning. His job begins at 5:45am which means he has to wake up early in the morning. John spends a majority of his time guarding the gates and property where he’s posted. He has to always patrol the premises where he guards. There are existing CCTV cameras in the building where he John wants to be able to connect to the existing CCTV cameras where he guards. This will give him access to activities happening in different places where he guards. John also has a lot of free time and would like to play games or engage in other activities.

                             == Concept ==

Moody is the name we choose. basically when you are using moody for the first time it should take you to the settings before it works.There is sensor in the form of a bracelet that senses the pulse rate. The camera on phone should also detect the mood by taking pictures of the user's face and analyzing it. When we are angry are pulse rate is high, or we frown our face.There are various options that the user has, music,color,pictures,theme and call.We all have favorite songs that make us happy, some colors tend to relax the viewer so does the theme, we all want to talk to someone whenever we are sad for example. Therefore using psychology and technology we can breakthrough to create emotional interaction between the phone and the user.


Prototype 1

Openning Application

Group5 mockup.png


First screen, uses opens the application. the second screen, the application asks user whether it should select a pattern whenever user is navigating the phone. A pattern using the phone could that a user calls she/her mom all the time, the application may select that pattern and add it to the settings. So whenever the user is sad the app will suggest the user to call mom for comfort.

Prototype 2

Configuration Screen

Group5 mockup2.png


The first screen shows the configuration of music for example. the user select her/his favorite songs. The second screen shows the songs selected. The third screen shows how to coordinated the application's response to your mood.

Prototype 3

Mood detection

Group5 mockup3.png


Screen shows the detection of the users' mood. the user is sad, so application alters the user that she/he is sad.The selection gives the user more control on how the application respond. Depending on the time the user might not want to play music so the user just select call person.

First and Second Iteration

After testing the first prototype this is what we got from the participants: Summary of Tests

Lady-Asaph (3rd year University Student, Ashesi University):

Initially when the wrist sensor was shown to Lady, she thought that when she pressed the button on the wrist sensor, it would tell her how she felt. She also did not like the name of the application and would prefer that it be changed. She did not like the pop-ups that come up when the application was running. For example, when a mood is detected, it asked whether she was sad and what did she want the application to do? She would prefer that the application just reacts once a mood has been detected. She also complained about the number of steps she had to go through when configuring the application. It was lengthy and she was willing to go through it. On the wrist sensor, she wanted to have two buttons. One to stop the application from running and another to make the application run one a mood has been detected. She found the application to be interesting but did not find herself using such an application. Changes proposed which will be implemented: - Reduce amount text in some of configuration stages. - Make wrist sensor with one button to control the application easily. - Make the application automatically react after sometime when a mood has been picked up.

Jacqueline (3rd year University Student, Ashesi University): When the application was explained to Jacqueline, she understood it and thought it would be interesting. We went through the process of configuring the application and there were no issues. However she raised some concerns with how the application would differentiate between the different moods the application would identify. She also raised concerns about how the application could be tricked when select the option of the application getting to know you. If you prefer to play a lot of hip hop music all the time and application picks up one of them as you favourite music. Therefore in a case where Moody wants to cheer you up, it would play the hip hop track when maybe you would prefer to listen to some gospel music. She also wanted the sensor to vibrate anytime a mood is detected. Also on the wrist sensor, she wanted a button that would automatically get Moody working without having to pick out her phone to activate the application. Unfortunately, she did not find herself using such an application but recommended such an application for children.

Changes proposed which will be implemented: - Make wrist sensor with one button to control the application easily. - Cause the wrist sensor to vibrate once a mood has been detected. Some of the participants of the testing process did not give us any constructive feedback so we scrapped their comments. After testing was carried out on Lady-Asaph and Jacqueline, we iterated the design of the prototype and factored in the proposed changes which will be implemented.

Augustus (3rd year University Student, Ashesi University) When the application was explained to Augustus, he understood it with ease and found it to be interesting also. He went through the process of configuring the application with ease. When shown the wrist sensor, he suggested that it be built into a watch or any item he wore on his wrist. Augustus suggested that if the phone could use the tone of your voice to try and determine your mood. He liked the application and thought it would be interesting if the group could pull off the application. Samuel (3rd year University Student, Ashesi University) Samuel was able to understand how the application would work when it was explained to him. He had very little concerns and went through the configuration process of the application. Changes proposed which will be implemented: - Inculcate microphone to pick up tone of voice in determining the mood of a user.

Iteration 1 & 2




7.jpg Fingerprint authentication Newa.jpg

Feedback and Impact

Feedback provided by Thomas Arend PhD, Lead Product Manager, Mozilla Mobile:

Hello, Steven, Abdourahmane , Ivan, and Derrick - thank you very much for sharing insights from your project. I really liked it, especially the visual parts. Allow me to share a few more comments here:

  • SAID
    I really like your mission, to develop a "...concept for mobile for the future which will improve user experience". I suggest to be even more concrete about the term "mobile" - are you taling about mobile devices, mobile services, mobile interaction, mobile web, or a different kind of mobility (cars? jet packs?)
  • Background Research
    PET - persuasion, emotion and trust - sounds like a great concept. It would be great to explain this some more. What exactly do you mean? Can you give some examples for P, E, and T and how they come together in an innovative product?
  • Problem Identified During The Research
    Those results are good and very insightful. But I am missing background information about your research setup. Did you interview people? Which people? Where? How exactly did you get to those insights? How representative was your group? What was the goal of your research? That would help put your results in context. I really like the unusual and very creative premise of your project: to include the mood of a user into the user interaction. Very innovative! What is your hypothesis around using knowledge about the users mood for improving mobile interaction? Some examples would help. Also: how do you define "mood". Could it be simply "behavior pattern" - if I interact with my phone very quickly, drag, drop, tap in rapid succession, one could infer I am (a) in a happy mood, (b) totally stressed out, (c) pressed for time, (d) just quick? And how would the system learn from user behavior over time, etc.
  • The design problem
    This goal is too generic to disagree. I would rather see this as your overall framework. But what exactly is your goal? Can you narrow it down? Maybe revolutionize user interaction with mobile devices? And what do you mean by "the future" - are we talking about fall 2011? Or 2015? Or the year 2200? Is this specific to a device? If so, what happens when mobile devices just disappear (e.g. in favor of embedded systems, e.g. every surface can give you access to the web)? What I really like though is that you describe your overall design problem in one short sentence as your mission or "core".
  • Understanding needs and establishing requirements
    This information is great. I would love to know more. Where did you talk to them? How many users? Demography? Which experience level with mobile phones / smart phones / internet? How diverse was your group? etc. In a real study, it is even better to add some stats about these and other details of the configuration of the setup (age distribution, experience level, stats about happiness/ frustration with mobile tasks, etc.).
  • Personas and Scenarios
    This part is awesome! Your Personas and Scenarios are great, I love the visual with the photos a lot! I would suggest to keep the persona description much shorter and to not mix them with the scenario part. Also: there may be multiple scenarios per user type that you want to highlight. In addition, it sometimes help to give your personas nicknames: e.g. Sheila - the busy student, or John - the early bird security guard. It is nice to see how your personas come to life with your background info and scenarios. Maybe you need more than two (up to five) personas to represent more user types, age groups, expertise level, and different classes of scenarios.
  • Prototypes
    I *love* your prototypes. They are very nicely done, not too much, great visual, just enough to show the concept, and not too much to not contain too many concrete design details. Great job! Two things that could help embed them in context even more: For each prototype, explain which scenario the are for: so, instead of "opening screen" and "configuration screen" rather start with an overall flow diagram to show the user interaction - either in one big diagram or in parts that explain different aspects (e.g. "configuration" or "application start and welcome"). A concrete example would help. Also: how do those prototypes map to the scenarios and personas you described above. In other words, how do these address concrete user requirements or unmet needs? It would be great if you could also visualize other important components of your concept: the wrist sensor, and your other ideas to capture a users mood. It sometimes make sense to separate user interaction (the flow chart) from visual design (your screens), especially if you want the actual application design to be a separate process in order not to limit creativity.
  • First and Second Iteration
    Would love to know how you tested those prototypes? Paper? Click-through?
    Iterations 1 & 2 look promising, but need some context to explain what exactly you are showing and why you suggest those changes. It is unclear if all those prototypes belong to one user process or whether they are different steps. Remember to re-use the user flow graph (see above) to describe which screens you are talking about. That serves as an easy "floor plan" for your research and documentation. Looks very promising. When can I find this prototype on an actual phone? ;o)

Great Job!! Feel free to contact me anytime at if you have any questions or additional comments. Thanks!