Sample Apps

Sample apps are PoC applications that are for testnet purposes only (aka, not mainnet). They are created to demonstrate the feasibility of a desired project. They can become a template for developer to build said desired projects and push it to production/mainnet. They can also serve as:

• Example on how to build on the Logos stack.
• Demo applications
• Dogfooding vector to test specific features of the Logos stack

Deliverables

A sample app release is considered shipped once the following assets are delivered:

• Code for the sample app: In a public repo with right licencing.
• FURPS+: On the present repo in the sample apps’ page in desired_projects folder. The FURPS+ define the behaviour of the sample app for a given release.
• Architecture Decision Records: On the present repo in the sample apps’ page in desired_projects folder. The Architecture Decision Records lay out specific decisions made regarding the choices in terms of design and protocol, to help developer understand those choices as they build with the sample app as example. This may contain some protocol diagrams or specs depending on the complexity of the app
• Dependencies: specific features of the Logos stack that the sample app depends on.

Tracking

Each release of a sample app is tracked with a milestone on the present repo.