One review surface
Recordings, transcripts, notes, bookmarks and OCR markers share a timeline.
Desktop product
_Blackbox
Recorded work becomes a searchable history, with timestamps that take you back to the moment behind an answer.
- My contribution
- Product design · React/Tauri · capture and retrieval workflows
- Timeframe
- Active private development
- Status
- Ongoing
THE WORK IN ONE LINE
Recorded work becomes searchable evidence; timestamped answers return to the source moment. In development.
01 / The problem
The answer was somewhere in a recording.
A long recording preserves what happened, but finding one decision still means scrubbing through it. Notes, transcripts and screenshots can become another set of disconnected files.
02 / What I built
I designed a connected capture, library and review experience. Transcript, OCR, note and decision markers retain their times; a search result or cited answer can seek back to the relevant source.
_BLACKBOX / SAMPLE SESSION
Find the moment behind the answer.
Design review · 30:00
The mobile menu is hard to find.
04:1200:0015:0030:00
WHAT CHANGED IN THE REVIEW?
The team made the Menu control visible. The review ended with a decision to keep it.
Fictional session with working timestamp links. _Blackbox is a private product in development; long-recording acceptance remains open.
04 / Result & scope
What changed. What comes next.
Current product source, review-timeline implementation and retained development checkpoint.
Answers with timestamps
Search and source-linked answers point back to the original moment.
Development checkpoint
Important long-recording acceptance remains open; this is an implemented private product in development.
Design around the moment
Library, Capture, Session Detail and Search share a clear path from recording to a specific piece of evidence. The public example makes the timestamp links work.
Connect storage and retrieval
The desktop interface, Rust capture workflows and retained-session services connect local interaction with searchable history. Recovery and health are part of the product surface.
What still needs proving
Native motion fidelity and source-loss recovery remain under validation in the latest checkpoint. I treat long-recording acceptance as separate from a passing interface or build check.