Development Roadmap: Dec. '22
Now that TIKI’s 1.0 infrastructure and SDKs are live, here’s what we have planned for roughly the next 3 months of development.
Keep in mind that the roadmap will inevitably change almost immediately after I hit publish. Projects always take longer than expected, and as developers, our eyes tend to be bigger than our stomachs.
If you would like to get involved and help contribute, join us on Discord.
Point person(s): Ricardo, with UX support from Vignesh
Example apps and demos to showcase common use cases and provide sample code to make it easier to get started building with TIKI.
Templated UX with a simple style configuration that a) makes TIKI fit in stylistically with any App and b) so devs don’t have to waste time building things like popups.
JS SDK (stretch goal: react/react native) to add TIKI to websites/webapps. A side benefit of a JS SDK is JS can be executed from a wide variety of other languages like Golang and Rust, opening up a whole new suite of native SDKs that can be created.
Example integrations and how-tos on using TIKI with common third-party tools like Stripe, Amplitude, Segment, LiveRamp, etc.
API v1.1 from our learnings in building our first apps, demos, and examples with API 1.0.
Point person(s): Mike
Multi-address registry; a single API to join multiple addresses. It’s not uncommon for users to be logged into an App on their phone, tablet, and browser. A compound address simplifies implementation for developers.
Transaction index to build a searchable API as blocks are written to our L0 Storage service —simplifies cross-chain syncing and querying.
Webhook execution engine and registry for developers to add async backend behavior to their applications triggered by block ingestion for events like consent modification or reward termination.
Common query endpoints (stretch goal) for easily fetching results like “retrieve total loyalty points issued for a given address.”
Point person(s): Mike and Ricardo
Reward tokenization to issue custom on-chain value-backed NFTs. A simple use case is loyalty point issuance based on data-driven actions/transactions.
Point person(s): Barry, with UX support from Vignesh
Whitepaper published, shared, and vetted by the community detailing the tokenomics, voting, and proposal structures.
1.0 of DEX Guidelines drafted and published becomes the starting point for the crowdsourced governance powered by the TIKI DAO —it’s far more productive to modify a living doc than start from a blank page.
UX wireframes for each required TIKI DAO action. These high-fidelity wireframes will become the relaunched TIKI app.
Point person(s): Tim, with support from Mike and Ricardo
Contributor process; a well-documented procedure for how to start contributing to TIKI’s code base, setting up a development environment, and how code is vetted, merged in, and deployed.
Contributor compensation programs to fairly reward the community for their hard work in maturing the TIKI codebase.
Community engagement schedule of events, programs, outreach, etc., to not just build awareness but, more importantly, get talented eyes on what we’re building.
Usage/utilization chats and metrics for developers to quickly inspect adoption rates —the stretch goal is to include KPIs for ownership and consent opt-in.
TIKI Scan; etherscan but for the TIKI chain.
Billing (stretch goal) is a lower priority as we’re focused on adoption and delivering valuable features —consumption-based billing will roll out as we gain a better feel for customer uptake.