How Zarparia works, in plain language — what each screen does and how to do the everyday things. Nothing here is a substitute for exploring the app yourself.
Zarparia only supports signing in with a Google account — there's no separate password to create or remember. Your name, email and avatar come from Google; nothing else about your Google account is touched unless you separately connect Google Photos.
Where available, you can also create an account with just an email address and a password instead of using Google. Create an account from the sign-in card, then check your inbox for a verification link — you need to verify your email before you can sign in.
Forgot your password? Use the "Forgot password?" link on the sign-in card to get a reset email. If you sign in with Google using the same email address you used for email+password, both reach the same account — Zarparia treats a verified email as one identity no matter which way you sign in with it.
Zarparia is a small, invite-only beta. The first time you sign in, your account is created but marked pending until the operator approves it — you'll see a review screen instead of your trips until then. There's nothing to do but check back; approval doesn't require you to sign in again.
Once approved, use 'New trip' to open a short wizard: give the trip a title and start date, then list the places you're going with how many nights at each. It builds the itinerary and drops you straight into it in edit mode, ready to fill in. Or start from a blank trip, which creates an empty one-day trip you rename and build up in place.
You don't need an account to see what Zarparia looks like with a real trip in it. The demo is a fully interactive sample itinerary — everything responds, nothing is saved, and it never touches a real account.
Your home screen once you're signed in and approved. It lists trips you own and trips others have shared with you, with the currently-happening trip (if any) pulled out into a highlighted card at the top.
The read-through view of a trip: a day-by-day itinerary with times, places, notes and a map, grouped into segments. This is what you see when you open a trip, and what anyone you share it with sees too. On a phone, Print and Add to calendar live under More in the bottom bar; on a wider screen they sit in the trip header.
Each day also shows a weather forecast, when the trip is close enough in time for one to be available. For trips that have already happened, the editor can instead record the weather that actually happened, so the day still shows something useful.
Every stop the app can locate is numbered, and that number is the same in all three places it appears: on the dot beside the time, on the pin on the day map, and in the Day Route strip under it. Stop 5 is pin 5. A stop that has a Maps link but no map location is still numbered and still joins the route, it simply cannot be pinned — so pin numbers may skip. Set a missing location with Find place in the stop’s ⋮ panel.
To move between days, tap a date in the strip across the top, or swipe left and right anywhere on the day itself. The date strip stays pinned as you scroll and picks up a line naming the trip and the day you are on, so you never lose your place in a long day. On a wide screen the days move into the sidebar instead, and the day’s map and route sit beside the itinerary rather than above it.
Press Edit on a trip and the itinerary itself becomes editable — you change the words where they are, in the finished trip, rather than in a separate form. Click any title, description or note and type. Empty fields show a faint prompt where you can add a description or a note for the day.
Everything about a stop that is not free text — its time, tags, cost, walking distance, map location, dot colour, waypoints, photo spots and booking links — lives behind the ⋮ button on that stop. It opens a small panel for that one stop (a sheet from the bottom of the screen on a phone), so you are never handed the whole trip as a form. The Find place search fills in the map location for you.
A stop's checklist is edited on the stop itself: click its heading or any item to reword them, ✕ to drop an item, and + to add one. Use the ⋮ panel to add a checklist to a stop that has none, or to remove it entirely. Ticking items off works whether or not you are editing.
To change the shape of a day rather than its words: hover between two stops for the + that adds one above, use Add a stop at the end of the day, drag the ⠿ handle on the left rail to reorder, and use Duplicate or Delete inside a stop’s ⋮ panel (which also has arrows for moving a stop up or down without dragging).
The day itself has its own ⋮ beside the date at the top of the day, holding the day's date, route mode, a walking-distance override and the stored weather used for past trips — plus Add day, Duplicate and Delete. A new or duplicated day takes the first free date after the one you were on, so days never end up sharing a date; if that puts it out of sequence the panel says so, and you can set the date you want.
Photos follow the day they are on. Re-date a day, or reorder the stops within it, and the photos move with it — they are tied to the day and stop themselves, not to the date or the position. Photos added long ago may still be tied to the date; where any remain, the day panel says so before you change it.
Plan variants live on the tabs under the segment name. While editing, that row is always shown — even on a segment with a single plan, since it's where the second one is created. + adds a variant as a copy of the one you're on, and the ⋮ beside it renames the tab, chooses which variant opens by default, sets the prefixes used on per-stop comparison notes, and duplicates or deletes the variant. When a segment has more than one, each stop's ⋮ gains a control marking it added, changed or kept versus the other plan, with a short reason.
The segment — the run of days in one place, whose name sits at the top of the trip — has a ⋮ of its own beside that name. It holds the colour theme and any custom colours overriding it, the location and timezone used for weather forecasts, which plan variant opens by default, and the segment's internal id, plus Add segment, Duplicate and Delete.
Changes save on their own about a second after you stop typing; a small label near the top shows Unsaved, Saving… and then Saved, so you never have to hunt for a save button. Undo and redo buttons sit beside that label, and Ctrl+Z / ⌘Z works too — inside a text field it undoes your typing, as in any text box; anywhere else it steps back through changes like adding or deleting a stop. Deleting always offers an Undo on the message it shows.
If a change leaves the trip incomplete — emptying a day of all its stops, say — saving pauses and says so rather than storing something broken. Your edits stay on screen; put a stop back and it saves immediately.
You are always editing the language you are currently reading. Switch the EN/PT toggle in the trip header and you edit that language instead, leaving the other one untouched.
If someone else changes the same trip while you have it open, saving pauses and a notice appears rather than overwriting their work — copy anything you have just written, then reload to carry on from the latest version. Press Done to leave edit mode.
Everything that describes the whole trip rather than any one day: title, cover emoji (the one shown on the trip's card in your trips list), languages, date format, currency and budget, the home base and the tag list. Press Settings on a trip and it opens as a panel over the itinerary, saving as you go like every other edit. Only people with edit access (owners and editors) see it.
Segments, plan variants and days themselves are not here — each is added, reordered and removed from its own ⋮ on the itinerary, beside the thing it belongs to. There is no separate editor screen any more: everything about a trip is changed on the trip.
A stop can hold more than one plan — alternate versions of the same days, for example a rainy-day option alongside the usual one. Anyone viewing the trip can switch between a stop's plans using the plan tabs in the trip view.
Paste a rough itinerary — an email thread, a list of notes, even a loose sentence describing the trip — and Zarparia turns it into a draft trip you can refine afterwards in the editor. It's a starting point, not a finished result; expect to tidy it up.
Pasting an itinerary is currently switched off, so you won't see it in the menu. The connector below does the same job from your own Claude app — and builds a richer trip — so use that in the meantime.
Your account page: export everything Zarparia holds about you as one file, or permanently delete your account. Reached from the sidebar (desktop) or the More sheet (mobile).
Open the trip and use Share. You can invite someone by email as a viewer or editor — if they don't have a Zarparia account yet, the invite is held as “Pending sign-in” and turns into real access the first time they sign in with that email — or turn on a shareable link that grants view or edit access to anyone who has it, no sign-in required for viewing.
Each person in the list has an Email button that opens a ready-to-send message in your own mail app, worded for their case: someone still pending is told to sign in with that email to get access, while someone who already has access just gets a link to open the trip. Pick the email's language with the selector (it defaults to your app language). Nothing is sent automatically — you send it yourself, from your own address.
Opening a shareable link someone sent you shows the trip straight away if it's set to view access. If it grants edit access, or the link owner turned it off, you'll be asked to sign in first so Zarparia can check the invite is still valid.
From a trip's Photos panel, connect Google Photos and pick photos with Google's own picker — Zarparia only ever sees the exact photos you select, never your whole library. Picked photos are matched automatically to the right day by when they were taken; any that fall outside the trip dates land in an "unmatched" section you can move by hand.
Install Zarparia as an app (from your browser's "install" or "add to home screen" option) and it keeps a copy of your trips available without a connection. Visit a trip once while online to make sure it's cached; changes made offline sync once you're back online.
From the Account page, "Export my data" downloads a single JSON file with everything Zarparia holds about you: your profile, your trips, sharing records, feedback you've sent, and your photo records.
Open a trip and use the "Add to calendar" button, always visible near the top — it downloads a single .ics file for the whole trip. Import that file into Google Calendar, Apple Calendar, Outlook or any other calendar app that accepts .ics files, and each event carries the trip's local times.
Open a trip and use the "Print / Save as PDF" button near the top. It opens a clean, A4-formatted document with the whole trip — every day and every stop laid out flat — and your browser's print dialog appears automatically. Choose your printer to print it, or pick "Save as PDF" as the destination to keep a file. Shared trips can be printed the same way from their public link.
Give a trip a currency and a total budget in Trip settings, then add an estimated cost — with an optional category (lodging, food, transport, activities, shopping or other) — to any stop in the block editor. Zarparia sums those into a per-day subtotal and a whole-trip total, shown against your budget as a colour-coded bar at the top of the trip: green while you have room, amber as you approach the limit, red once the estimate goes over.
The bar keeps to a single compact line at the top of the trip — the running total against your target, over a slim progress track. Tap it to expand exactly how much is left, or how far over the estimate has gone.
Because each alternative plan has its own stops, the total re-calculates when you switch plans — so you can compare what two versions of the same days would cost. If you set no budget but still add costs, the bar just shows the running total.
In the block editor, any stop can carry one or more booking links — paste the URL of a hotel confirmation (Booking.com, Expedia, Airbnb, Hotels.com and others), a restaurant reservation, or a ticket. Leave the label blank and Zarparia names the pill from the link itself (for example a booking.com URL shows as "Booking.com"); set a label to override it.
The links show up as tappable pills on the stop in the trip view, and are listed in full — label and URL — on the printed/PDF itinerary. They travel with the trip, so anyone you share it with sees them too; only add links you're happy for those people to open.
Also from the Account page — this is permanent and cannot be undone. Trips you own are deleted, including for everyone they were shared with; trips shared with you are simply removed from your access, not deleted. You'll be asked to type a confirmation before it happens.
The EN | PT switcher changes the app's own language (a trip's content can be in different languages again, independently). The theme control cycles light, dark and system. Both live in the sidebar on desktop and in the More sheet on mobile, and are remembered for next time.
Advanced/optional: Zarparia has an MCP connector that lets an AI assistant (for example, Claude) read and edit your trips on your behalf, once you approve the connection through a standard OAuth screen. Access tokens are stored hashed, and a pending account cannot use this even with a valid connection.
Trips the assistant creates come fully built out — maps links, a live weather strip, photo spots, per-stop costs and booking links — not a bare skeleton. One thing to know: the connector acts as whichever account you approved it with, so sign in to Zarparia with that same account to see those trips in your list.
Use the feedback button — a speech-bubble icon in the sidebar (desktop) or the "More" sheet (mobile) — to send a bug report, an idea, or anything else. Your submissions are listed on the Feedback page (/feedback); deleting your account deletes them along with the rest of your data.
What happens next: every submission is read and triaged. If an idea is accepted it appears on the Roadmap (/roadmap), in both English and Portuguese, and your submission's status on the Feedback page changes to "planned" or "done". Nothing you write becomes public automatically — only the wording rewritten at triage goes onto the roadmap.
A single itinerary — one or more segments (Florence, Rome, the Amalfi Coast…), each with its own days and schedule. Within a day, the individual places and activities are called stops.
One day within a trip's schedule: a date, an optional title and note, and a list of timed blocks (places, activities, travel).
An intermediate place within a single stop. A stop is where you are; its waypoints are what you pass through while there — a park walk might list the lake, the gardens and the fountain. They appear as their own numbered entries in the Day Route, and the route you open in Google Maps threads through them in order.
Add or edit them in a stop’s ⋮ panel while editing the trip.
A single URL that grants access to a trip to anyone who has it, without naming individual people. Can be turned off, or switched between view and edit access, at any time by the trip owner.
The two roles a trip can be shared with: a viewer can read a trip but not change it; an editor can also add, edit and reorder its content. Only the owner can delete a trip or change who it's shared with.
A signed-in account that hasn't yet been approved by the operator. It can't read or create any trip, photo or feedback data until approved.
The public sample trip at /demo — fully interactive, requires no account, and never saves anything or touches real data.