PWA · Technical Producer · IAP Catalog Design guide
Use a browser-playable PWA context to produce a state-machine and implementation handoff. Own transaction IDs, duplicate-submit guards, delivery ownership, reconciliation, persistence, and rollback evidence; treat the result as a workflow prototype, not proof that native billing is connected.
Create this game flow
Focused keyword and player case
Prototype a three-item catalog with one cosmetic, one bounded consumable, and one optional content pack. The technical producer reviews item scope, price ladder, free baseline, and catalog overlap and delivers a state-machine and implementation handoff. Acceptance means every transition has an owner, an observable receipt, an idempotent retry rule, and a safe recovery path after interruption.
Use the focused IAP Catalog Design 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.
Turn the purchase into named states and transitions. Separate the player-facing prototype from identity, persistence, native billing, security, and refund work.
Design for the input, layout, interruption, and return behavior players expect from PWA games.
PWA packaging does not create native platform IAP entitlements.
Show one non-required item, its preview, specific Koin amount, current Koin balance, and ownership rule in a layout suited to PWA games.
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.
Make a player cancellation, too little Koin, pending, interrupted delivery, and reload visually distinct, with a safe next action.
Map preview, confirmation, a cancelled choice, a Koin shortage, pending, success, delivery, owned, and reload. Give every failure a safe next action. Use the prototype to resolve player-facing questions before creating platform integration tasks.
For a technical producer, this catalog design prototype should make every player action and result shown in the game easy to evaluate. Write how to define item identity, value, Koin price, preview, and ownership before checkout. Map preview, confirmation, a cancelled choice, an insufficient balance, pending, success, delivery, owned, and reload. Give every failure a safe next action. Try the flow in a regular tab and an installed presentation. Navigation, focus, and recovery should remain understandable even when browser controls are reduced or the app resumes from suspension.
An unavailable connection must not look like a completed purchase. Explain when the action cannot continue, preserve the game state, and provide a safe retry after connectivity returns.
PWA installation does not create platform IAP ownership. Durable identity, cross-device state, refunds, billing integration, and app-store policy remain outside the browser prototype.
Separate preview, confirmation, pending, success, delivery, owned, insufficient Koin, cancel, interrupted, and reopened states. Assign later production work for identity, persistence, native billing, security, refunds, policy, and monitoring.
Repeated confirmation, a slow response, navigation during delivery, and reopening must resolve to one result. Record which state is authoritative and how the player can safely retry without another grant or Koin deduction.
Capture the visible behavior first, then create implementation tasks with expected examples for each transition and platform boundary. Do not translate a working browser interaction into an unsupported claim that backend commerce is complete.
Use the same fields for every offer: preview, benefit, ownership or duration, full price in Koin, and owned state. Consistent cards make differences easier to understand. Test that behavior using PWA games. PWA packaging does not create native platform IAP entitlements.
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 PWA games. PWA packaging does not create native platform IAP entitlements.
A catalog also needs sold, owned, equipped, and unavailable presentations. Do not leave a purchased item looking buyable after reload. Test that behavior using PWA games. PWA packaging does not create native platform IAP entitlements.
Choose the input and screen behavior for PWA games. State the platform limit beside the prototype brief.
Result: An honest scope
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
Show the item, exact price, balance, confirm, cancel, pending, success, and delivery without payment-provider screens.
Result: A complete player journey
Map preview, confirmation, a player cancellation, too little Koin, pending, success, delivery, owned, and reload. Give every failure a safe next action.
Result: Technical producer focus
Interrupt delivery, repeat the input, and reload. The prototype should never grant twice or leave the player in an unexplained state. Repeat the test after interruption and reload.
Result: A stable prototype
Create installable web presentation and offline-aware states for a technical producer. 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 technical producer must be able to name every state, owner, failure path, and expected check. Do not add subscriptions, payment-provider UI, revenue analytics, or native platform claims. State this boundary: PWA packaging does not create native platform IAP entitlements.
Keep the item optional. Show its full price in Koin, visible Koin balance, confirm, cancel, low-balance, success, visible delivery, and reload states.
Own transaction IDs, duplicate-submit guards, delivery ownership, reconciliation, persistence, and rollback evidence. Coordinate adjacent work, but keep the page's acceptance artifact specific to this role.
Deliver a state-machine and implementation handoff that records item scope, price ladder, free baseline, and catalog overlap, 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