Updated
The players have worked through the physical evidence and are ready to give their final answer. If the response drops at that moment, the companion should not turn uncertainty into a lost result or an accidental second attempt. The ending deserves as much product design as the opening chapter.
Curiosive can build web companions for physical narrative-game publishers serving Sweden, Norway, Denmark and Finland. The scope can connect kit access, chaptered media, player progress and a deliberate final-deduction journey. Start with one complete game and the rules for finishing or replaying it.
Choose the moment that turns an active investigation into a completed attempt. An incorrect answer might permit another try, reveal a consequence or end the story; that is the publisher's rule to supply. Keep chapter progress, answer submission and completion as distinguishable states. The interface should tell players what they are committing to before a final action, rather than treating every button like an ordinary next-page link.
Murder in Prague, recorded in Czechia, pairs a Shopify storefront selling a physical detective kit with a Next.js and TypeScript web companion. It presents chaptered video interviews, calls and text messages, then asks the player to identify the killer. Sanity manages game content; Supabase supports accounts and saved progress, and one step continues on a phone. This establishes a physical-game companion delivery. The result-recovery, access and replay rules below are proposed scope, not claims about its historical tests or mechanisms.
A player can lose the response after the server has already recorded an answer. Give that action an identifiable attempt and an agreed way to discover its current state. Reopening the game should not automatically label it incorrect or submit another answer. Define what remains visible while the result is unresolved and how the original attempt is reconciled once the service is available. A retry of that request must be distinguishable from a new play attempt. The implementation depends on the actual game-state and backend contract.
Decide which progress or permissions make the ending available. A saved ending URL should follow that rule when opened early, after signing out or under a different account. Separate an intentional replay from recovery of an interrupted session. If a replay resets progress, tell the player what changes and whether the earlier completion remains available. Do not assume multiplayer, shared household accounts or a branching story engine unless those are part of the commission.
Use the publisher's actual case files, chapter references and approved media to review the handoff into the companion. Identify the kit or edition the player owns without assuming that a storefront purchase automatically grants every possible account access. A phone-only step needs a clear place in the intended device journey. The first release can preserve an existing store while adding the agreed companion; payment and fulfilment changes are separate requirements.
Choose the game and interface languages needed in Sweden, Norway, Denmark and Finland, with the creative team reviewing clue wording, media and the final-answer interaction. A translated label cannot establish that a deduction still works as intended. Decide whether players select from supplied answers or enter text, and how the publisher approves acceptable responses. Keep those creative decisions explicit rather than inferring a new answer-validation policy from another game's implementation.
Use one fictional player attempt and the intended final screen to make the completion, recovery and replay decisions concrete.
Physical-game companion discovery worksheet
Proposed acceptance: test approved correct and incorrect deductions against the publisher’s result rules. Lose the response after one submission is recorded, then reopen and recover that attempt’s outcome. Separately test a request that was not recorded. Checking or retrying the same submission must not silently consume another attempt. Where replay is included, its deliberate action applies the defined reset and previous-result policy. An early ending link or another account follows the agreed access rule. These are proposed checks, not claims about Murder in Prague’s historical completion or replay implementation.
Share a representative kit, approved media and the final-deduction rules. Curiosive can deliver the agreed web companion remotely from Ankara, Türkiye, with the creative and product owners reviewing a complete play-through and its interrupted ending.
We can assess the store, access handoff and companion separately. Murder in Prague uses Shopify, but that does not establish compatibility with every commerce setup or require your product to replace its current shop.
No. The publisher defines the attempt policy. The product should make the consequence understandable and apply it consistently to a normal submission, retry and return after interruption.
That can be a scoped rule. Decide whether a replay creates another attempt, resets selected progress or replaces the earlier record, then make the chosen action explicit before it happens.
That can be assessed as part of the device journey. Define the supported screens, account or session handoff and progress that must remain recognisable. A web companion does not imply an offline or native mobile application.
Your creative team supplies the approved clues, media, story outcomes and answer rules. The development scope implements those decisions and makes them reviewable; it does not infer the solution or invent a branching narrative.
A short note about the product, the timeline and who it is for is enough to start. You will hear back from the engineer who would do the work, not a sales team.
Ankara / Türkiye · Working across European and US time zones