Product manager focus
Keep the catalog small and the player promise precise. Use the prototype to decide whether the idea deserves engineering effort, not to forecast revenue.
Game Product Manager guide · HTML5 Games · Koin purchase UX
Game Product Manager Guide to Koin Catalog Design for HTML5 Games
Use a browser-based playable build to work through catalog design for HTML5 games. The goal is to make the player journey concrete before the team commits to native commerce implementation.
Create this game flow
Define the HTML5 games scope
Platform context
Design for the input, layout, interruption, and return behavior players expect from HTML5 games.
Prototype boundary
Browser delivery does not prove native store billing or platform approval.
Catalog Design in practice
Starting state
Show one voluntary game item, its preview, full price in Koin, Koin balance now, and ownership rule in a layout suited to HTML5 games.
Main task
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.
Recovery
Make cancellation, not enough Koin, pending, interrupted delivery, and reload visually distinct, with a safe next action.
Role decision
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.
Solve the catalog design details
Design for a shareable session
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.
Handle tabs and navigation
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.
Keep canvas and interface coordinated
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.
Write the decision before the feature
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.
Compare free and owned journeys
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.
Set the release boundary
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.
Compare items consistently
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.
Keep the first catalog small
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.
Design owned and unavailable states
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.
Prototype the player journey
1. Set the platform context
Choose the input and screen behavior for HTML5 games. State the platform limit beside the prototype brief.
Result: An honest scope
2. Map catalog design
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
3. Add the Koin choice
Show the item, exact price, balance, confirm, cancel, pending, success, and delivery without payment-provider screens.
Result: A complete player journey
4. Apply the game product manager lens
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
5. Test return and recovery
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
Generate the HTML5 games prototype
Prompt 1
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.
Prompt 2
Keep the item optional. Show its specific Koin amount, current Koin balance, confirm, cancel, low-balance, success, visible delivery, and reload states.
Game Product Manager test checklist
- The catalog design sequence feels natural for HTML5 games.
- The game product manager can make the intended decision from the playable result.
- The item, Koin price, and balance appear before the player confirms.
- Cancel, too little Koin, pending, success, and reload have different outcomes.
- The page states this boundary: Browser delivery does not prove native store billing or platform approval.
- Ask players what they expect before confirming and what they received afterward. Remove pressure language and unsupported platform claims.
Limits for HTML5 games
- Browser delivery does not prove native store billing or platform approval.
- This guide uses a direct Koin transaction for one optional game item. It does not create a subscription or recurring charge.
- The result is a playable web prototype. Native billing, identity, durable entitlements, security, refunds, and store approval need separate implementation.
- SEELE does not provide payment analytics, tax tools, payout reports, or guaranteed revenue through this flow.
Frequently asked questions
What does catalog design mean here?
Write how to define item identity, value, Koin price, preview, and ownership before checkout. The result is shown as a playable Koin flow.
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. Browser delivery does not prove native store billing or platform approval.
Create the catalog 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