Gaia/Design/ApplicationUXDocumentation: Difference between revisions

Gaia/Design/ApplicationUXDocumentation (view source)

Revision as of 21:21, 19 June 2012

321 bytes removed , 19 June 2012

no edit summary

Joshcarpenter

816

edits

@@ Line 1: / Line 1: @@
-== Overview ==
+* First Run
-UX Documentation
+** Usually presents an Empty State
+** Provides opportunity to prompt user to setup an account, etc.
-* Describes user intent & use (usability, aesthetic design, interface design)
+** Can also be used to educate user via tutorials, tooltips, etc.
-* Describes Stakeholder understanding (vision, product, packaging, marketing)
+* Empty state
-* Assists developers in implementing
+** Occurs when there is no content available.
+** Most commonly seen on app First Run.
-== Application UX Outline ==
+** 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.
-=== Overview ===
+* Error states
-Description of the application
+** Most common will be "no internet connection".
+** As with Empty State, we should avoid user confusion by communicating situation in UI.
-== References ==
+* Input Errors
-External references to other documents which are important to the understanding of this document.
+** What happens when a user's form input fails?
+** Can communicate with:
-=== Team ===
+*** Inline-message (displayed alongside erroneous field)
-* UX
+*** [[Gaia/Design/BuildingBlocks#Dialogue:_Banner|Banner dialogue]]
-* Dev
+*** [[Gaia/Design/BuildingBlocks#Dialogue:_Prompt|Prompt dialogue]
-* Signoff/Stakeholder
+* Date & Time dependencies
+** Is the app effected by user changing global Settings for Date & Time?
-=== Status ===
+*** Time zones
-Stage:
+*** Regions
-Release:
+*** Number formats
+* Dependencies
-=== Use Cases and Stories ===
+** What hardware dependencies exist, and how do we flag them?
-Use cases, stories and scenarios that test the UX and functional requirements of the application against overall goals of application.
+** eg: Music app could be dependent on SD card removable storage, and app could use [[Gaia/Design/BuildingBlocks#Dialogue:_Banner|Banner dialogue]] to communicate.
+* Settings
-=== Functional requirements ===
+** User preferences and settings that effect the operation of the application.
-What are the functional pieces required for the application.
+* Application data states
+** How do apps display states for items?
-=== Wireframes ===
+** eg: Mail message states:
-information and functional architecture of application.
+*** New
+*** Unread
-=== User Flows ===
+*** Read
-Describes how user moves through application and what screens or functions are responsible.
-* Describes logic
-* Describes External dependencies
-* Are user initiated
-=== Events ===
-Describes application generated actions and what functions and screens are altered, changed or updated.
-* How and if requires user action?
-* Describes changes in application state
-=== Dependencies ===
-Hardware:
-Sound, Camera, Haptic, Mic
-API
-rely on other external software or application components
-UI
-interface and design patterns
-=== Settings ===
-User preferences and settings that effect the operation of the application.
-* Required
-Before application is fully functional.
-(ie: email requires accounts to be setup)
-* User Configurable
-** Have defaults
-** Not required for the user to operate application
-(ie: how often email is checked)
-=== Application data states ===
-How applications display states for items.
-eg:
-Mail message states:
-New, Unread, Read
-=== Revisions ===
-Describes revisions of documents.