Considering the very wide scope of work, and the necessity to ramp-up operational and business processes while simultaneously shipping software, it’s proposed that tactical (short term) builds can be preceded by strategic (longer term). Such decisions can be made by the project’s tech lead, for each section of the project. This approach will support early grant raising and capital raising activities, since a product and revenue flows will be observable early-on.
- Tactical:
- Quick and simple plays to gain early advantage
- Likely to be relatively centralised (i.e. use of hosting services)
- Will include components that are later dropped in favour of better alternatives
- Strategic:
- Longer term game
- Maximally decentralised
- Maximally anti-fragile
We think that a Progressive Web App ‘PWA First’ approach – with good optimisation across devices – is probably an optimal tactical approach, since it’ll provide resilience to delisting by centralised app stores.
A quick initial build will likely comprise a few specific open source stacks, and will allow us to on-board suppliers, acquire low cost product lines (stickers etc.), set-up affiliate and dropshipping arrangements, and acquire early users.
- Tactical build components might include:
- MedusaJS / WooCommerce
- CoinOS or similar
- URL’s to Keet (to initiate chat sessions within Keet app)
- Strategic build components might include
- Pear-Holepunch
- Pubky
- Propitiatory Ark / Second.tech
- Keet module integrated
We are not considering Nostr for any part of the project; it is insufficiency decentralsied and suffers from irreparable design & architecture flaws.
