Skip to content

Instantly share code, notes, and snippets.

@craigbeck

craigbeck/design-elements.md

Created March 11, 2016 22:56
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save craigbeck/4a946ba99936b22cb878 to your computer and use it in GitHub Desktop.
Save craigbeck/4a946ba99936b22cb878 to your computer and use it in GitHub Desktop.
Download ZIP
Design pointers and considerations for web apps
Raw
design-elements.md

Frequently missing components

  • empty view; what about when there is no data?
  • tansitions; animations?
  • busy indicators; spinners, interstitial views
  • error views
    • view?
    • alert?
  • global alerting
    • "new version available"
    • "that last op failed"
    • "there was an update"
    • "that last thing succeeded"
  • paging
    • what about a lot of data?
  • component library; many things dont need "design" as have given
    • generally dont need form design as long as we know what forms look like; fields define form
    • design matters when there's complexity; general pattern for form may not scale to complex form; so single form or wizard?

Pitfalls

  • tables for non-tabluar data
    • if its not comparable, its not a table
    • you don't have quantitative data
    • example: multiline-admin table showing invites and assigned lines
  • tabs
    • should it be routable? don't use tabs
    • is it secondary data? maybe
    • is it primary data? don't use tabs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment