HTML5 · Technical Producer · IAP Inventory Delivery guide
Use a browser-playable HTML5 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 delivered item that moves from pending to owned exactly once and appears in the correct inventory slot. The technical producer reviews idempotent delivery, quantity, ownership, and visible inventory state 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 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.
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 HTML5 games.
Browser delivery does not prove native store billing or platform approval.
Show one non-required item, its preview, specific Koin amount, current Koin balance, and ownership rule in a layout suited to HTML5 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 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 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. Map preview, confirmation, a player cancellation, not enough Koin, pending, success, delivery, owned, and reload. Give every failure a safe next action. Assume a player may open the game from a link in a new browser with limited prior context. Put item identity, Koin balance, and the return route inside the playable experience.
Try refresh, back navigation, a second tab, and returning after the page was suspended. A browser interaction must not imply native-store ownership or silently repeat a delivery action.
If the game uses a canvas, make focus, keyboard input, scaling, and purchase overlays cooperate. Closing the choice should restore game controls without leaving hidden buttons or trapped focus.
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.
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 HTML5 games. Browser delivery does not prove native store billing or platform approval.
Use owned, equipped, unlocked, or remaining quantity as appropriate. The state should match the promise made on the offer card. Test that behavior using HTML5 games. Browser delivery does not prove native store billing or platform approval.
Reload the prototype and return to inventory. The item should remain visible without subtracting Koin or granting a second copy. Test that behavior using HTML5 games. Browser delivery does not prove native store billing or platform approval.
Choose the input and screen behavior for HTML5 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
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 a shareable browser session for a technical producer. 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 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: Browser delivery does not prove native store billing or platform approval.
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 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