The present document describes the proposed changes to Copay.
Be competitive. Win market share. Redesigned with a user-centered approach. Great proof-of-concept, move from the prototype stage to something usable.
- The need to remember several passwords (one peer wallet).
- The need to administrate and securely store several backups (one peer wallet).
- Only can receive notifications of activity from one wallet at a time.
- Switching between wallets it's a PITA.
- The lack of a proper transaction history or account balance report.
- Unfriendly for no-technical people (Displays a lot of: IDs, Outputs/Inputs, Timestamps).
- Encourages addresses reuse.
- Friendly for human beings, no technical knowledge required.
- Designed for personal AND shared wallets.
- Offer relevant information about your money and how you spend it.
- Creates a user profile, with name and picture.
- A user can have several wallets, to store personal and shared founds.
- A user handles only one password.
- A user manages only one backup file for his account (updated regularly)
- Notifications works at the profile scope, across all wallets.
- Hide addresses wherever it's possible and focus on the user cases.
Copay should be an open source wallet library, with pluggable implementations of backing services (e.g. storage, networking, blockchain). This library will be used by the web, desktop and mobile distributions of copay, but also by smart agents and third party software providing services like risk-analysis, two-factor authentication/signing, etc.
- Works on node and on the browser.
- Asynchronous and event oriented interface (Promises/A+).
- Modular and pluggable implementations.