Difference between revisions of "UX and Onboarding"

Jump to navigation Jump to search
no edit summary
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.
Process of actions:
1. User flow diagrams
2. Wireframes
=UX Improvements=
'''Kiwix Android App improvements.'''
- Remove the content on the first page of the app. Give the following its own page:
1. "what does kiwix do?"  - About us
2. "where is the content?"  - FAQ/Help
3. "how to use the large zim file" - FAQ/Help
The Introduction could give clear instructions to navigate the app (see Joe's design)
- Renaming device, online and downloading as they aren't intuitive enough for users to understand
- Merging downloading and online tabs together OR merging downloading and device together
- Within the 3 dotted menu, link the home button to the apps home content page.


=Notes on User Stories=
=Notes on User Stories=

Navigation menu