Why I Built Lapapi

Here's the honest origin story — and why I think most productivity tools are solving the wrong problem.

Context Death

I build a lot of things. SwiftUI apps. Shopify stores. AI agents. Design systems. And I jump between them constantly.

The problem isn't that I forget what I was doing. It's that the context dies.

You know the feeling: you return to a project after two weeks and nothing makes sense. The build was failing for a reason you never wrote down. A file you were "just about to refactor" sits untouched. Your last commit message says "wip" and you have no idea what work-in-progress meant.

I tried Notion. I tried Obsidian. I tried project management tools, todo apps, time trackers. They all made me feel like I was managing a second job just to track the first one.

I don't need a productivity dashboard. I need a memory system that doesn't judge me.

The Actual Requirements

I sketched out what I wanted on a bad day, staring at five open projects and zero motivation. The list was short:

• No login walls. I should open the app and be inside my workspace immediately.
• No noise. No notifications, no gamification, no streaks, no "you're 73% productive today."
• Project continuity. Not project management. I want to re-enter a project and know exactly where I left off — not plan the next 6 months of it.
• My tools, my way. ChatGPT for strategy, Codex for building, Ollama for local tasks, Pieces for memory. I needed a hub that connects them, not replaces them.
• Mac-native. Not a web app in a wrapper. Something that feels like it grew out of macOS.

That's it. No Gantt charts. No kanban boards. No AI chatbot asking me how my day is.

Calm Operational Continuity

I wrote this down early and stuck it on my monitor:

"Help users safely re-enter projects after time away. Focus on continuity, intent, and recovery state — not activity tracking or analytics."

That's the single sentence that drives every design decision in Lapapi.

A friend put it even better during a design review: "You're no longer solving 'how do I show automation info?' You're solving 'how do humans comfortably trust autonomous systems?'"

That reframing changed everything. The best interfaces for this feel:

• Quiet
• Transparent
• Emotionally stable
• Low-pressure
• Highly intentional

Three Simple Ideas

1. Your Projects, Alive

Projects aren't folders. They're living context — last files touched, recent commits, active builds, open errors, and the 2-3 things you were actually trying to solve.

2. Tools, Not Replacement

Lapapi connects to what you already use — Pieces OS, Ollama, Codex, GitHub, Eagle. It's the switchboard, not the replacement.

3. Anonymous by Default

No account. No onboarding flow. No "connect your Google." Open the app, you're in. This isn't a privacy pitch — it's a friction pitch.

"Boring in the Best Way"

When I refactored the home dashboard last week, I didn't add features. I removed them. Reduced visual noise. Tightened spacing. Made it actually calm to look at.

Why I Removed Claude

Last week I removed all Claude integration from Lapapi. My stack was getting bloated — Anthropic, OpenAI, Google, local models in the same UI. The app felt like a model marketplace, not a workspace.

Now Lapapi only tracks what matters to my workflow. Build passed. App relaunched. It felt like removing clutter from a desk.

Ruthless focus. One core problem. One calm solution.

One Sentence

"Lapapi is a calm private shelf that remembers where you left off, so you can pick up any project without starting from zero."

Not an AI. Not a dashboard. Not a manager.

A memory system for people who build too many things to keep in their head.