53
edits
No edit summary |
No edit summary |
||
Line 148: | Line 148: | ||
'''Plans – how we want to solve the problem(s)''' | '''Plans – how we want to solve the problem(s)''' | ||
--> Using the method: other application's test: | |||
First we start to analyse the login process at other applications. | First we start to analyse the login process at other applications. | ||
Line 168: | Line 168: | ||
==First design considerations and ideas== | ==First design considerations and ideas== | ||
We want | After the intervies, the observations while usability tests and the comparision with other apps, we could draw the first design conclusion and ideas: | ||
1. We want the process of creating an account and signing in as inutitve as possible (comparable with WhatsApp and Facebook Messenger) | |||
2. We want the app as safe as possible (safer than WhatsApp and Facebook Messenger) | |||
first changings/development ideas: | |||
* additional button for entering a password (if it isn't saved) | |||
* reduce redundant buttons | |||
* clarify inconclusive and obscure functions/buttons | |||
==Prototypes== | ==Prototypes== | ||
Line 225: | Line 233: | ||
What did work well: | What did work well: | ||
Our teamwork worked all time | Our teamwork worked all time. On the one hand inside the course but especially inside our working group because we regulary organised meetings and were always in contact via messaging about the actual state of affairs. | ||
Furthermore we were well prepared before interviewing so that we could implement that while talking to our target group. | Furthermore we were well prepared before interviewing so that we could implement that while talking to our target group. | ||
Generally we got sufhficient background knowledge for our process of work during the course. So we optained step by step our final design. | Generally we got sufhficient background knowledge for our process of work during the course. So we optained step by step our final design. |
edits