fikka

Your AI writes the app. fikka keeps your data safe from it.

Ask for a grocery list app and get one for the web and your Android phone, both on one offline-first database. AI-written apps will have bugs, so the platform owns the schema, and nothing is deleted for good until you empty the bin.

Read the docs Sign in

Groceries build 3
  • Oat milk
  • Rye bread
  • Lingonberry jam
  • Coffee beans
  • Cardamom

Delete a few items, or ship a build that wipes the list. Every row goes to the bin first, and you can put it back.

From a chat to your phone

  1. Ask

    Tell Claude, or any agent that speaks MCP: “make me a grocery list app.” It proposes the tables.

  2. Approve

    You approve the schema on your platform page. Agents can only propose changes, and only ones that add to what's there.

  3. Push

    The agent pushes the code with git. Every push builds a web version and an Android app.

  4. Use it

    Install it and keep adding items on the train with no signal. It syncs when you're back, and the web app shows the same list.

Made for apps that will have bugs

Every delete goes to the bin
From every app, every build. You see which build deleted what, restore it, and you're the only one who can empty the bin. Apps and agents can't.
You own the schema
Apps can read and write rows, never change tables. Schema changes are additive, so the build already on your phone keeps working after the next one ships.
One database for every client
The web app and the phone app share one synced database. Each works offline and catches up when it reconnects.
Yours to take
The code is plain git and the data is SQLite. Hosting is a convenience, and fikka is built so you can run both yourself.

fikka is early. It runs today for one person: the one building it. The blog follows along as that changes.