⚡ Offline Windows tray app for developers

Turn your development day into a report people can actually understand.

yester<dev> captures the work behind the work, implementation progress, technical decisions, experiments, screenshots, recordings, code, links, and notes, without breaking your focus. Then it turns those moments into a clear, publishable report.

Works offline · Your data is yours · No account required

yester<dev>
The problem

Valuable development context disappears between the work and the report.

You implement features, compare approaches, test ideas, review changes, read logs, collect screenshots, and make decisions all day long.

By the time someone needs the story, the context is scattered across browser tabs, chat messages, screenshots, commits, and memory.

The result: the work is difficult to explain, repeat, hand off, or turn into useful documentation.

📸 screenshot_final_v2.png 💬 "wait, why did we choose this?" 🔗 14 open browser tabs 📝 untitled.txt 🧠 "I changed that around 11, right?" 📋 clipboard history, lost ⏰ report due in 20 min
How it works

yester<dev> records the path, not just the result.

A tray-first workflow with global hotkeys. Every capture is timestamped, tagged, linked to the source app, and appended to your session log, automatically.

1

Start a session

Name the activity you're working on. yester<dev> keeps a folder and timeline for it.

2

Capture with hotkeys

Screenshots and screen recordings ⌃⇧S, notes ⌃⇧N, code ⌃⇧D, and links ⌃⇧L.

3

Tag while it's fresh

Add quick notes and tags in seconds, while the context still exists.

4

Organize to publish

Select and order captures across Sessions to build one clear publishing list.

5

Preview & publish

Review the report in your browser, then publish to HTML, Confluence, Notion, or Slack.

Features

Built for one job: making development work visible.

⚡

Capture without context switching

Global hotkeys capture the current state of work without opening a heavy tool or interrupting your flow.

🕒

A timeline builds itself

Every capture lands in the session log with a timestamp, source app, tags, notes, and media references.

🏷️

Searchable by design

Tags turn scattered capture moments into a navigable work trail. Create a missing tag right from the capture dialog.

🧾

Context stays together

Screenshots, recordings, snippets, links, and notes live in one report, with what happened and the path that led there.

🚀

Publish where teams work

Export clean HTML, push directly to Confluence Cloud or Notion, or send the report into a Slack thread.

🔒

Private thinking stays private

Session post-its stay local and are deliberately excluded from every exported report.

Screenshots and video

Capture the screen. Then show what matters.

Draw, point, and write directly on screenshots and video frames. Highlight the exact interface element, value, behavior, or change that matters. For video, pin each annotation to the precise moment where it belongs. The explanation stays attached to the thing being explained.

🖊️

Annotate screenshots

Circle details, draw arrows, underline content, and place explanatory text directly on the image.

🔤

Explain video visually

Draw and write over video frames so changes, behavior, and important details are immediately understandable.

⏱️

Pin context to time

Choose exactly when each video annotation appears and disappears, so the explanation arrives at the relevant moment.

Use cases

One workflow, every kind of development story.

Development reports

Turn a work session into a structured update: what was done, what changed, what was learned, and what remains open.

Feature implementation

Capture milestones, interface changes, implementation decisions, tradeoffs, and progress as the feature takes shape.

Technical decisions

Preserve the alternatives, reasoning, visual references, and code context behind an important decision.

Client and stakeholder updates

Share clear reports that show progress, decisions, visible changes, and next steps.

Technical handoffs

Package the context another developer needs to continue the work, without a long meeting.

Bug investigations

Keep reproduction steps, screenshots, recordings, code findings, and hypotheses together in one timeline.

Integrations

Your report, where your team already works.

</> Standalone HTML
C Confluence Cloud
N Notion
S Slack
Offline and yours

Your data is yours.

🖥️ Works offline

Capture, organize, annotate, and create HTML reports entirely on your computer. No account or connection is required for the core workflow.

🔐 Files you control

Sessions are ordinary Markdown and media files stored in a folder you choose. There is no required service account, proprietary cloud, or hidden upload.

👀 You decide what leaves

Nothing is sent to Confluence, Notion, or Slack until you choose a destination, preview the report, and publish it. Private post-its are never included.

Stop reconstructing your day from memory.

yester<dev> turns development work into documentation while the context is still fresh. It works offline, and your data stays yours. Free during the beta.