Embedded Feature

Embedded features invite users to extend the product’s functionality, without detracting from their ability to find and use the existing features. It should look distinct from and secondary to the other content on the page. But it still feels like it’s part of the included product functionality.

Web

When to Use

Embedded features can be used in a variety of places across the product. Use an embedded feature when the new functionality is a robust experience during on-going use. For example, getting paid on a invoice, adding inventory items, etc. are all robust on-going use experiences. Embedded features help the user understand how the new functionality will work in context and provides a sneak peak of how it might work. Because embedded features are specific to individual areas and flows, the designs should be reviewed by the Discovery Governance Team.

Appearance & Behavior

Because they are embedded, they do not have a standard look and feel. However, they do have some common elements.

  • No standard look and feel
  • Blend into the existing structure of the page
  • Have a greyed-out or disabled appearance until enabled

They can drive the user to Learn Pages or directly to turning on new functionality.

Where this pattern is used

  • For example, Fathom demonstrates how new reports will look once Fathom is turned on.
  • For example, turning on the ability to get paid online from an invoice.
Screen Shot 2016-02-10 at 12.55.45 PM
  • Created by and
  • Last modified April 8, 2016 by Kylie
© Intuit 2016 | Terms of use