- Client
- SpikSpak
- Role
- Design & Development
- Timeline
- Ongoing
- Year
- 2026
- Category
- Travel App
Overview
SpikSpak is a collaborative trip planner: Expo 54 app plus static web, Firebase (`spikspak-f83e6`), Duffel flights, Mapbox. Trips include itinerary, packing, shopping, documents, invites, wallet, and flight search. Emails in code: hello@ / support@spikspak.com.
Why
Groups still plan trips across a flight app, a map, a packing list, a folder of PDFs, and a group chat. Reservations disappear in the gaps. SpikSpak makes the trip one object: itinerary, packing, shopping, documents, invites, and flight search.
Relevant to any collaborative travel product. Duffel is real flight inventory, not a screenshot; booking stays in test mode until a payment flow ships. Mapbox is the journey, not a static pin.
The challenge
Travelers still juggle a flight app, a map, a packing list, a folder of PDFs, and a group chat. Groups lose reservations in the gaps.
What made it hard
- Groups planned trips across flights, hotels, maps, chats, and email PDFs.
- Packing and documents never lived next to the itinerary.
- Flight search had to be real inventory (Duffel), not a screenshot.
Approach
One trip object: activities, packing, shopping, documents, collaborators. Duffel for flight search; Mapbox for the journey. Web dashboard mirrors the mobile loop.
Process
- Trip object: Create/join/invite as the social core.
- Ops inside the trip: Packing, shopping, documents, wallet.
- Flights + map: Duffel search and Mapbox visualization.
What we built
- Collaborative trips: Create, join, invite — the trip is shared state, not a forwarded spreadsheet.
- Itinerary + map: Activity detail with Mapbox context for the whole journey.
- Duffel flights: Real flight search; booking is built and runs in test mode until a payment flow ships.
- Packing, docs, wallet: The annoying fragments of travel live on the same trip.
How it was built
Expo 54 app plus static web on Firebase `spikspak-f83e6`. Trips include activities, packing, shopping, documents, collaborators, wallet. Duffel powers flight search; booking runs on test keys until payments ship. Mapbox visualizes the journey. Web dashboard mirrors the mobile loop.
Emails in code: hello@ / support@spikspak.com. Create, join, and invite are the social core. Package 1.0.0, pre-launch: spikspak.com runs a waitlist.
Stack
- Expo 54: Mobile + web
- Firebase: Auth, Firestore, Storage, Functions
- Duffel: Flight search
- Mapbox: Trip geography
Outcomes
- 1 trip: Itinerary, packing, docs, wallet
- Duffel: Flight search
- Mapbox: Journey visualization
- Beta: Expo app 1.0.0
Wins
- One trip object: itinerary, packing, docs, shopping, wallet.
- Duffel flight search, with booking built and held in test mode.
- Mapbox journey visualization.
- Collaborative create / join / invite on mobile and web.
Hard parts
- Fragmented planning: Flights, hotels, maps, chats, and PDFs never lived together. The trip object had to replace that pile.
- Real inventory: Flight search had to be Duffel, not a mock. Booking stays on test keys until there is a real payment flow.
- Packing next to the itinerary: The annoying fragments of travel had to sit on the same trip or people bounce back to Notes.
Services
- React Native / Expo
- Mapbox 3D Routing
- Duffel API (Flight Search)
- Trip Documents & Packing
- Itinerary Builder