HTML5 · Game Designer · IAP Catalog Design guide
Use a browser-playable HTML5 context to produce an annotated player-flow specification. Own screen hierarchy, offer timing, readable choices, and visible feedback; treat the result as a workflow prototype, not proof that native billing is connected.
Create this game flow
Focused keyword and player case
Prototype a three-item catalog with one cosmetic, one bounded consumable, and one optional content pack. The game designer reviews item scope, price ladder, free baseline, and catalog overlap and delivers an annotated player-flow specification. Acceptance means a player can preview the offer, decline it, recover from low balance, and explain the delivered result without coaching.
Use the focused IAP Catalog Design hub for an authentic screenshot, direct playable result, and the complete purchase-state checklist. Gameplay evidence supports placement testing; it does not prove a live transaction.
Start with player motivation and the core loop. The item should support a goal players already understand rather than remove deliberately created frustration.
Design for the input, layout, interruption, and return behavior players expect from HTML5 games.
Browser delivery does not prove native store billing or platform approval.
Show one item that remains optional, its preview, clearly stated Koin cost, available Koin balance, and ownership rule in a layout suited to HTML5 games.
Write how to define item identity, value, Koin price, preview, and ownership before checkout. Keep each change visible to the player rather than hiding it in technical state.
Make cancelling the action, an insufficient balance, pending, interrupted delivery, and reload visually distinct, with a safe next action.
Choose the offer moment, explain the game benefit, and protect the complete free path. Compare the experience before and after ownership. Use the prototype to resolve player-facing questions before creating platform integration tasks.
For a game designer, this catalog design prototype should make every player action and clearly displayed outcome easy to evaluate. Write how to define item identity, value, Koin price, preview, and ownership before checkout. Choose the offer moment, explain the game benefit, and protect the complete free path. Compare the experience before and after ownership. Assume a player may open the game from a link in a new browser with limited prior context. Put item identity, Koin balance, and the return route inside the playable experience.
Try refresh, back navigation, a second tab, and returning after the page was suspended. A browser interaction must not imply native-store ownership or silently repeat a delivery action.
If the game uses a canvas, make focus, keyboard input, scaling, and purchase overlays cooperate. Closing the choice should restore game controls without leaving hidden buttons or trapped focus.
Run the game without opening the purchase choice, then run it with the item. Compare pacing, motivation, difficulty, and recovery so the offer supports play instead of repairing frustration that was added deliberately.
Describe what changes on screen, how long it lasts, where it appears, and what remains available without it. Replace value labels such as better or premium with rules a player can observe.
Check what the player was doing immediately before the offer and where cancel returns them. The item should arrive after enough context to understand it, but never during a time-critical or emotionally pressured action.
Use the same fields for every offer: preview, benefit, ownership or duration, full price in Koin, and owned state. Consistent cards make differences easier to understand. Test that behavior using HTML5 games. Browser delivery does not prove native store billing or platform approval.
Start with one to three clearly different items. A large grid makes it harder to find unclear value, duplicated promises, and missing delivery states. Test that behavior using HTML5 games. Browser delivery does not prove native store billing or platform approval.
A catalog also needs sold, owned, equipped, and unavailable presentations. Do not leave a purchased item looking buyable after reload. Test that behavior using HTML5 games. Browser delivery does not prove native store billing or platform approval.
Choose the input and screen behavior for HTML5 games. State the platform limit beside the prototype brief.
Result: An honest scope
Write how to define item identity, value, Koin price, preview, and ownership before checkout. Describe the player action and visible response at each point.
Result: A clear catalog design sequence
Show the item, exact price, balance, confirm, cancel, pending, success, and delivery without payment-provider screens.
Result: A complete player journey
Choose the offer moment, explain the game benefit, and protect the complete free path. Compare the experience before and after ownership.
Result: Game designer focus
Play cancellation and a full session without purchase. Check timing, value, competitive impact, and whether the item matches the delivered result. Repeat the test after interruption and reload.
Result: A stable prototype
Create a shareable browser session for a game designer. Focus the IAP prototype on define item identity, value, Koin price, preview, and ownership before checkout. Use a direct Koin item transaction with preview, exact price, confirmation, cancel, insufficient balance, success, delivery, and reload behavior. The game designer must be able to connect the offer to the core loop and player motivation. Do not add subscriptions, payment-provider UI, revenue analytics, or native platform claims. State this boundary: Browser delivery does not prove native store billing or platform approval.
Keep the item optional. Show its precise Koin price, balance before spending, confirm, cancel, low-balance, success, visible delivery, and reload states.
Own screen hierarchy, offer timing, readable choices, and visible feedback. Coordinate adjacent work, but keep the page's acceptance artifact specific to this role.
Deliver an annotated player-flow specification that records item scope, price ladder, free baseline, and catalog overlap, named owners, failure states, and the next production verification step.
No. Production release still requires authenticated records, security, refunds, platform compliance, monitoring, and support procedures.
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