Confirmed users
25
edits
Englehardt (talk | contribs) (Refactoring site-specific containers + moving it to end or wiki) |
Englehardt (talk | contribs) (Refactor of Behaviors, Discovering the Feature, and Making Containers look different. Removing outdated or incorrect information from these sections.) |
||
Line 43: | Line 43: | ||
==Purpose-specific Containers== | ==Purpose-specific Containers== | ||
We propose a model where users are given a set of contexts that user research suggests are common or useful user contexts, and also provide the ability for a user to define their own contexts. | |||
[[File:Containers-start-page.png|900px|frameless]] | [[File:Containers-start-page.png|900px|frameless]] | ||
The set of included containers is: | |||
* Personal (to use at home) | |||
* Work (to use at the office) | |||
* Banking (for accessing sites with financial or sensitive informations) | |||
* Shopping (for accessing ecommerce sites) | |||
* Custom (for future versions) | |||
Through naming and onboarding, we gently encourage users to use different containers for different purposes, as the separation is necessary to gain the benefits above. A purpose-specific container can have many sites in it: | |||
* The Personal container can be signed into Outlook, Facebook and Twitter. Work can have Outlook, Facebook and Twitter, too. | |||
* The Banking container can be signed into your bank, insurance, accounting and investing websites | |||
* The Shopping container can be a place for Amazon, Alibaba, and other stores | |||
===Behaviors=== | ===Behaviors=== | ||
By creating containers, we also create a notion of sites that exists ''outside'' of a container. This necessitates a few behaviors when you navigate from inside a container: | By creating containers, we also create a notion of sites that exists ''outside'' of a container. By default, all of a user's browsing prior to enabling the feature is considered to be in the ''default'' container. Additionally, any browsing that occurs after the feature has been turned on, but not in a named container is considered to be in the default. | ||
Our goal is to match the navigation experience that users currently expect during a session without containers. This necessitates a few behaviors when you navigate from inside a container: | |||
Manually-invoked navigation: | Manually-invoked navigation: | ||
Line 80: | Line 84: | ||
Each container could have a different: | Each container could have a different: | ||
* Name: | * Name: On the File Menu and location bar | ||
* Icon: | * Icon: On the File Menu and location bar | ||
* Color: | * Color: On the tab and location bar | ||
==Discovering the feature== | ==Discovering the feature== | ||
Line 88: | Line 92: | ||
[[File:Containers-file-menu.PNG|668px|frameless]] | [[File:Containers-file-menu.PNG|668px|frameless]] | ||
For | For the initial version, this feature is discoverable via the File menu and is limited to a few purpose-specific containers. However, on Windows, the File menu is hidden until the user hits the Alt key. In future versions, the Containers menu should be added as an item under the ‘Hamburger’ menu on the right side of the toolbar. | ||
Containers are discoverable for those who want to use them, and have no impact on the browsing experience of those who don't. Through user research, we’ve found that most people have only one account per website, and that they don’t currently separate their online selves into work/home/banking/etc. | |||
However, we can hook into several user actions and present onboarding messages to encourage container use. We can detect users logging in and out of a service like Twitter that doesn't have support for multiple logins, and offer the feature to them. We can also offer the feature to users when they first try to access their online banking after the feature has been enabled. | |||
==Alternative Features== | ==Alternative Features== |