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.

FeatureNotes
Fan sign-inDiscord, Google, X, Twitch, through the OAuth proxy. Guide
Linking accountsDiscord, X, Twitch, Steam, Riot and more, with typed errors and expiry. Guide
QuestsThe full loop: list, detail, all template families, submit. Guide
PredictionsOptions, a lock, one final pick, a visible split, payout on resolution. Runs on the quest system today. Guide
Rewards and claimsEvery reward type, and the loot box reveal. Guide
Quest descriptionsStructured content rendered into your design. Guide
BattlepassSeasons, free and premium lanes, claim one or claim all. Guide
StoreListings, filters, the purchase gate, Shopify orders, purchase history. Guide
LeaderboardXP and quest boards, and the fan's own row. Guide
NewsfeedThe feed, members-only posts, reactions and threaded comments. Guide
Prizes and inventoryPrize detail forms, loot box claims, owned items. Guide
PersonalisationProfile pictures, borders and backgrounds, equipped per community. Guide
MembershipOne gate across the battlepass, store and newsfeed. Guide
Display stringsA catalog with an i18n adapter. Guide

The leaderboard and the newsfeed are not in the latest tag yet. Which tag.

In build

FeatureNotes
EventsTime-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.

FeatureNotes
Predictions as their own surfaceMoving predictions off the quest system into a surface of their own. The behaviour stays the same; where your code reads it from changes.
Avatar systemFan avatars beyond the three personalisation slots.

Exploring

ItemNotes
Self-serve community creationSign up, get configuration and prompts, integrate without us in the loop.
Non-React bindingsCore has no framework dependency, so Vue or Svelte is possible. No timeline.
Wallet connectWallet 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 ShopifyConfigured 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 membershipYour own checkout. The SDK reads membership and gates on it. Membership.
Admin and content creationThe Hub. Quests, seasons, listings and posts are all created there. Deliberately not in a client SDK.
Community data exportData 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.

On this page