Brierly docs
v1.0.0
Get help
● Documentation · Flutter · Node.js

Brierly
from download to your own forecasting trainer.

Brierly is an Android and iOS app that trains forecasting skill. For each public question the user commits their own probability before seeing the crowd, then gets a Brier score and a calibration curve. This guide takes you from the download to a branded build in the stores, step by step. Read it top to bottom the first time; after that, press / and search.

v1.0.0Flutter · Android · iOS 16+Node.js server with operator consoleEducation, not betting

01What you bought

Brierly is complete, white-label mobile app source code plus a small server with an operator console. The user opens a public question, drags a slider to set their own probability of Yes (1 to 99 percent) with the crowd's odds hidden, and seals the call. Only after that does the app show what the crowd thought. When the question is decided, the app computes the user's Brier score, draws a calibration curve (reliability diagram) and compares the user with the crowd on the same questions. A Pro tier, sold through in-app purchases, lifts the weekly call limit and the history limit. All forecasts and scores stay on the phone.

What it is not

Brierly is a forecasting-skill trainer for learning to estimate, nothing more. It has no wallet, no order buttons, no advice and no link to any market's own page. Please describe your app the same way in your store listing.

PartFolderWhat it is
Mobile appapp/Flutter project for Android and iOS. Without a server it runs on its own: no questions arrive (an honest empty state is shown) but history and scores still work.
Serverserver/Node.js backend that serves the questions, with an operator console: choose the question source, hide or feature questions, add your own, resolve them, change the paywall, features, announcement and force update without a new build, and optionally confirm purchases with the stores.
Contractcontract/CONTRACT.mdThe calls between app and server, with example JSON.
Question list with this week's set
Question list · Live public data
Calibration screen with Brier score and reliability diagram
Calibration card · Sample data

02Folder map

PathWhat is inside
app/lib/brand.dartApp name, tagline, accent colour, fonts, default attribution line, support/privacy/terms links, default store product ids, server address. The one file for rebranding.
app/lib/src/Dart code: core/ (models, scoring, config), data/ (SQLite store of calls), services/ (controller, purchases, question API, config client, ping, settings), ui/screens/ (Home, Question, Calls, Calibration, Settings, Paywall, Onboarding, Update).
app/android/Android project (MainActivity.kt is the standard activity).
app/ios/iOS project, PrivacyInfo.xcprivacy and the Swift app and scene delegates.
app/assets/fonts/Instrument Serif, Instrument Sans and DM Mono fonts with their licence texts.
app/tool/make_icon.pyScript that draws the app icon.
app/test/Automated tests (scoring, blind call, config, paywall, screens).
server/src/TypeScript server: app.ts (routes), market.ts (question sources), questions.ts (storage), purchases/ (App Store and Google Play checks), admin/manifest.ts (what the console shows).
server/packages/admin-kit/The operator console (MIKODES Admin Kit), licensed with this item.
server/.env.exampleEvery server setting, with comments.
server/DockerfileContainer build for the server.

03How it fits together

The app keeps every forecast on the phone. The server serves the questions and settings. The phone never calls the question source itself: your server does, keeps its own cache, and hands out the crowd's odds only at the moment a call is sealed. Arrows point from the part that calls to the part that answers.

Brierly architecture The phone app keeps calls and scores in a local SQLite database. It calls routes on your Node server: GET /v1/config, GET /v1/questions, GET /v1/questions/:id/crowd at the moment of sealing, POST /v1/resolutions, and optionally POST /v1/ping, the leaderboard routes and POST /v1/purchases/verify. The server stores settings and questions in SQLite, is managed through the operator console at /admin, reads a public question source such as Manifold Markets, and calls the Apple App Store Server API and the Google Play Developer API to verify purchases if switched on. The app buys through the Apple and Google stores directly. Phone app (Android, iOS) Local SQLite: your calls, scores, calibration. Crowd hidden until sealed. app/lib/ android/ ios/ Apple and Google stores In-app purchase: lifetime, yearly, restore (in_app_purchase). buy, restore Your server server/src/ Node.js, Hono GET /v1/config GET /v1/questions (no odds) GET /v1/questions/:id/crowd POST /v1/resolutions optional: ping, leaderboard, verify SQLite files in data/DATABASE_PATH Operator console Browser, /admin. Sign-in with two-factor. Source, questions, paywall, announcements. edits settings Question sourcepublic API, read by the server AppleApp Store Server API GooglePlay Developer API Forecasts and scores never leave the phone. The phone never calls the question source; only your server does.
Architecture: app, server, console, question source and store APIs

04Quick start (about 20 minutes)

Windows users

Flutter runs natively on Windows: use PowerShell for the flutter commands and Android builds (iOS builds need a Mac). For the server, either install Node.js 22.12+ for Windows and use PowerShell (replace cp .env.example .env with Copy-Item .env.example .env; there is no openssl by default, so use WSL or any random 64-character hex string), or run the commands in WSL 2 (Ubuntu) or Docker. macOS and Linux users can ignore this note.

  1. Install Flutter 3.41 or newer (see Requirements) and run flutter doctor until it shows no red items for the platform you want.
  2. Start the server (it provides the questions).
    cd server
    cp .env.example .env
    openssl rand -hex 32        # paste the result after ADMIN_SECRET_KEY= in .env
    npm ci
    npm run build
    npm start
    Open http://localhost:8787/admin and follow First sign-in. Check that questions arrive: curl http://localhost:8787/v1/questions.
  3. Run the app against it.
    cd app
    flutter pub get
    flutter test
    flutter run --dart-define=API_BASE_URL=https://your-server.example.com
    Connect an Android phone with USB debugging on, or start an iOS simulator. The address must be https: the project sets no plain-http exception, so a http://localhost address is refused by current Android and iOS (see Installation). Without API_BASE_URL the app still runs, with an empty question list.
  4. Rebrand. Follow Rename and rebrand: name, package id, bundle id, icon, colours.
  5. Choose your question source and read its terms: Market data source.
  6. Create the store products and put their ids in the app or the console: Store products.
  7. Build and publish: Release builds and signing.
Demo console

A read-only demo of the operator console is at https://brierly-demo.mikodes.com/admin. Email: demo@brierly.demo · Password: brierly-demo-2026 (read-only demo account).

05AI tools

AI tools were used to assist with parts of the code, documentation and graphics of this item. The author reviewed and tested the result. The product itself contains no AI features.