• 1 year ago - link
    by @ghost

    [bins-3]

    back: bins-0

    Additional possible user interactions.

    Define a large drop area at some standard location on the screen. the user may drop the button into that bin to trigger some special action. Possible use cases:

    • Fullscreen bin menu which presents an even more powerful interface in the form of a n x m grid. The grid is analagous to an iPhone homescreen. When a user drags the action button over an element of the grid, text is displayed prominently that describes what the action would do. bins-4
    • "drop to learn": a target area that provides help information
    • "drop to filter": when triggered, presents a filter list menu item interface that can include such information as: action title, description, icon, info popup trigger, or a link to deeper explanation. Filtering is easy. This list can be comprehensive. It fosters discoverability. It helps users learn about actions related to their current usecase.

    These are all unique potential design patterns enabled by this unconventional binning system. My curiousity gets the better of my rational self when it comes to whether or not one should ever attempt to utilize nonstandard UX design patterns. Theoretically groundbreaking UX tends to make the worst UX.

    I will implement prototypes and refine as I progress.

    With binning, bin menus, filter menus, a chatbot, and tutorials and documentation referenced by the same, one could achieve a very powerful, low ScReF, low burden, unobtrusive, contextual, on demand help UX.

    back: bins-0

[bins-3]

back: bins-0

Additional possible user interactions.

Define a large drop area at some standard location on the screen. the user may drop the button into that bin to trigger some special action. Possible use cases:

  • Fullscreen bin menu which presents an even more powerful interface in the form of a n x m grid. The grid is analagous to an iPhone homescreen. When a user drags the action button over an element of the grid, text is displayed prominently that describes what the action would do. bins-4
  • "drop to learn": a target area that provides help information
  • "drop to filter": when triggered, presents a filter list menu item interface that can include such information as: action title, description, icon, info popup trigger, or a link to deeper explanation. Filtering is easy. This list can be comprehensive. It fosters discoverability. It helps users learn about actions related to their current usecase.

These are all unique potential design patterns enabled by this unconventional binning system. My curiousity gets the better of my rational self when it comes to whether or not one should ever attempt to utilize nonstandard UX design patterns. Theoretically groundbreaking UX tends to make the worst UX.

I will implement prototypes and refine as I progress.

With binning, bin menus, filter menus, a chatbot, and tutorials and documentation referenced by the same, one could achieve a very powerful, low ScReF, low burden, unobtrusive, contextual, on demand help UX.

back: bins-0