SEELE AIStart creating

Families and Parent-Guided Players · Player-first Koin purchase UX

Koin Optional-Only Purchase Design for Families and Parent-Guided Players

Design one optional Koin item around the real needs of families and parent-guided players. This guide applies optional-only purchase design to the offer, confirmation, a cancelled choice, recovery, and delivered result.

Create this game flow
Koin Optional-Only Purchase Design for Families and Parent-Guided Players visual reference
Visual reference only. Your generated game follows the prompt you choose.

Start with what families and parent-guided players need

Audience need

The experience must use adult-controlled prompts, clear age context, and no child-account assumptions.

Design principle

Preserve a complete playable path and avoid selling relief from deliberately created frustration.

Small first scope

Use one item and one Koin price so players can evaluate the complete choice without navigating a large shop.

Optional-Only Purchase Design in practice

Offer moment

Choose a calm point where families and parent-guided players understand the game context and can decline without interrupting active play.

Offer card

Show the item, benefit, duration or quantity, specific Koin amount, current Koin balance, confirm, and cancel in plain language.

Safe recovery

After a cancelled choice or an insufficient balance, preserve progress and return families and parent-guided players to an understandable game state.

Visible delivery

When the action completes, show ownership, equipped state, unlocked content, or remaining quantity where the item will be used.

Apply optional-only purchase design throughout the flow

Review the shared family decision

Keep adult guidance visible, avoid guessing who controls the Koin balance, and let a parent or guardian dismiss the choice without changing the child-facing game. Use age-appropriate wording and never imitate consent or child-account systems that the prototype does not provide.

Prove that declining leaves a complete game

Play the advertised core route from the first meaningful action through recovery and its promised conclusion without opening the offer. Record any place where storage, pacing, difficulty, retry access, story information, or social participation feels intentionally weakened. Decline the item at several natural moments and confirm that progress continues from the same point without repeated pressure. Then buy it and compare the owned experience against the free route: the item may add expression, bounded content, or reasonable convenience, but it must not reveal that frustration was manufactured to sell relief. Remove guilt, countdowns, loss threats, and language that treats a voluntary choice as required.

Finish the free path first

Play the complete promised game without opening the offer. Progress, recovery, and the core ending should still feel intentional. For families and parent-guided players, the experience must use adult-controlled prompts, clear age context, and no child-account assumptions.

Offer an easy decline

Give players a visible dismiss action and return them to the exact game state they left without repeated pressure. For families and parent-guided players, the experience must use adult-controlled prompts, clear age context, and no child-account assumptions.

Do not sell relief from frustration

Avoid slowing ordinary progress or creating unnecessary limits simply to make the non-required item feel required. For families and parent-guided players, the experience must use adult-controlled prompts, clear age context, and no child-account assumptions.

Design the flow in five steps

  1. 1. Start with the audience requirement

    Write this into the prompt before the item description: Use adult-controlled prompts, clear age context, and no child-account assumptions.

    Result: A clear design constraint

  2. 2. Apply optional-only purchase design

    Preserve a complete playable path and avoid selling relief from deliberately created frustration. Carry the same principle through confirmation and delivery.

    Result: A consistent player experience

  3. 3. Define one voluntary game item

    Name the benefit, duration or quantity, ownership rule, precise Koin price, and delivered result.

    Result: An understandable offer

  4. 4. Playtest with families and parent-guided players

    Try confirmation, a player cancellation, too little Koin, repeated input, interruption, delivery, and reload without coaching.

    Result: Audience-specific feedback

  5. 5. Revise the unclear moment

    Change one prompt instruction, regenerate, and compare whether players understand the choice more quickly.

    Result: A focused second version

Generate it in SEELE

Prompt 1

Create a browser-playable game purchase-flow prototype for families and parent-led players. Optimize for optional-only purchase design: preserve a complete playable path and avoid selling relief from deliberately created frustration. Apply this audience requirement: use adult-controlled prompts, clear age context, and no child-account assumptions. Use one item that remains optional priced directly in Koin with preview, explicit confirm and cancel, insufficient-balance feedback, success, and visible delivery. Do not include subscriptions, revenue reporting, payment-provider UI, or guaranteed outcomes.

Prompt 2

Keep the item optional. Show its specific Koin amount, current Koin balance, confirm, cancel, low-balance, success, visible delivery, and reload states.

Playtest with families and parent-guided players

Before this flow goes live

Frequently asked questions

Why does optional-only purchase design matter for families and parent-guided players?

It makes the choice easier to understand while respecting this audience's needs.

Is this a subscription?

No. The player spends Koin directly on one named item or unlock.

What happens if the player cancels?

Return to the same game state without spending Koin or delivering the item.

What if the Koin balance is too low?

Explain the shortage, preserve progress, and do not deliver the item.

Does this include payment or revenue reports?

No. It covers the player-facing purchase experience, not financial reporting.

Is the prototype ready for a native store?

No. Identity, persistence, security, refunds, native APIs, policy, and accessibility still need production work.

Build a optional-only purchase design prototype

Open the complete prompt in SEELE, adjust the item and Koin price, then generate a playable version you can test.

Open this prompt in Workspace