7
edits
Difference between revisions of "UX and Onboarding"
Jump to navigation
Jump to search
m
no edit summary
Julianharty (talk | contribs) (Raw dump of my text notes. I'll edit these and hope other participants will do likewise.) |
Hybridhayley (talk | contribs) m |
||
| Line 68: | Line 68: | ||
Boris: what about the iOS app? Emmanuel: there’s only 1 developer, he’s not here. Several of the team will meet him in Northern New York right after Wikimania. Chris is a very sensitive developer and much interested in usability feedback. However volumes are not similar so let us stick to Android for the time being. | Boris: what about the iOS app? Emmanuel: there’s only 1 developer, he’s not here. Several of the team will meet him in Northern New York right after Wikimania. Chris is a very sensitive developer and much interested in usability feedback. However volumes are not similar so let us stick to Android for the time being. | ||
=Notes on User Stories= | |||
To improve user flow, it's recommend to start writing user stories to provide us with a sense of direction when using the app. | |||
This will also give us appropriate expectations in terms of functionality and determine any unnecessary actions. | |||
'''Examples for user stories:''' | |||
"As a user I would like to... because..." | |||
Structuring our expectations like this will allow us to: | |||
1. create effective and simple user journeys. | |||
2. help automated testing test on behalf of the user and the user expectations. | |||