CutSeen

Preserving every viewing journey

A TV and film tracker that keeps every FirstSeen and ReSeen as its own history instead of flattening them into one progress bar.

Relationship
Studio development
Stage
In development

Availability

As of October 6, 2026: a test build exists. CutSeen is not available in an app store.

The problem

A first watch and each later rewatch need distinct progress and history, without one viewing overwriting another.

The contribution

JodyInk defined the viewing-history model and built the mobile product around continuity, recovery, and legible state.

Decisions that shaped the work

  1. Model FirstSeen and every ReSeen as independent runs rather than a single mutable record.

  2. Preview imported changes and preserve recovery paths instead of treating import as an irreversible shortcut.

What was implemented

  1. Independent viewing runs, append-only history, and progress that retains its original context.

  2. Import preview, retry, and rollback behavior designed around recoverable data changes.

  1. Product design · Data modeling · Media softwareWhy a rewatch deserves its own historyA product-modeling decision in CutSeen: repeated viewings become separate runs, so chronology, notes, and uncertainty are preserved instead of flattened.