Mobile Web · Product Manager · IAP Purchase Recovery guide
Use a browser-playable Mobile Web 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 an interrupted 60 Koin unlock reconciled after reload without charging or granting twice. The product manager reviews pending state, transaction reconciliation, restore, and support evidence 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 Purchase Recovery 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 mobile web games.
Mobile web is not the same as an App Store or Google Play binary.
Show one item that remains optional, its preview, clearly stated Koin cost, available Koin balance, and ownership rule in a layout suited to mobile web games.
Write how to handle reloads, interrupted delivery, duplicate clicks, and insufficient Koin without double granting. Keep each change visible to the player rather than hiding it in technical state.
Make a cancelled choice, a Koin shortage, 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 purchase recovery prototype should make every player action and clearly displayed outcome easy to evaluate. Write how to handle reloads, interrupted delivery, duplicate clicks, and insufficient Koin without double granting. Define the player need, item scope, ownership rule, Koin price, and free path. Check age context, accessibility, rights, and platform expectations. Use comfortably separated confirm and cancel controls, readable Koin amounts, and a layout that survives portrait, landscape, browser chrome, and an on-screen keyboard without hiding the item.
Simulate locking the phone, changing tabs, receiving a call, and returning with a slow connection. The player should see one understandable result and retain a safe route back to play.
A mobile browser prototype is not an App Store or Google Play binary. Native billing APIs, device identity, refunds, entitlements, and submission need separate implementation and review.
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.
If delivery is interrupted, explain whether the result is pending, safe to retry, or already complete. Do not show both failure and success. Test that behavior using mobile web games. Mobile web is not the same as an App Store or Google Play binary.
Repeated clicks and reloads should resolve to one purchase result. The player must never receive duplicate items or lose Koin twice. Test that behavior using mobile web games. Mobile web is not the same as an App Store or Google Play binary.
Cancellation, too little Koin, and recoverable errors should preserve progress and offer a clear return or retry action. Test that behavior using mobile web games. Mobile web is not the same as an App Store or Google Play binary.
Choose the input and screen behavior for mobile web games. State the platform limit beside the prototype brief.
Result: An honest scope
Write how to handle reloads, interrupted delivery, duplicate clicks, and insufficient Koin without double granting. Describe the player action and visible response at each point.
Result: A clear purchase recovery 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 touch-first play in a mobile browser for a game product manager. Focus the IAP prototype on handle reloads, interrupted delivery, duplicate clicks, and insufficient Koin without double granting. 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: Mobile web is not the same as an App Store or Google Play binary.
Keep the item optional. Show its clearly stated Koin cost, available 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 pending state, transaction reconciliation, restore, and support evidence, 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