TripFlow

An AI-assisted travel planner that brings the whole trip together in one place, with real-time collaboration, interactive maps and full offline access.

Two smartphones showing the TripFlow app: a dashboard with trip stats and a trip detail screen for a Japan itinerary.
01

The problem

Planning a trip means juggling half a dozen tools that don't talk to each other. The result is information that's scattered, copied by hand and out of date almost immediately.

01

Information is scattered across search engines, maps, blogs and chats.

02

Nothing is connected: every detail is copied by hand and goes stale instantly.

03

In a group it multiplies: different preferences and changes that get lost.

02

The whole trip in one place

Most tools solve only a slice of the problem. TripFlow set out to cover the whole of it (time-based planning, AI, real-time collaboration and offline) in a single product.

MapsTripAdvisorRoamyWanderlogTripFlow
Time-based planning
Real-time collaboration Paid
AI generation
Offline support Partial Paid
Cross-platform
Pricing Free Free Free Freemium Freemium
03

Features

Everything you need to plan a trip, from the first idea to a shareable, offline-ready itinerary.

04

Distributed architecture

TripFlow is a distributed system: a React PWA talks to a set of Spring Boot microservices through a gateway, and those services coordinate asynchronously over an Apache Kafka event bus.

SPA / PWA client React · Vite
Gateway Cloudflare · Traefik · HTTPS
Microservices Spring Boot · Java 21
Main APIAINotifications
Event bus · Apache Kafka
Persistence PostgreSQL · H2
05

Key technical decisions

A handful of decisions shaped the project the most, around security, AI, real-time and offline.

01

JWT authentication

Dual JWT (15-min access, 30-day refresh) in HttpOnly cookies to mitigate XSS.

02

Async, secure AI

Prompt-injection filtering on the way in, and sanitization of the generated JSON on the way out.

03

Real time

WebSocket + STOMP with JWT validation in the handshake itself to authorize events.

04

Offline PWA

A service worker installs the app and lets you consult itineraries with no connection, mid-trip.

06

Quality & delivery

Built with a strong testing and automation culture from day one: every change ships through the same pipeline.

950+ automated tests 313 backend · 640 frontend · 8 E2E suites (Playwright)
67% code coverage measured on every build
803+ commits in CI/CD build + tests before every merge
100% automated deploy VPS · Dokploy · Traefik · HTTPS
07

The journey

TripFlow was my Bachelor's Thesis at Universidad Rey Juan Carlos, graded 10/10, designed and built end to end. It grew iteratively across three versions, and each one shipped as a working, deployed release rather than a prototype, from the first commit to v1.0.0.

v0.1 MVP

Authentication and base itineraries.

v0.2 Intelligence

AI, notifications and administration.

v1.0 Product

Maps, collaboration, share links, PWA and PDF.

Each release, documented from first commit to v1.0.0:

  1. Sep 2025 Introducing TripFlow
  2. Sep 2025 CI/CD & Testing TripFlow
  3. Nov 2025 TripFlow MVP
  4. Feb 2026 TripFlow v0.2.0: AI & Microservices
  5. Apr 2026 TripFlow v1.0.0: Collaborative Travel, Maps and Offline Access