Feature status
What is live, what is planned, and in what order.
What is in the SDK today and what is coming. Updated as things ship.
Statuses: Live in the package and documented. In build being worked on. Planned agreed and scoped, not started. Exploring under discussion.
Live
In the alpha and beta packages, and documented here.
| Feature | Notes |
|---|---|
| Fan sign-in | Discord, Google, X, Twitch, through the OAuth proxy. Guide |
| Linking accounts | Discord, X, Twitch, Steam, Riot and more, with typed errors and expiry. Guide |
| Quests | The full loop: list, detail, all template families, submit. Guide |
| Predictions | Options, a lock, one final pick, a visible split, payout on resolution. Runs on the quest system today. Guide |
| Rewards and claims | Every reward type, and the loot box reveal. Guide |
| Quest descriptions | Structured content rendered into your design. Guide |
| Battlepass | Seasons, free and premium lanes, claim one or claim all. Guide |
| Store | Listings, filters, the purchase gate, Shopify orders, purchase history. Guide |
| Leaderboard | XP and quest boards, and the fan's own row. Guide |
| Newsfeed | The feed, members-only posts, reactions and threaded comments. Guide |
| Prizes and inventory | Prize detail forms, loot box claims, owned items. Guide |
| Personalisation | Profile pictures, borders and backgrounds, equipped per community. Guide |
| Membership | One gate across the battlepass, store and newsfeed. Guide |
| Display strings | A catalog with an i18n adapter. Guide |
The leaderboard and the newsfeed are not in the latest tag yet. Which tag.
In build
| Feature | Notes |
|---|---|
| Events | Time-boxed competitions with their own leaderboard and prizes by finishing position. Quests can already belong to an event. |
Planned
Priority order. Dates are not committed until the item moves to In build.
| Feature | Notes |
|---|---|
| Predictions as their own surface | Moving predictions off the quest system into a surface of their own. The behaviour stays the same; where your code reads it from changes. |
| Avatar system | Fan avatars beyond the three personalisation slots. |
Exploring
| Item | Notes |
|---|---|
| Self-serve community creation | Sign up, get configuration and prompts, integrate without us in the loop. |
| Non-React bindings | Core has no framework dependency, so Vue or Svelte is possible. No timeline. |
| Wallet connect | Wallet quests take a typed address today. A connector is a bigger piece of work. |
Not in the SDK
Available on the platform but through other surfaces, not these packages.
| Where it lives | |
|---|---|
| Connecting Shopify | Configured in the Hub. The SDK shows a Shopify-fulfilled purchase and its delivery status, but never talks to Shopify itself. Shopify orders. |
| Buying or upgrading a membership | Your own checkout. The SDK reads membership and gates on it. Membership. |
| Admin and content creation | The Hub. Quests, seasons, listings and posts are all created there. Deliberately not in a client SDK. |
| Community data export | Data API with an API key. Server-to-server. |
Asking for something
If a Planned item is what decides your integration, tell your FanBase contact. Partner demand moves this list.