Thursday, 2 May 2013

Smart Phone Concept for Five Years Time

The aim of this project was to design a concept smart phone for use in five years time (2018), taking into account the relevant development of technology and how it could be applied in the form of functions.

I first began by researching common problems that users currently experience in order to understand what aspects of smart phones could be improved or changed, in favour of better usability and functionality. This storyboard highlights the problems I discovered.

  1. The annoyance of having to pick up and unlock a phone in order to see a notification such as a text message or email. As this usually happens frequently, this repetitive task can become annoying, leading to the user not bothering to check the notifications until later on.

  1. The difficulty of inputting form data due to the text boxes being too small, for example when purchasing items on the internet. Instead, users will often just wait until they get home to use a PC with a larger screen. It is also difficult to read and input card details when on the move or on public transport. This problem means that many people are put off online shopping whilst away from home.


  1. Other people can unlock a user’s phone if it is left somewhere and so access personal content without permission. Password protection of course prevents this, but the act of having to type a password or swipe a pattern can be annoying to a user.

  1. The majority of smart phones today are not water proof and so if a user goes swimming, they will have to leave it elsewhere. Not only does this mean they can’t access their phone if they want/need to, but the fact it is not with them increases the chance of it getting stolen.

  1. Often when users are away from home, they will realize that they need to turn on a home appliance such as the cooker or the heating at a certain time in order to be ready for when they come home. Unless they can contact someone else who is at home then there is nothing they can do about it.

No comments:

Post a Comment