Creator Guide
What is a Post?
A Post is a short game that lives in a feed. Players open the app, see your game, and play it right there: no downloading, no signing up, no reading instructions. Like a short video: a beginning, an end, and enjoyable with no prior context.
The Most Important Thing to Understand
Every Post is an entry point. The recommendation engine shows your games in no particular order. If you make a puzzle game with 600 puzzles, puzzle #572 might be the first one a player ever sees from you.
Every Post must work as a complete experience for someone who has never played your games before.
What a Post Looks Like
One short play session with a clear ending:
- One puzzle
- One level
- One run with a fixed number of lives
- A timed challenge
The player should always know what they are doing and when it is over.
What a Post is Not
The enforced gameplay rules (no progression systems, no monetisation, no accounts, no in-game leaderboards, no social features) live in Platform Requirements. Also off-limits: push notifications and re-engagement mechanics. You cannot prompt players to come back.
A brief tutorial on first play can help players get started. If you use the npm package, build one with the SDK overlay described in Interactive Tutorials.
A Simple Test
- Can someone understand what to do within a few seconds?
- Does it have a clear ending?
- Does it feel complete, not like a teaser?
Good example: Wordle. You open it, you know what to do, you guess the word (or you don't), and it is over. That is a Post.
Connecting to the Platform
Report a result once the session ends. It's how the platform rewards the player and closes the run:
// score is the final score from your game's own state
window.minit.reportResult(score);
The full API (score semantics, flavorText, delay) is in Reporting Results.
How Distribution Works
- Sessions where players stay engaged to completion count more strongly.
- Cheers (player reactions) are a strong positive signal.
- New content receives a boost: freshly published Posts are preferred.
Difficulty & Content Strategy
- Easier Posts drive higher engagement from new players.
- Harder Posts resonate more with your existing fans.
- Alternate between easy and hard releases to serve both.
Tip: Soften early failure. If a player can fail quickly, offer a gentle retry rather than immediately reporting the result. Keeping the player in the session drives distribution.
Live Operations
Release on a regular cadence, ideally daily: consistency plus the fresh-content boost maximizes your presence in the feed.
Technical Requirements
Every technical constraint, and every number, lives in Platform Requirements. The short version:
- Built for the feed: portrait, responsive, instantly playable, touch-driven.
- One bundle shape: a single self-contained ZIP.
- The SDK is the bridge: results via
reportResult, per-player persistence via userData (Saving User Data), never browser storage.
For the upload flow itself, see Your First Game.