SEELE AIStart creating

Game Product Manager guide · Roblox Experience Designers · Koin purchase UX

Game Product Manager: Roblox Game IAP - Review Koin Purchase Recovery

Use an AI-generated, browser-playable Roblox experience designers prototype to test purchase recovery. Write how to handle reloads, interrupted delivery, duplicate clicks, and insufficient Koin without double granting. This gives the game product manager a concrete decision before native implementation.

Create this game flow
Game Product Manager: Roblox Game IAP - Review Koin Purchase Recovery visual reference
Visual reference only. Your generated game follows the prompt you choose.

Game Product Manager decisions for Roblox experience designers

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.

Platform context

Design for the input, layout, interruption, and return behavior players expect from Roblox experience designers.

Prototype boundary

This page does not create Roblox developer products or process Robux.

Purchase Recovery in practice

Starting state

Show one voluntary game item, its preview, specific Koin amount, visible Koin balance, and ownership rule in a layout suited to Roblox experience designers.

Main task

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.

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.

Game Product Manager deep dive on purchase recovery

Focus on item value and UX

For a game product manager, this purchase recovery prototype should make every player action and result shown in the game 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 the concept to test where an offer belongs, what the player understands, and how delivery appears in play. Do not label simulated Koin as Robux or a Roblox developer product.

Respect experience context

Consider shared sessions, avatar identity, age context, moderation, and platform interface expectations. Avoid fake platform dialogs or claims that an external browser state proves Roblox ownership.

Create a separate Roblox plan

Developer products, marketplace rules, receipts, persistence, refunds, security, and platform review need Roblox-specific implementation. Carry only the tested player promise and state scenarios forward.

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.

Keep pending understandable

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 Roblox experience designers. This page does not create Roblox developer products or process Robux.

Make retry idempotent

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 Roblox experience designers. This page does not create Roblox developer products or process Robux.

Return to a safe game state

Cancellation, not enough Koin, and recoverable errors should preserve progress and offer a clear return or retry action. Test that behavior using Roblox experience designers. This page does not create Roblox developer products or process Robux.

Game Product Manager workflow for the player journey

  1. 1. Set the platform context

    Choose the input and screen behavior for Roblox experience designers. State the platform limit beside the prototype brief.

    Result: An honest scope

  2. 2. Map purchase recovery

    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

  3. 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. 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. 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

Prompt a decision-ready prototype

Prompt 1

Create a concept prototype for item value and UX 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: This page does not create Roblox developer products or process Robux.

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

Platform and implementation limits

Frequently asked questions

What does purchase recovery mean here?

Write how to handle reloads, interrupted delivery, duplicate clicks, and insufficient Koin without double granting. 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. This page does not create Roblox developer products or process Robux.

Review the purchase recovery 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