Found footage is a story told as leftover media: tapes, clips, files the characters did not shoot for an audience. A phone UI is the modern leftover. Messages, photos, voice notes, and lock-screen debris already look like a documentary nobody agreed to make. Mapping the genre to a phone is not a skin. It is a rule about who the camera thinks it is for.

Found footage maps to a phone UI as fragments with timestamps, not as a movie the player watches. The interface is the camera roll, the thread, and the lock screen the owner left behind.

Spylie uses that map: you work a fictional found phone. Listing: Spylie on the App Store. Goktug Unver and Yusufhan Sokur treat chrome as evidence, not as decoration. Studio: home.

What does found footage require that a cutscene does not?

It requires an in-world reason the media exists. A video call exists because two people called. A burst of photos exists because someone checked a door. A voice note exists because they were walking and could not type. If a clip exists only because the writer needed exposition, it is a cutscene wearing a timestamp.

The player is a later viewer. That is the genre contract. Why the object works: why found-phone mystery games work. How Spylie applies it: how Spylie turns a phone into a case.

How do film grammar beats become UI beats?

Dead ends are the static. They keep the archive from feeling curated. Why mystery games need dead ends. Clues must still be used, not only collected: clue hoarding versus clue using.

Which apps carry the “camera”?

1. Photos and files for images the owner thought were private.
2. Messages for performed speech.
3. Notes for speech they did not send.
4. Audio for breath and hesitation that text hides. Chat versus audio logs.
5. System debris (alarms, calendar leftovers) for time the owner did not narrate.

Unreliable sources thrive here because leftover media is already incomplete. Unreliable narrators in mobile mystery games. Do not add a documentary host. Immersion is the reread: clues, doubt, payoff.

When should you break the footage rule?

Break it for onboarding only if the first session would otherwise teach nothing. Even then, keep the tutorial short. A long guide breaks the object. Practical play path: Spylie guide. Commute-length sessions also argue against long cinematic inserts: pacing a case across commute sessions.

Never break the rule to instruct a real-world search of someone else’s device. This is fiction. A lock-screen notification that exists because the character left it is footage. A toast that exists because the designer needed a tutorial is not. Ethics: looking through a fictional phone without creep.

What mistakes turn the UI into a movie player?

• Autoplay video as the main story: the player becomes a spectator.
• Perfect folders: real phones are messy. A tidy evidence locker feels authored.
• Omniscient captions: “Clue found” stickers kill found-footage grammar.
• Feature creep mini-games that are not media: say no. Feature creep.

Quiet chrome helps the object stay believable. Quieter interfaces. Index: Journal.

Frequently asked questions

Is a found-phone game the same as a found-footage film?

No. Film is watched in order. A phone is browsed. The player chooses the next clip. That choice is the play.

Do I need shaky-cam filters?

No. Filters are decoration. The grammar is leftover media with a reason to exist.

Can a polished UI still feel like found footage?

Yes if the content is messy and the system does not narrate every tap. Polish can sit in type and latency. It should not sit in a host voice.

Why not tell the story in one long video?

Because then you shipped a player, not a case. Investigation needs source, time, and a theory the player revises.

Is Spylie a real-camera product?

No. It is a narrative simulation. Do not use it as a model for touching a real phone that is not yours.