Pacing a Case Across Commute Sessions
Pacing a case across commute sessions means the story can start, pause, and resume in the gaps of a day. A session might be eight to fifteen minutes. The player needs a unit that is not “watch the next cutscene.” The unit is a doubt they can remember when the doors open. If the only save is a flag deep in a thread, they will rerun the same chats and call it confusion.
A commute-paced case gives the player one doubt they can carry off the train. Save progress in a theory, a pin list, and a next source, not only in an invisible checkpoint.
Spylie is a found-phone case, which already fits pockets. Store: Spylie. Goktug Unver and Yusufhan Sokur design for interruption. Studio: home. Attention context: attention and digital experience.
What is a complete commute unit?
A complete unit has one new doubt, one object the player can point at, and a next door they chose. It does not need a chapter title. Immersion on mobile is this timing problem: clues, doubt, payoff. Payoff can wait for a longer sitting. Doubt should not wait. If the player leaves with nothing to hold, they will hoard screenshots instead of using clues. Clue hoarding versus clue using.
How do you end a session without a fake cliffhanger?
- Prompt a one-line theory in the player’s words, even if only in their head.
- Keep a short pin list, not an archive.
- Leave a next source the player picked, not a forced video.
- Prefer chat over long audio at the session edge. Chat versus audio.
- Allow a dead end to be a clean close. “This album is last year.” Dead ends.
A fake cliffhanger (“unlock the next clue in 20 minutes”) is a live-ops habit, not investigation. Mechanics should still be source, time, theory: investigation mechanics.
What breaks commute pacing?
| Break | Why | Fix |
|---|---|---|
| Unskippable audio walls | Doors open mid-sentence | Short clips, tap to pause |
| A puzzle that needs a table | Thumbs, standing | Keep locks rare |
| No recents | Players lose the last object | Surface last three sources |
| Omniscient narrator recap | Removes deduction | Show the objects again |
Found-footage mapping argues against recap hosts: found footage to phone UI. Unreliable sources should still be catchable after a night away: unreliable narrators. Wrong theories should survive a pause without bricking the save. Let the player be wrong.
How should Spylie players use a short session?
Pick one question. Open two apps. Write one sentence. Stop. The guide: Spylie found-phone guide. The product loop: how Spylie turns a phone into a case. Why the object works in short bursts: why found-phone games work.
Do not treat a commute as practice for opening a real stranger’s phone. Fiction only. Without creep.
What mistakes do studios make when they “add sessions”?
- Chopping a long chapter into three load screens: that is not pacing. That is slicing.
- Daily login cases that ignore the save theory: the player’s head is the save.
- Feature creep maps and combat: different genre. Feature creep.
- Tutorial theater on every cold start: the phone stops feeling found.
Quiet UI helps a session start in one tap. UI patterns that build trust. Index: Journal.
Frequently asked questions
How long should one session be?
Short enough to finish a doubt. Eight to fifteen minutes is a useful target. Some players will sit longer. Do not require it.
Should the game remind me what I believed yesterday?
Remind with objects, not with a host essay. Show the last pins and the last thread. Let the player reconstruct.
What if I only play once a week?
Then reread is the mechanic. Design so old media is easy to find. Do not expire evidence.
Can a commute session include a big twist?
It can include a doubt that will become a twist later. A full rewrite needs time to reread. Save the rewrite for a longer sit when you can.
Is Spylie meant to be played on a real found phone?
No. Spylie is a game about a fictional device. Play the case. Do not copy the premise onto a real person’s hardware.
