- Similar examples from other apps/websites for the same use case have been studied
- Information architecture has been followed. Think: Is the UI design forcing the user through the intended flow?
- Is the user eased-in to the UI or suddenly shown a bunch of confusing options? Is there a proper onboarding? (Reference: Useronboard)
- No dead ends on any page/screen. Always show empty states when needed
- Navigation items have room for growth as new features are added
- Every action that alters the user's data or application's settings can be undone.
- Dropdowns menu’s have been avoided on mobile UI’s
- Empty status must be informative and must prompt the user to take an action
- Fonts and colors must be consistent across all screens
- Brand names must be written consistently (SquareBoat vs Squareboat)
- Sufficient space must be available for user-interface text expansion
- Confirmation/Error message placement
- Validation errors
- Desktop and mobile views
- Loaders when necessary
- Clear call to actions
- Placeholders and tooltips for all necessary fields
- [Web] 404 and 500 page
- No dropdowns for short lists. Large buttons placed as radios
- [Web] Clear Visual Hierarchy and Navigation (Breadcrumbs)
- Multi-step workflows have a clear progress indicator (Step 1 of 4, 30% complete etc.) and a clear sense of where the user currently is.
- Spell check is done
- If UI contains a bulk upload feature, it must have an option to download a sample file.