|
|
|
Here is a quick summary of the first UX meeting with Ame from simply-secure. (25-4-18)
|
|
|
|
|
|
|
|
# Name Choice
|
|
|
|
Throuout the meeting it became clear that we might want to reconsider the naming.
|
|
|
|
|
|
|
|
> "Repeater" does not really relate to what it does.
|
|
|
|
|
|
|
|
+ Mailbox
|
|
|
|
+ Storage Box
|
|
|
|
+ Hold Box
|
|
|
|
+ Answering Machine
|
|
|
|
+ **Later Box**
|
|
|
|
|
|
|
|
Later Box because it stores messages to be pulled _later_.
|
|
|
|
|
|
|
|
This lead to the **Briar Later** idea.
|
|
|
|
|
|
|
|
# 1 Sentence Description
|
|
|
|
|
|
|
|
> Briar Later is a private message box for Briar messaging users to send and receive messages when 1 person is offline
|
|
|
|
|
|
|
|
> Briar Later is message holding box that lets you send and receive Briar messages when 1 person is offline
|
|
|
|
|
|
|
|
|
|
|
|
# More on Description
|
|
|
|
|
|
|
|
> A Briar user can set up a **Later Box** that is always online and can privetly hold messages until the sender or receiver is online
|
|
|
|
|
|
|
|
> If I set up a **Later Box**, it automatically holds messages I send that can't be delivered and waits until the other person comes back online. **Later Box** also holds all messages for me if I'm unavailable, and when I come back online I get them _in Briar_ from my **Later Box**
|
|
|
|
|
|
|
|
# Design/SetUp
|
|
|
|
1) Identify hardware (e.g. old phone/raspi)
|
|
|
|
2) Download App
|
|
|
|
3) Give bluetooth permission
|
|
|
|
4) Follow setup/scan barcodes
|
|
|
|
5) Choose communication channel (bluetooth/wifi/tor)
|
|
|
|
6) Show dashboard with important information
|
|
|
|
|
|
|
|
> No need to tell my Briar contacts that I have a _Later Box_. Messages and contact information exchange is handled automatically
|
|
|
|
|
|
|
|
# Visualisation |
