Group trips without the chaos
Every group trip starts the same way: endless WhatsApp threads, five different apps, and always someone missing something. Doodle for dates, Splitwise for expenses, Notes for packing lists, Google Photos for memories — and half the discussion gets lost in the chat anyway.
weReady brings it all together in one cheerful app. Date voting, automatic expense splitting, packing lists where everyone claims what they bring, and a shared photo album for afterwards. Planning together should be fun — not stressful.
From frustration to product
weReady was born out of pure frustration. As a group of friends, we organised the same weekend every year — and every year we ran into the same chaos. At some point it became obvious: this had to be better. What started as a side project grew into a full-featured app, live on the App Store and Google Play, with a landing page at weready.app available in 13 languages.
The goal was clear from day one: no feature bloat, no complex onboarding. Just an app that does what you expect from a planning tool, and does it well.
The modules that make the difference
Six core features mean you never have to switch between apps again:
- Planning — Date and activity voting, so decisions are locked in fast
- Costs — Automatic expense splitting with clear per-person balances
- Packing lists — Claim system so you never end up with three speakers at the campsite
- Ideas — Central hub for everything the group wants to do
- Meals — Plan meals per day, divide up the ingredients
- Photos — Shared album afterwards, no clutter in your camera roll
Mobile-first architecture
The app itself is built with React Native via Expo — one codebase for iOS and Android, with a native feel on both platforms. TypeScript end-to-end for type safety, and a handful of carefully chosen libraries to keep iteration fast without bloating the bundle.
Deeplink support via Universal Links (iOS) and App Links (Android) means sharing invites just works — tap the link, the app opens straight to the right trip.
Landing page in 13 languages
The landing page at weready.app is an Eleventy static site with a custom design system — no Tailwind, no framework overhead. Just CSS variables, Nunjucks templates, and an i18n setup that handles 13 languages: English, Dutch, French, German, Spanish, Italian, Portuguese, Polish, Romanian, Greek, Latvian, Turkish and Chinese.
Each language gets its own URL structure (/en/, /nl/, /fr/, …), optimised meta tags, and Open Graph data for social sharing. A blog with SEO-focused articles on group trip planning drives organic traffic.
Cloudflare + Convex: serverless without the headache
The backend runs entirely on Convex: a reactive database with TypeScript functions and realtime sync out of the box. Changes made by one group member — a date vote, a new expense, an item on the packing list — appear instantly for everyone else, without me having to set up any websocket infrastructure.
The landing page runs on Cloudflare Pages, with Cloudflare's global CDN, SSL and DNS on top. All serverless, no containers, no VMs to manage. Operational costs stay near zero while the site and the app load fast worldwide.
Business model
weReady has a free tier with the essentials: up to 3 active trips, 2 friend groups, 4 attendees per trip, and 50 photos per trip (150 lifetime). Enough to plan a weekend away with a few friends without ever hitting a wall.
weReady Pro unlocks it all at €19.99/year: unlimited trips, unlimited attendees, unlimited photos, plus the features that matter for bigger groups — document uploads (tickets, itineraries, boarding passes), multiple trip admins, and ghost members for friend groups. No ads, no data selling — just an honest model where users pay when they get value.
What makes this project special
weReady is my first own product from start to finish. No client, no employer setting direction — every decision (product, design, code, infrastructure, marketing) lands on my desk. That means learning by doing: app store submissions, writing a privacy policy, GDPR compliance, content marketing, pricing.
Reflection
Building your own product is a very different exercise from client work. You feel every decision — good and bad — directly in the metrics. It forces you to make choices you can sometimes avoid in client work: which feature do I actually build, what do I cut, where's the balance between polish and shipping.
The biggest lesson: shipping is a skill. The first version wasn't perfect, but it was live. The second was better. The third better still. That rhythm — build, ship, learn, repeat — is where I grow most as a developer.