Design Review Call #3

[ConorOkus]

Date: 2020-10-12
Time: 16:00
TimeZone: UTC
UTCTime: 2020-10-12T09:00:00.000-07:00
Duration: 1h - 1h 30 mins approx

Agenda

Bitcoin Name System - @ildarmgt
Concept Mapping - @AlexaAker
Carrot - @pat-riley
Private Key Management Illustrations - @danielnordh

Check your timezone

https://everytimezone.com/zones?t=5f839c80,3c0

Join the call

https://meet.jit.si/bitcoindesign

[pat-riley]

Would love to present Carrot (http://earncarrot.com/) which we just moved into Beta

[ConorOkus]

Summary

Concept Mapping - @AlexaAker
Alexa showed some cool illustrations she is working on that we can look to use in the design guide and also more widely across the Bitcoin ecosystem as an open-source resource library. Still early days but looking into best ways to make this collaborative with Figma probably being the preferred solution. We also looked at her very detailed concept mapping aimed at helping to educate users depending on what path they are most interested in. This lead to some discussion around gamification to make Bitcoin education fun and developing some character illustrations that users feel they can identify with.

Carrot - @pat-riley
Carrot provides a way for users to earn sats by supporting their favourite brands. Pat gave us a great demo on how Carrot works and why a brand would want to use it. The onboarding flow seems right in line with the Bitcoin ethos of not needing to provide identification in order to use the system. This has been implemented using Magik links so the user doesn't need to remember a user name and password in order to log in. Some smaller points around copy were raised, the landing page heading is "Support Their Mission" and is not always clear who they are? There is perhaps also some friction around redeeming codes requiring you to enter an email before you can get access.

Private Key Management Illustrations/Scheme - @danielnordh
Here we looked at a diagram that would help people decide what scheme was most suitable for a particular use-case with regards to private key management. The idea is that we have a spectrum of private key management that might be suitable for different use cases e.g tips or pocket change might benefit from some type of automatic backup in the cloud whereas life savings may need a multi-key distributed backup. The scheme is only in V1 but some things to consider moving forward are progressive security improvements as a user moves through the spectrum and ensuring we don't blur the line too much between what is deemed low value and high value.