One trip, one shared plan
Itinerary, bookings, tickets, map and to-dos in one app. No passwords, it runs on your own server, and it works without signal.
Android · needs an invitation code
One shared place instead of scattered tickets
The details of a trip usually live in five different places. We collect them here.
The problem
Scattered information
Hotel in an email, ticket in a PDF, plan in a spreadsheet. Before departure nobody can find what they need.
Hidden mistakes
No transfer after landing, a connection that is too tight, a night without a hotel: you only notice on site.
No signal, no data
Abroad without roaming, cloud tools are often useless exactly when you need the ticket.
The Mapify solution
One shared, private place
Itinerary, bookings, tickets, to-dos and places for one trip, with a role for every member of the group.
Automatic checks
After every change the server validates the itinerary and tells you what is missing or clashing.
There even without signal
Trip data is stored encrypted on your phone. Changes wait in line and sync by themselves as soon as you are back online.
What the app can do.
Everything listed here already works. The images are real screens of the app with made-up data.
Time zone aware timeline
Flights, stays, transfers and activities on a daily timeline, with local times and time zone changes marked.
Bookings and tickets
Open PDF tickets in the app and save them offline. Booking references are encrypted on the server, the app only shows masked values.
Smart warnings
Missing transfer, tight connection, overlapping events, a night without a stay, missing ticket: with fix suggestions.
Document import
Upload a booking (PDF, email, image): after a virus scan the data shows up as a proposal and you approve it.
Roles and suggestions
Admin, editor, contributor, viewer. Contributors suggest ideas, organizers approve what goes into the plan.
Map and routes
Places and ideas list, route search between places and a hand-off to your navigation app. Map tiles are optional.
Notifications without Firebase
Itinerary changes, new device awaiting approval, upcoming departure: with our own notification system (SignalR, polling, background task).
To-dos and offline use
Shared checklist, encrypted local cache, offline editing. Accessibility (TalkBack, large text, dark mode) has been tested.
What the app looks like
Today: next departure
Itinerary timeline
Warnings
Import review
Tickets
Dark mode
No password, no social sign-in.
You sign in to the app with a one-time invitation code (or QR code). The phone creates its own key pair and the private key never leaves the device secure storage.
Device-bound sign-in
ECDSA P-256 key in the Android Keystore. The admin can approve or revoke each device.
Protected data
Encrypted booking references, virus-scanned uploads, rate limiting, PIN lock in the app.
No ads, no tracking
No Google or Firebase dependency. Data stays on your own server, one instance serves one trip.
How you sign in
- 1The admin creates an invitation
- 2You type the code or scan the QR
- 3The phone generates a key pair
- 4A signed challenge completes the sign-in
The code is valid for 10 minutes and works only once.
What it is built with
We build it for our own trips, so it stays small and simple.
Technology
.NET 10 API and background worker, PostgreSQL 17, Flutter Android app (about 23 MB), React landing page.
Invitation only
Invitation only, one instance per trip. Data stays on your own server, nothing is sold.
Automatic checks
Every change runs the build, the tests, code analysis and a scan for vulnerable packages.
Get access
Mapify is a closed, invitation-only system. You get the app and an invitation code from us in person.
Android, about 23 MB. iOS is not planned.
How to get it
- 1Write to us and we send you the app installer.
- 2Allow installing from unknown sources for your browser or file manager.
- 3Open the file and install it.
- 4On first start enter the invitation code from the trip organiser, or scan the QR code.
The app is not usable without an invitation code, because Mapify is a closed system.
Status
What is done, what we are working on, and what will not happen.
System design and API contract
DoneData model, OpenAPI, roles and permissions
Backend
Done.NET 10 API, PostgreSQL, device pairing, sync, import, virus scanning
Android app
DoneTimeline, tickets, map, use without signal, notifications, accessibility
Automation
DoneAutomatic checks, release and deployment
Testing on real phones
In progressQR camera, battery and Doze, App Link verification
The first live trip
In progressReal use, feedback, fine tuning
Store distribution
PlannedOptional, if there is demand
Frequently asked questions
What is Mapify?
Mapify is a private, invitation-only trip planner Android app for groups of friends. The itinerary, bookings, tickets, map and to-dos of a trip live in one place.
Does it need a password?
No. You sign in with an invitation code or a QR code, and the phone creates its own key pair. The admin approves each device.
Does it work without signal?
Yes. Trip data is stored encrypted on the phone, tickets can be saved offline, and changes sync by themselves as soon as you are back online.
Is there an iOS version?
No, and none is planned. Mapify is built for Android only.
Where is my data stored?
On your own server, one instance serves one trip. There are no ads, no tracking and no Google or Firebase dependency.
How can I get access?
Mapify is a closed system. Write to us and we send you the installer, and the trip organiser gives you the invitation code.
Who builds it
Two of us build Mapify in our free time.
The two of us
We like travelling and programming. One of us does the backend and the infrastructure, the other does the interface and the design.
We both learn along the way, and we build everything from scratch.