Trinity v2 will be a step up in IOTA's usability, bringing it on par with consumer-facing apps. It will become the human-facing entry point into the IOTA ecosystem and form an expandable open-source platform for third party developers to explore.
18 December 2019
Trinity v2 Spec
Building an open-source, composable and expandable application requires detailed, careful planning.
Releasing Trinity v2 to a closed Alpha testing group is an important step towards a production-ready product.
Beta Release is the last stage before production-readiness. The app is available publicly and following a security audit can be released in production.
Providing users with a Digital Identity adds trust to transactions. Users can improve their profile with verifiable credentials such as third-party verified KYC information.
Matrix is a decentralised, end-to-end encrypted messenger. Complementing peer-to-peer transactions with a chat system is essential for a smooth user experience.
All core logic (transactions, secret handling & storage) should take place within an account manager package. Trinity itself operates as a UI shell with certain device functionalities (camera, file system etc.) and does not execute core logic.
Trinity will provide an environment for developers to build white-label apps. Developers will be able to make use of APIs and a component library, to build solutions that leverage the functionality of Trinity and interact with the IOTA protocol.
Purchasing IOTA directly through Trinity is essential for smooth onboarding to the IOTA ecosystem. Trinity v2 will incorporate multiple options for purchasing IOTA.
Backing up one's seed is key to ensuring funds are secure. Trinity will leverage existing approaches (like SeedVault) for seamless and safe backup.
Trinity setup will be quick and effortless. Balancing security and usability, users will be able to setup their profile with ease.
Transaction History Backup
Trinity should back-up a user's transaction history for longevity (e.g. with a cloud service provider). Local state should automatically sync when users manage the same seed across multiple devices.