We Built an App Where Your Words Drift on Real Wind

Earlier this year I shipped Message in the Wind, a location-based anonymous messaging app where notes don’t sit still. You write something, release it, and the app uses real local wind data to carry it across a map. Someone standing near its path can catch it. Or not. That’s kind of the point. Here’s why I built it, what went into it technically, and what it’s taught me about building your own thing while running client work at the same time.

It started with a bottle

There’s something about the message in a bottle that never really gets old. You write something, seal it, throw it into the ocean, and let go of it completely. No read receipt. No delivery confirmation. Just the question: where did it go? How far did it travel? Did anyone ever find it? People have been doing this for centuries, and the stories that come back are remarkable - bottles crossing oceans, found decades later on the other side of the world, with notes still legible inside. The gap between releasing something and hearing where it ended up is part of what makes those stories worth telling. I kept thinking about that gap. What made it interesting wasn’t the message itself. It was the journey, and the not-knowing. Most messaging apps are engineered to eliminate that feeling entirely. Instant delivery. Read receipts. Typing indicators. All of it designed to collapse the distance between two people as fast as possible. That’s useful. It’s also the opposite of what makes a message in a bottle worth sending. I wanted to build something that brought that old tradition into the present - not as a gimmick, but as a real mechanic. Something that blended the physical act of releasing something into the world with the actual physical world around you. Wind felt right. Wind is real, it’s directional, it changes, and nobody controls it. Release a note in the morning and it might travel northeast. By evening the wind has shifted and it goes south. That unpredictability isn’t a bug. It’s the whole thing.

What’s under the hood

The app runs on Laravel with Livewire 3 and Alpine.js on the front end. The map is Leaflet.js with dark CARTO tiles. I spent an embarrassing amount of time getting the map aesthetic right, because the visual language of the whole thing depends on it feeling like you’re looking at real terrain, not a stylized graphic. Wind data pulls from a weather API on a per-region basis. Notes have a starting coordinate, a bearing derived from current wind direction, and a drift speed. Every few hours the position updates. “Caught” means your GPS is close enough to the note’s current position. You don’t get to see notes coming from far away. Proximity is the whole mechanic. A few things I built that I’m still happy with: the approximate location system, the tone picker, and the drift tracker. Approximate location was a deliberate design decision, not an afterthought. Your precise coordinates never leave your device in a readable form. The app works with a fuzzy radius: close enough to matter, not close enough to pin you. The tone picker lets you tag a note as Restless, Wistful, Gusty, or a few others before releasing it. It affects how the note looks when someone catches it. It’s a light touch but it changes how messages read. A Gusty note feels different than a Breeze. The drift tracker is the My Wind tab. You can follow your released notes on a live map and watch how far they’ve traveled. One of my test notes moved about 10 miles overnight. I built the feature partly because I wanted to watch that happen - to recreate that feeling of tracking something you let go. The full brand system, name, logo (the “Carried Dot”), the Fraunces and DM Sans pairing, color palette, I designed all of it before writing a line of code. That’s how I like to work. A clear visual identity makes every UI decision easier because you’re not solving two problems at once.

Building it alongside client work

I don’t have a clean productivity lesson here. It was messy. The honest version: I worked on MITW in gaps. Late nights, weekend mornings, the occasional afternoon when client work was sitting in review. I didn’t track hours. I probably should have. What I can say is that building something of your own changes how you approach client work, and vice versa. Client projects get sharper when you’re making real product decisions on your own time, not just executing someone else’s spec. Your own project gets more disciplined when you only have two hours and can’t afford to spiral on something that doesn’t matter. Shipping was the hard part. I had a version that was probably ready months before I pushed it to production, but I kept finding reasons to iterate. At some point you have to decide the thing is real.

What it is, practically

Message in the Wind is live at messageinthewind.com and available on iOS and Android. There are currently over 1,100 notes in the wind right now. It’s not trying to grow fast. It’s not a social network. It’s for people who find something interesting about the idea of an anonymous note traveling toward them on actual wind. Some people get that immediately. Some don’t. That’s fine. If you want to try it: release a note somewhere, then check back the next morning and see where it went.

Message in the Wind was designed and built by AiluroTech. If you’re curious about the product thinking, the tech stack, or the brand work behind a project like this, get in touch.