[submission] Switch When Available

[bumbleblue]

The Design Problem

Discovery is often the biggest hurdle for decentralized protocols. We cannot expect users to continuously hear and learn about new and relevant technologies. Even when new apps and protocols exist, users may not know where to find them and how to use them.

The Design Solution

When a (new) decentralized technology is implemented, advertise the availability on an existing app or platform. Use a switch or a redirect to let users try out the new behavior. This applies both to entirely new apps or technologies, as well as individual new features.

Examples

::: examples

• Beaker Browser uses "p2p version available" when it finds a website that an existing peer is hosting, prompting a switch from https to beaker.

:::

Why Choose ... ?

Switch When Available meets people where they are. Instead on installing and revamping exisitng systems and technologies to accommodate for new app or protocols, a feature like Switch When Available makes it easier to switch on an individual basis.

Best Practice: How to Implement ...

• Switch When Available should be close to existing indicators.
• It should not be obtrusive (no added friction) to reflect its opportunistic nature.
• Once activated, the benefits should be immediately visible (detectable) to the user.
• It's important that the switch is reversible; users are encouraged to try out new technologies, but must have the option to switch back if they do not like what they get.

Potential Problems with ...

• Changing too little: if nothing changes after switching underlying technology, users might wonder what the benefit of the switch was.
• Changing too much: if the entire context changes (reloads with a new installation, completely different UI, etc.) then users might feel tricked into something they did not intend to.

The Take Away

Switch When Available is an opportunistic, just-in-time intervention for switching protocols without changing the overall context.

References & Where to Learn More