Build a game

Cosmetic IAP hub

Design cosmetic items players can judge before buying

Cosmetics work when the player can see the difference, understand the exact price, and keep the complete play loop without paying.

See the worked examplePlay the reference game
Authentic Block Matrix gameplay used as context for cosmetic iap testing
Real gameplay context: Block MatrixUse the playable result to evaluate placement and UI state—not as proof of a completed transaction.

Concrete design brief

Worked example: a 40 Koin matrix trail

Preview the cyan trail on the active piece, label it “Matrix Trail · cosmetic only,” and show 40 Koin beside the confirm button. On success, add it to owned effects and equip it; on cancel or insufficient balance, leave the run unchanged.

Open the playable result →

Required state chain

Specify the whole IAP flow

  1. 01

    Preview item on the player avatar or board

  2. 02

    Show “40 Koin” and cosmetic-only scope

  3. 03

    Offer separate Confirm and Cancel actions

  4. 04

    Handle insufficient balance without blocking play

  5. 05

    Deliver to owned items and show Equip

  6. 06

    Reload and verify ownership and equipped state

Before release: replace mocked balances and local flags with authenticated transaction records, idempotent delivery, platform-required consent, security review, and a support/refund process.

Related IAP design hubs

Move to the closest purchase intent

Content unlock Consumable IAP Convenience IAP Purchase flow testing Player trust

Focused questions

Cosmetic IAP FAQ

Should a cosmetic change gameplay stats?

No. If it changes power, speed, access, or rewards, describe and evaluate it as a functional offer rather than a cosmetic.

What belongs in a cosmetic preview?

Show the exact appearance in its real gameplay context, the item name, whether it is permanent, and the full Koin price.