DEV Community

Raf.Goldman
Raf.Goldman

Posted on

Reopening a project after two weeks? I built a tool so I never lose the thread again

The problem

Every developer has ten projects sitting in their Documents folder. Reopen one after two weeks and you ask yourself:

  • What was I working on?
  • What was blocking me?
  • Did I leave a stash somewhere?
  • Is there uncommitted work I forgot about?

Git tells you what changed. It doesn't tell you what you were thinking.

The idea

FlowRecall keeps a tiny context note per project, with three fields:

  1. Goal: what I'm trying to achieve
  2. Blocker: what's in the way
  3. Next action: the very next thing to do

Open the app in the morning and in a few seconds you see which project needs you first, and why.

Smart Git alerts

FlowRecall also watches your repositories and warns you about:

  • a forgotten stash (older than a threshold you choose)
  • uncommitted WIP that has been sitting there too long
  • a possibly outdated note (the code moved on, the note didn't)

How it's built

  • Java 21 + Swing
  • SQLite for local storage: no account, no cloud
  • Packaged as a Snap with strict confinement

The packaging was the most surprising part. Shipping a Swing app as a strictly confined Snap (bundled JRE, bundled git, no access to hidden folders) took more time than some features. I might write about that next.

Try it

sudo snap install flowrecall
Enter fullscreen mode Exit fullscreen mode

It's version 1.0, so I'd love your feedback:

  • Does the goal / blocker / next action format make sense to you?
  • What other alerts would be useful?
  • Would you want it on other platforms?

Top comments (0)