pulling together a small private power-user group to talk context switching, ADHD, bugs, weird edge cases, ideas, all of it. if you spend your day bouncing across apps + tabs and losing the thread sometimes, come hang :) joinrecall.com/community would be great to have you there.

portability is the easy promise. the hard part is preserving provenance, permissions, and enough context that memory stays useful after the agent changes runtimes.

d work, VS Code when the project has history and weird edges. Haven't used Antigravity enough to pretend otherwise. The best one is usually where the repo's context already lives.

Nobody talks about the real cost of a 30-min meeting. It's not 30 minutes. It's the deep work you don't start before it, plus the weird reload after where your brain can't find the thread again. What's your real meeting tax?

What costs you more: the interruption, or clawing your way back in afterward? Mine: a 2-min ping. Tabs still open, but the decision I was mid-way through was gone. 20 min to find the thread. Drop your worst switch-back 👇 (the exact gap JoinRecall chews on)

Finish this: "The moment I completely lost the thread was ______." Mine: pulled into a Slack fire, came back 2 hours later, rewrote a migration I was already halfway through. Wrong half. Yours 👇 (building JoinRecall for exactly this)

You come back from a ping to a pile of duplicate, half-labeled threads. Which cleanup should JoinRecall nail first? 🔵 Better project detection 🔵 Merge + dedupe 🔵 Cleaner threads 🔵 Fewer noisy nudges One tap 👇 it decides my week

5/ Big thx to Noah, William, @AppSumo, and the partner team. They’ve been genuinely receptive and helpful through the whole process. If you’re cooking something early and unsure how to launch it, I’d seriously look at Radar. Happy to share our distribution map or answer early GTM questions in DMs.

4/ The biggest lesson: Don’t scale traffic into weak retention. We already mapped the next 6 months of distribution, but now the focus is feedback, activation, retention, and improving Recall’s core reasoning.

3/ Distribution was completely manual: X Reddit LinkedIn 1:1 outreach inside our network No cold email. No outreach automation. The first sales came from conversations, not scale.

2/ Before launch, we ran 64 async/live conversations with founders, operators, GTM people and devs. We studied real context-switching cases, not “productivity” in general. That shaped the positioning, first features, and gave us early testers.

1/ It started when I saw @noahkagan post about AppSumo Radar on LinkedIn. I reached out and pitched Recall while it was still basically an idea and a landing page. Noah was super receptive and encouraged us to apply. We spent the next 2 weeks building the first usable MVP.

The ADHD tax nobody bills you for: the reload after an interruption. The tabs survive. The "what was I about to do" does not. How do you get it back — a note, raw memory, or just eat the 20 min? Building JoinRecall (local-first Mac) around exactly this 👇

lol

Looking for 15 Mac users with context switching pain. Genuinely messy workflows. The messier the better. Building JoinRecall to bring back your exact work state after an interruption, and the hard part is nailing it on chaos, not demos. Reply "in"