Built in the open

Build activity

What people are building with Vibe1Up, counted honestly.

Every number here is a real recorded action. How we count.

From idea to first prompt

📈 Tracking started Oct 16. Numbers coming soon, once we have a full week of data.

Recipes copied

Soon

Successful clipboard writes, daily-deduplicated per recipe.

Tracking started Oct 16.

Remix buttons clicked

Soon

A press of “Remix this,” not a completed remix.

Tracking started Oct 16.

Slot Machine spins

Soon

Completed user-requested generations. Initial automatic ideas do not count.

Tracking started Oct 16.

What has evidence behind it

Current published snapshots. These two totals are not affected by the action-window buttons.

Creator-confirmed prompts

—

Distinct public games with a creator-confirmed prompt. This is not a fresh reproduction test.

Reproduced Starter recipes

—

Distinct Vibe1Up recipes with a published fresh-session test record. See the Classic test.

How we count

Each copy, Remix click or Slot Machine spin counts once per visitor per day. We never store IP addresses or show anything personal, and we never fill gaps with estimates.

Full counting rules

Copies and Remix clicks: Counted once per event, recipe/game and UTC day using a browser guard and a daily salted server hash of the request's IP and user agent. People can share an address or change browsers: these are approximate daily-deduplicated actions, not unique people. Only successful clipboard writes trigger a copy event.
Slot Machine spins: A spin is recorded after a user-requested result finishes rendering. A new nonpersistent nonce separates spins; retries with the same nonce overwrite the same record. The automatic first idea and unfinished spins are excluded. Spin tracking begins with this release; no past spins are backfilled.
Recorded total and dates: Totals cover valid events still retained in our counter storage, not activity before tracking existed or failed requests. Each card shows its first retained UTC event date, or says no events have been recorded. UTC windows use the event's original day key, not a later retry's upload timestamp.
Creator-confirmed prompts: One count per distinct public catalog game explicitly flagged as having a creator-confirmed prompt. Duplicate catalog entries are collapsed. Private or unpublished submissions are not included. Several prompts for one game still count as one public game.
Reproduced recipes: One count per distinct recipe with a published “reproduced” record, not per model run or output. Every record names its recipe version, model, test date, exact prompt and result, plus limitations. It does not certify someone else's original prompt or all variants.
Privacy and limitations: This page returns only anonymous aggregate counts. No report keys, raw IP addresses, user agents, visitor hashes, private submissions or individual browsing histories are published. Obvious bots are filtered, but client-triggered analytics are not fraud-proof or a complete census. Failed delivery can undercount. Totals may be cached for a few minutes. If storage is unavailable, the page says so instead of pretending there were zero actions.

Make the next one yours

Start with one small mechanic and a recipe that has actually produced a playable result.

Make a gravity-flip game with AI Spin a new game idea