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 · Desktop Web Games · Koin purchase UX
Game Product Manager Guide to Koin Purchase Confirmation for Desktop Web Games
Use a playable browser prototype to work through purchase confirmation for desktop web games. The goal is to make the player journey concrete before the team commits to native commerce implementation.
Create this game flow
Define the desktop web games scope
Platform context
Design for the input, layout, interruption, and return behavior players expect from desktop web games.
Prototype boundary
Desktop browser purchases remain Koin flows inside the supported experience.
Purchase Confirmation in practice
Starting state
Show one item the player may decline, its preview, precise Koin price, balance before spending, and ownership rule in a layout suited to desktop web games.
Main task
Write how to show the exact item, Koin amount, balance impact, and explicit confirm/cancel actions. Keep each change visible to the player rather than hiding it in technical state.
Recovery
Make cancelling the action, an insufficient balance, 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 purchase confirmation details
Support keyboard and pointer
For a game product manager, this purchase confirmation prototype should make every player action and player-visible outcome easy to evaluate. Write how to show the exact item, Koin amount, balance impact, and explicit confirm/cancel actions. Define the player need, item scope, ownership rule, Koin price, and free path. Check age context, accessibility, rights, and platform expectations. Check tab order, focus indicators, mouse targets, escape behavior, and the return to game controls. Confirmation must never borrow an input that also performs a high-frequency gameplay action.
Plan for wide layouts
Keep the item, Koin amount, balance effect, and actions together on common desktop widths. Avoid pushing cancelling the action off screen simply because the game canvas occupies a large area.
Test window changes
Resize, move between displays, zoom, refresh, and restore a background tab. The interaction should preserve the selected item and resolve pending or delivered states without another grant.
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.
Repeat the complete choice
The confirmation should repeat the selected item, exact Koin amount, Koin balance now, remaining balance, and ownership rule without introducing a different offer. Test that behavior using desktop web games. Desktop browser purchases remain Koin flows inside the supported experience.
Separate confirm from cancel
Use distinct actions with clear labels and enough spacing for the target input method. Returning to the game should never spend Koin. Test that behavior using desktop web games. Desktop browser purchases remain Koin flows inside the supported experience.
Prevent repeated confirmation
After confirmation, show a pending state and disable repeated input until the result is known. A slow response should not create duplicate grants. Test that behavior using desktop web games. Desktop browser purchases remain Koin flows inside the supported experience.
Prototype the player journey
1. Set the platform context
Choose the input and screen behavior for desktop web games. State the platform limit beside the prototype brief.
Result: An honest scope
2. Map purchase confirmation
Write how to show the exact item, Koin amount, balance impact, and explicit confirm/cancel actions. Describe the player action and visible response at each point.
Result: A clear purchase confirmation 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 desktop web games prototype
Prompt 1
Create keyboard-and-mouse browser play for a game product manager. Focus the IAP prototype on show the exact item, Koin amount, balance impact, and explicit confirm/cancel actions. 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: Desktop browser purchases remain Koin flows inside the supported experience.
Prompt 2
Keep the item optional. Show its precise Koin price, balance before spending, confirm, cancel, low-balance, success, visible delivery, and reload states.
Game Product Manager test checklist
- The purchase confirmation sequence feels natural for desktop web games.
- The game product manager can make the intended decision from the playable result.
- The item, Koin price, and balance appear ahead of confirmation.
- Cancel, an insufficient balance, pending, success, and reload have different outcomes.
- The page states this boundary: Desktop browser purchases remain Koin flows inside the supported experience.
- Ask players what they expect before confirming and what they received afterward. Remove pressure language and unsupported platform claims.
Limits for desktop web games
- Desktop browser purchases remain Koin flows inside the supported experience.
- 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 browser 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 purchase confirmation mean here?
Write how to show the exact item, Koin amount, balance impact, and explicit confirm/cancel actions. 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. Desktop browser purchases remain Koin flows inside the supported experience.
Create the purchase confirmation 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