SYSTEMS · Kika

Why I Built Lapapi — and Why It's Nothing Like the AI Tools You're Using

I didn't set out to build another AI assistant. In fact, if Lapapi feels like one, I've failed. Here's the honest origin story.

I didn't set out to build another AI assistant. In fact, if Lapapi feels like one, I've failed.

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

The 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.

What I Actually Needed

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

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

The Philosophy: 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:

What Lapapi Is NOT (And Why That Matters)

I keep a literal rejection list. Every time someone suggests a feature, I check it against this:

What It Actually Does

Lapapi has 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. When you click a project, you don't see a timeline. You see a briefing.

2. Tools, Not Replacement

Lapapi connects to what you already use:

It doesn't try to be any of these. It's the switchboard.

3. Anonymous by Default

No account. No onboarding flow. No "connect your Google." Open the app, you're in. The server runs local-only by default. Your data stays on your machine.

This isn't a privacy pitch — it's a friction pitch. Every login screen, every OAuth redirect, every "verify your email" is a reason to not open the tool when you need it.

The Design: "Boring in the Best Way"

I have a sticky note on my monitor that says:

"Keep this app boring in the best way. It should not feel like another productivity dashboard. It should feel like a calm private shelf of useful tools."

The UI follows my own taste: Apple-quality minimalism, Raycast-level polish, glassmorphism where it helps, keyboard-first everything. No cards. No dashboards. No "AI copilot" sidebars taking up 30% of the screen.

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

How It's Different From Everything Else

The Real Difference

Most AI tools are asking: "How can AI do more for the user?"

Lapapi asks: "How can the user do more without the AI getting in the way?"

That's a subtle but massive difference. It means:

Why I Removed Claude

Last week I made a decision that surprised even me: I removed all Claude integration from Lapapi.

Not because Claude is bad. It's excellent. But my stack was getting bloated. I was tracking Anthropic, OpenAI, Google, and 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: Pieces, Ollama, Apple's local capabilities, and Codex project context. Build passed. App relaunched. It felt like removing clutter from a desk.

That's the philosophy: ruthless focus. One core problem. One calm solution.

The One-Sentence Pitch

If I only had one line:

"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.

From the same desk

Lapapi is the philosophy; the apps are the practice. The same calm, local-first instinct runs through every small macOS tool I ship.

See the apps