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 · Classroom Game Labs · Koin purchase UX
Game Product Manager Guide to Koin Inventory Delivery for Classroom Game Labs
Use a browser-based playable build to work through inventory delivery for classroom game labs. The goal is to make the player journey concrete before the team commits to native commerce implementation.
Create this game flow
Define the classroom game labs scope
Platform context
Design for the input, layout, interruption, and return behavior players expect from classroom game labs.
Prototype boundary
Use simulated Koin values and instructor review; do not collect student payment data.
Inventory Delivery in practice
Starting state
Show one item that remains optional, its preview, clearly stated Koin cost, available Koin balance, and ownership rule in a layout suited to classroom game labs.
Main task
Write how to connect successful purchase to a visible owned or quantity state. Keep each change visible to the player rather than hiding it in technical state.
Recovery
Make a cancelled choice, a Koin shortage, 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 inventory delivery details
Use simulated value only
For a game product manager, this inventory delivery prototype should make every player action and result the player can inspect easy to evaluate. Write how to connect successful purchase to a visible owned or quantity state. Define the player need, item scope, ownership rule, Koin price, and free path. Check age context, accessibility, rights, and platform expectations. Treat Koin as a classroom game variable and do not request payment details, account credentials, or personal student information. The exercise is about interface states and responsible design.
Make the learning objective visible
Ask students to explain the item promise, free path, cancel behavior, failure recovery, and production boundary. Grade reasoning and playtest evidence rather than purchase completion.
Plan instructor-led testing
Run the prototype on shared devices with accessible controls and privacy-safe displays. Native billing, identity, durable storage, refunds, platform approval, and real transactions remain outside the lab.
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.
Connect success to the item
A success message is not delivery. Place the cosmetic, consumable, unlock, or upgrade in the screen where the player expects to use it. Test that behavior using classroom game labs. Use simulated Koin values and instructor review; do not collect student payment data.
Show ownership and quantity
Use owned, equipped, unlocked, or remaining quantity as appropriate. The state should match the promise made on the offer card. Test that behavior using classroom game labs. Use simulated Koin values and instructor review; do not collect student payment data.
Verify delivery after reload
Reload the prototype and return to inventory. The item should remain visible without subtracting Koin or granting a second copy. Test that behavior using classroom game labs. Use simulated Koin values and instructor review; do not collect student payment data.
Prototype the player journey
1. Set the platform context
Choose the input and screen behavior for classroom game labs. State the platform limit beside the prototype brief.
Result: An honest scope
2. Map inventory delivery
Write how to connect successful purchase to a visible owned or quantity state. Describe the player action and visible response at each point.
Result: A clear inventory delivery 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 classroom game labs prototype
Prompt 1
Create a non-production demonstration of purchase states for a game product manager. Focus the IAP prototype on connect successful purchase to a visible owned or quantity state. 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: Use simulated Koin values and instructor review; do not collect student payment data.
Prompt 2
Keep the item optional. Show its clearly stated Koin cost, available Koin balance, confirm, cancel, low-balance, success, visible delivery, and reload states.
Game Product Manager test checklist
- The inventory delivery sequence feels natural for classroom game labs.
- The game product manager can make the intended decision from the playable result.
- The item, Koin price, and balance appear prior to confirming.
- Cancel, a Koin shortage, pending, success, and reload have different outcomes.
- The page states this boundary: Use simulated Koin values and instructor review; do not collect student payment data.
- Ask players what they expect before confirming and what they received afterward. Remove pressure language and unsupported platform claims.
Limits for classroom game labs
- Use simulated Koin values and instructor review; do not collect student payment data.
- 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 browser-based playable build. 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 inventory delivery mean here?
Write how to connect successful purchase to a visible owned or quantity state. 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. Use simulated Koin values and instructor review; do not collect student payment data.
Create the inventory delivery 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