How to vibe codeGoing
Flight Alerts, Mistake Fares & Cheap Tickets
going.com ↗Travel & Flight Alerts
The verdict: can you vibe code Going?
You can build a personal notification dashboard for a few airports, but the real challenge is continuously acquiring raw flight pricing data feeds.
Going relies on massive, continuous commercial airfare data streams and years of proprietary filtering logic to catch fleeting mistake fares. While you can spin up a web and React Native app shell using AI coding tools in a few weeks, your personal clone will stall out unless you build or pay for robust flight data pipelines. Furthermore, aggregating multi-region deals and wiring Apple and Google push notification certificates requires significant debugging friction.
Estimated effort: 6+ weeks of full-time development and data pipeline debugging
What you can't replicate
- Proprietary human-curated filtering rules honed over 13 years
- Commercial-grade global flight pricing data feeds
- Active community of over 2 million paying subscribers
Founded
2013
Raised
—
Team
50+
Cheapest paid tier
$49/yr
What Going does
Going monitors commercial flight data to alert users about major price drops, heavily discounted routes, and mistake fares.
Core features
- Flight deal ingestion engine
- Algorithmic filtering for price anomalies and mistake fares
- User preference settings (home airports and route regions)
- Email notification dispatch pipeline
- Push notification delivery for mobile clients
- Subscription tier management (Free vs Premium/Elite)
The business
Pricing
- Limited (Free)Free
- Premium$49/yr
- Elite$200/yr
Funding
Unknown / bootstrapped
Pay vs build, cumulative
No break-even inside 24 months at these numbers.
The hard parts of vibe coding Going
- Acquiring low-latency, comprehensive global flight pricing data feeds without expensive commercial licensing
- Filtering thousands of daily price fluctuations to isolate genuine mistake fares without false positives
- Maintaining low-latency push notification delivery at scale across iOS and Android platforms
How to vibecode Going
Prerequisites
Node.jsfree
Required for running the Next.js web application and backend scripts.
GitHubfree
Version control and deployment integration.
Expofree
Simplifies building and testing the React Native iOS and Android application.
AI coding tools
Recommended stack
| Frontend | Next.js (Web) & Expo / React Native (iOS/Android) |
|---|---|
| Backend | Next.js API Routes / Node.js background workers |
| Database | Turso (SQLite at the edge) |
| Auth | better-auth |
| Payments | Stripe |
| Other | Resend, OneSignal |
Build guide
01Project Scaffolding & Database Schema
Initialize the monorepo structure with a Next.js web frontend and an Expo React Native mobile app. Set up Turso database with tables for users, home_airports, flight_deals, and user_alerts.
Scaffold a monorepo containing a Next.js app in /web, a backend worker service in /worker, and an Expo React Native app in /mobile. Configure Turso SQLite with Drizzle ORM. Create tables for users (id, email, subscription_tier), home_airports (id, user_id, airport_code), flight_deals (id, origin, destination, price, original_price, airline, departure_date, return_date, is_mistake_fare, created_at), and user_alerts (id, user_id, deal_id, sent_at). Ensure TypeScript types are fully generated and enforce strict type safety across all workspaces.02Authentication & User Preferences
Implement authentication using better-auth and build user settings screens for selecting home airports and deal destination preferences.
Implement email/password authentication using better-auth integrated into the Next.js backend and shared across the Expo mobile app via API clients. Build a settings screen on both web and mobile that allows authenticated users to select multiple home airports (e.g., JFK, SFO) and specify their cabin class preference (economy, premium_economy, business_class). Store these preferences in user-associated tables and create API endpoints to fetch and update them.03Flight Data Ingestion Pipeline
Build a background worker script that mocks or fetches incoming flight price data feeds and populates the flight_deals table.
Create a background worker script in the /worker service running on a cron schedule. Implement a modular provider interface that can ingest flight pricing data either from public aviation APIs or structured mock feeds. Parse incoming pricing records, normalize origin and destination airport codes, calculate discount percentages relative to historical averages, and insert valid records into the flight_deals table. Include robust error handling and rate-limit management for external HTTP requests.04Deal Filtering & Anomaly Detection Engine
Develop the core filtering algorithm that evaluates flight deals against user preferences and flags significant price drops or mistake fares.
Develop a filtering and matching engine service that runs after every flight data ingestion batch. The engine must query active flight deals, compare prices against historical thresholds for specific routes, and flag deals with discounts exceeding 40% or obvious pricing errors as mistake fares. Filter deals matching user home airports and subscription tiers (e.g., economy-only for Free/Premium users, business class for Elite users), generating pending notification queue items.05Multi-Channel Notification Dispatcher
Wire up Resend for email alerts and OneSignal or Expo push notifications to dispatch deal alerts to users.
Build a notification dispatcher service that processes the pending notification queue. Integrate Resend for sending beautifully styled HTML email alerts containing deal summaries, direct airline booking links, and pricing details. Integrate OneSignal or Expo push notification services to dispatch real-time alerts to the mobile app clients. Implement idempotency checks to ensure users never receive duplicate alerts for the same deal ID.06Web Dashboard & Mobile Feed UI
Build the user-facing interfaces on web and mobile to browse active deals, view deal details, and manage subscriptions.
Build the deal feed UI in both the Next.js web app and the Expo mobile app. The interface must display a chronological list of active flight deals filtered by the user's home airports, featuring destination imagery, price drop badges, airline names, and direct booking CTA links. Include search filters by region and cabin class, along with a subscription upgrade page outlining Free, Premium, and Elite tiers.
Cost vs paying for Going
What will you build it with?
Starting total with Claude Code$0 one-time
Starting costs (one-time)
- AI Coding Tools (Claude Pro)$20
- Domain Name$12
Total~$32 one-time
Ongoing costs (monthly)
- Vercel Hobby/Pro Hosting$0-20
- Fly.io Worker Hosting$5
- Resend Email API$0 (Free Tier)
Total~$15-25/mo
Paying for Going
$4.15/mo (averaged across Premium annual plan)
Your time to build
40-60 hours
AI tool credits
$20 one-time (Claude Pro)
Break-even
Not a financial win (subscription is ~$49/yr, build is for learning and personal utility)
Vibe code Going: FAQ
- Can you vibe code Going yourself?
- Serious undertaking — 35/100 vibecodeable. You can build a personal notification dashboard for a few airports, but the real challenge is continuously acquiring raw flight pricing data feeds.
- How long does it take to vibe code Going?
- 6+ weeks of full-time development and data pipeline debugging — roughly 40-60 hours of hands-on time with an AI coding agent.
- How do you build your own Going?
- Scoped to personal use: Next.js (Web) & Expo / React Native (iOS/Android) on the front, Next.js API Routes / Node.js background workers behind it, Turso (SQLite at the edge) for data. Follow the 6-step build guide on this page — each step has a paste-ready prompt for an AI coding agent.
- How do you code your own Going without being an expert?
- Use an AI coding tool (Claude Code or Cursor) and work in small steps: scaffold, data model, core screens, then deploy. Realistic effort: 6+ weeks of full-time development and data pipeline debugging. The prompts on this page are written so the AI does the heavy lifting.
- How much does it cost to vibe code Going instead of paying?
- About ~$32 one-time to start and ~$15-25/mo to run, versus $4.15/mo (averaged across Premium annual plan) for Going. Break-even: Not a financial win (subscription is ~$49/yr, build is for learning and personal utility).
- What stack should you use to vibe code Going?
- Next.js (Web) & Expo / React Native (iOS/Android); Next.js API Routes / Node.js background workers; Turso (SQLite at the edge); plus Resend, OneSignal.