
Introducing Bite-Stamped
When was I last at The Moose Cafe?
That question sums up why I built Bite-Stamped, a private journal of the places I go: restaurants, bars, breweries, museums, parks, anything. It runs in the browser, installs on my phone's home Screen, works offline, and keeps all of its data in plain Markdown files on a server I control.
Where it started: Eatlist
For a long time I've used Eatlist on my iPhone to keep track of restaurants: the places I've been, the dishes I ordered, photos of the meals, and the places I still want to try. It's a nice app, and it was the direct inspiration for Bite-Stamped.
Eatlist seems to have been abandoned, though, and it was missing things I wanted. The small one that kept bugging me: I couldn't give my photos a title. A picture of a plate is much more useful a year later if it says what's on it. With no updates coming, those gaps weren't going to close.
In Bite-Stamped, every photo has a title, and a place keeps all its visits with a rating for each one:
The other half: Foursquare and Swarm
I've also been a Foursquare user for a long time, checking in with Swarm. The badges, mayorships and other game parts were never really the point for me. I used it as a memory aid. A check-in history lets me answer questions like "when was I last at The Moose Cafe?" or "what was that Mexican place in Asheville with the avocado tacos?"
Eatlist could also record visits, so I fell into a routine of doing everything twice: check in on Foursquare, then log the same visit in Eatlist. If I was going to build my own version of Eatlist anyway, I could merge those two into one app. So Bite-Stamped has a check-in feature: open the Timeline, and with one tap I can check in to a place right around me.
That also replaced another bit of glue. I'd been using IFTTT to turn my Foursquare check-ins into calendar entries, so my visits showed up next to everything else on my calendar. Bite-Stamped publishes my visits as a private iCal feed instead, which I subscribe to in Apple Calendar (Google Calendar and Outlook work too). One less service in the middle.
Inside the app, the Timeline shows the same history as a month calendar. Each day's dots are colored by the kind of place, and tapping a day lists that day's visits:
Owning my data
Both apps taught me something about data ownership, mostly by its absence.
- Eatlist had no way to export my data at all. Years of meals and photos, stuck in one app.
- Foursquare has a process where you request your data and they send it to you, but it takes a long time and what you get is pretty minimal.
So data ownership became the main goal for Bite-Stamped, not an afterthought:
- Plain Markdown files. I've used Obsidian for a while and really like its model: your notes are just Markdown files in a folder. Bite-Stamped does the same. Every place is a Markdown file with a YAML header for the structured parts (rating, address, visits, dishes) and ordinary Markdown for notes. If I ever abandon this project the way Eatlist was abandoned, my data is still readable in any text editor, forever. I can even edit the files on the server by hand and the changes sync back to my devices.
- Export any time. One click gives me a ZIP of all those Markdown files.
- Every version is kept. The server keeps every version of every file as a backup.
- A way out of the old apps. Bite-Stamped can import my Eatlist data (restaurants, visits, people, dishes and photos) and my Foursquare / Swarm check-in export (places, visits, lists, tips and photos), merged together with the places I already have.
Why a web app, and why self-hosted
I made Bite-Stamped a web app on purpose. It's plain HTML, CSS and JavaScript with a small Node.js server: no frameworks, no build step, no dependencies. That makes it easy to host yourself on a home server, a Raspberry Pi, or a small VPS.
Self-hosting is the point. I don't want to run a service that holds other people's restaurant habits and location history, and I don't think you should have to hand that to anyone either. If you run your own copy, your data is exactly as private as you want it to be. It lives on your machine, and you decide who can sign in.
Even though it's a web app, it behaves like a phone app: it installs to the Home Screen, works offline, and syncs between devices when they're back online.
Built with Claude Code
I built Bite-Stamped with Claude Code, Anthropic's AI coding tool. I described what I wanted, tried it out, and kept refining: the first version, the Eatlist importer and device sync all came together on the first day, and the app has grown steadily since. It let me build the app I actually wanted, with the features that were missing from Eatlist, in the time I had.
What it does today
- Places of any kind, with rating, a "to try" flag, cuisine or category, address, website, phone, tags and notes
- Visits with date, rating, who I was with, and notes, plus one-tap check-in
- Dishes with rating, price, notes and a photo
- Photos with a title and a date (finally)
- A Timeline of every visit, by day or as a month calendar
- "Visited" and "To Try" lists, sorted many ways or shown on a map
- Search across everything, or by field:
tag:brunch,with:anna,city:knox - Finding and merging duplicate places
- Offline-first sync between devices
- A private calendar feed of my visits
- Export and import as a ZIP of Markdown files
Try it
The code is on GitHub at github.com/mckeehan/bite-stamped. The README covers running the server, setting up HTTPS so it installs on a phone, and running it as a service. If you've got years of Eatlist or Foursquare history you'd like to rescue, the import tools are there too.
And for the record: I can now tell you exactly when I was last at The Moose Cafe.