Browser extension connected to a product workflow
← Build

YAS / IMPLEMENTATION CAPABILITY / Apps and extensions

Choose the surface that removes a specific context switch.

An extension or native app is useful when a repeated action happens inside another platform or needs device, offline, camera, notification, or local-context capability.

When this capability is useful

  • The repeated action happens inside a third-party browser interface.
  • The workflow needs camera, notifications, offline, or device integration.
  • A platform extension can remove a costly context switch.

What must be designed

  • Surface decision: browser, web, mobile, desktop, or platform extension.
  • Minimum permission and data-boundary map.
  • Distribution and release-channel plan.

Decision artifacts

Choose the surface after the operating model.

  1. 01Surface decision matrix.
  2. 02Permission map.
  3. 03Release-channel plan.

When not to use it

  • Do not use platform logos as a substitute for a use case.
  • Do not ask for broad permissions ‘for later’.
  • Do not promise store approval.

Related decision path

Customer and product systems

Open related path →