Difference between revisions of "UX and Onboarding"

Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 86: Line 86:


2. help automated testing test on behalf of the user and the user expectations.
2. help automated testing test on behalf of the user and the user expectations.


Process of actions:
Process of actions:
Line 96: Line 97:


'''Kiwix Android App improvements.'''
'''Kiwix Android App improvements.'''


- Remove the content on the first page of the app. Give the following its own page:
- Remove the content on the first page of the app. Give the following its own page:
1. "what does kiwix do?"  - About us
1. "what does kiwix do?"  - About us
2. "where is the content?"  - FAQ/Help
2. "where is the content?"  - FAQ/Help
3. "how to use the large zim file" - 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)
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
- Renaming device, online and downloading as they aren't intuitive enough for users to understand
Line 109: Line 116:


- Within the 3 dotted menu, link the home button to the apps home content page.
- Within the 3 dotted menu, link the home button to the apps home content page.
=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.

Navigation menu