The following is a list of common UX considerations to take into account when building out Gaia apps.
- Usually presents an Empty State
- Provides opportunity to prompt user to setup an account, etc.
- Can also be used to educate user via tutorials, tooltips, etc.
- Occurs when there is no content available.
- Most commonly seen on app First Run.
- Also seen when user clears all content.
- To avoid user confusion ("Nothing is showing up. Is the app broken?") we can display a status and/or explanation. For example, a "No messages" string where a list might usually be.
- Most common will be "no internet connection".
- As with Empty State, we should avoid user confusion by communicating situation in UI.
- Note where gestures are available to the user, and what they do.
- What happens when a user's form input fails?
- Can communicate with:
Date & Time dependencies
- Is the app effected by user changing global Settings for Date & Time?
- Time zones
- Number formats
- What hardware dependencies exist, and how do we flag them?
- eg: Music app could be dependent on SD card removable storage, and app could use Banner dialogue to communicate.
- User preferences and settings that effect the operation of the application.
- First determination: does the app _need_ dedicated specs?
- Second determination: what settings are needed? Larissa's Settings Design Patterns are a handy reference when laying out.
Application data states
- How do apps display states for items?
- eg: Mail message states:
- Does the app support landscape orientation?
- Does the app receive or send activities? eg: Share, Select, etc.
- Does the app issue Notifications? When, and what?
- Action (eg: open App, open SMS thread, open keyboard)