PWA · Product Manager · IAP Inventory Delivery guide
Use a browser-playable PWA 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 a delivered item that moves from pending to owned exactly once and appears in the correct inventory slot. The product manager reviews idempotent delivery, quantity, ownership, and visible inventory state 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 Inventory Delivery 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 PWA games.
PWA packaging does not create native platform IAP entitlements.
Show one voluntary game item, its preview, full price in Koin, visible Koin balance, and ownership rule in a layout suited to PWA games.
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.
Make cancellation, not enough Koin, 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 inventory delivery prototype should make every player action and player-visible outcome 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. 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.
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.
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 PWA games. PWA packaging does not create native platform IAP entitlements.
Use owned, equipped, unlocked, or remaining quantity as appropriate. The state should match the promise made on the offer card. Test that behavior using PWA games. PWA packaging does not create native platform IAP entitlements.
Reload the prototype and return to inventory. The item should remain visible without subtracting Koin or granting a second copy. 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 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
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 installable web presentation and offline-aware 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: PWA packaging does not create native platform IAP entitlements.
Keep the item optional. Show its specific Koin amount, current 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 idempotent delivery, quantity, ownership, and visible inventory state, 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