HTML5 · Product Manager · IAP Catalog Design guide
Use a browser-playable HTML5 context to produce a catalog and acceptance brief. Own offer scope, price ladder, free baseline, release policy, support ownership, and measurable acceptance criteria; 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 product manager reviews item scope, price ladder, free baseline, and catalog overlap and delivers a catalog and acceptance brief. Acceptance means the team can state who the offer serves, what remains free, which outcome is accepted, and who owns refunds or support escalation.
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.
Keep the catalog small and the player promise precise. Use the prototype to decide whether the idea deserves engineering effort, not to forecast revenue.
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 voluntary game item, its preview, full price in Koin, visible 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 cancellation, not enough Koin, pending, interrupted delivery, and reload visually distinct, with a safe next action.
Define the player need, item scope, ownership rule, Koin price, and free path. Check age context, accessibility, rights, and platform expectations. Use the prototype to resolve player-facing questions before creating platform integration tasks.
For a game product manager, this catalog design prototype should make every player action and result the player can inspect easy to evaluate. Write how to define item identity, value, Koin price, preview, and ownership before checkout. Define the player need, item scope, ownership rule, Koin price, and free path. Check age context, accessibility, rights, and platform expectations. 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.
State which player problem the item addresses, why a purchase is appropriate, and what evidence would cause the team to drop the idea. The prototype supports a product decision; it does not forecast revenue.
Ask testers to complete the same goal with and without the item. Look for comprehension, pressure, fairness, and delivered value rather than using purchase completion as the only measure of a good experience.
Review age context, accessibility, localization, rights, moderation, platform policy, refunds, support, and security with the responsible owners. Keep unverified native capabilities and financial reporting out of the public promise.
Use the same fields for every offer: preview, benefit, ownership or duration, clearly stated Koin cost, 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
Define the player need, item scope, ownership rule, Koin price, and free path. Check age context, accessibility, rights, and platform expectations.
Result: Product manager focus
Ask players what they expect before confirming and what they received afterward. Remove pressure language and unsupported platform claims. Repeat the test after interruption and reload.
Result: A stable prototype
Create a shareable browser session for a game product manager. 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 product manager must be able to balance player clarity, catalog scope, and release risk. 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 specific Koin amount, current Koin balance, confirm, cancel, low-balance, success, visible delivery, and reload states.
Own offer scope, price ladder, free baseline, release policy, support ownership, and measurable acceptance criteria. Coordinate adjacent work, but keep the page's acceptance artifact specific to this role.
Deliver a catalog and acceptance brief 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