TabiPace

Does this day work for a 3-year-old and a 78-year-old at once?

No other travel app asks that question. TabiPace asks nothing else. Tell it what each traveller can manage, sketch the day, and it tells you who the day will break, and why, before you're standing at the bottom of a hill with a toddler and a cane.

Coming to Google Play

A TabiPace day: a red banner reading "Too much for Margaret, Theo and Mia", then a card per traveller: Margaret marked Over, with her specific breaches listed; Dave and Priya marked OK.
Why it exists

The itinerary was never the hard part

A multigenerational trip rarely fails because nobody knew what to see. It fails at 2pm on day four, when the toddler is past napping, the grandfather has done three flights of temple stairs he shouldn't have, and everyone is too far from the hotel to fix it.

That failure is predictable the night before. It's arithmetic, done against what each person can actually manage: distance, stairs, heat, rest. Nobody does that arithmetic at 11pm. So TabiPace does it.

How it works

Describe the people. Sketch the day. Read the verdict.

Three tabs, and none of them ask you what you want to see. They ask what everyone can manage.

The limits, written down once

How far someone walks in a day, how much rest they need and when, whether stairs or heat are a problem, whether they use a cane. It's the sort of thing a family already knows and has never written down.

The app is careful about this, and says so on the screen: the defaults are a starting point based on age band, not a judgement about anyone. You edit them to match the real person.

  • Age bands (toddler, child, adult, senior) set sensible starting limits you then correct.
  • Limits are specific and legible: walks 1h/day, needs 45 min rest 13:00 to 15:30, no stairs, heat sensitive, cane.
  • These limits drive every warning the app gives. Nothing is inferred behind your back.
The People tab: a card per traveller listing their recorded limits: Margaret as senior, walks 1h/day, needs 45 min rest, no stairs, heat sensitive, cane; Theo as a child; Mia as a toddler.

The day, sketched roughly

Not a minute-by-minute itinerary, just what you're thinking of doing, when, and who's coming. It's a sketch, and it's meant to stay one.

  • Each entry carries a start and end time, roughly how much walking it involves, and the things that matter for pacing: stairs, outdoors, the neighbourhood.
  • Who's attending is set per activity, which is what makes splitting the group possible later.
  • Days are switched with a row of chips across the top, so a four-day trip is four taps end to end.
The plan for one day: Fushimi Inari shrine from 09:30 to 14:00 tagged 2h 30m walking, stairs and outdoors, then Nishiki market and a group dinner, each listing the five travellers attending.

The verdict, in names and numbers

This is the part no other travel app does. The day is scored against every traveller, and where it fails it fails by name, with the specific limit it crossed.

  • A banner says who the day breaks: "Too much for Margaret, Theo and Mia."
  • Each person gets a status, Over or OK, and a bar, so a bad day is visible before you read a word.
  • Breaches are concrete, never vague: walking 3h 40m, over their 1h limit; no rest in 13:00 to 15:30, needs 45 min; stairs at Fushimi Inari shrine; 4h 45m outdoors in the midday heat.
  • Amber warnings are separated from red failures, so "uncomfortable" doesn't read the same as "won't work".
A day view: a red banner reading

And a check across the whole trip

Individual days can each be survivable while the trip as a whole still isn't. TabiPace looks at the shape of the days together and tells you whether the heavy ones are spaced out.

  • A plain verdict on the Trip tab: "No run of heavy days without a lighter one between them."
  • Trip name and dates live here too, so the whole trip is one object you can rename or reschedule.
Pricing. TabiPace is free for up to three travellers. Beyond that, which is most multigenerational trips, a one-off unlock covers unlimited travellers. No subscription.
The Trip tab: trip name and start and end dates, a green banner reading
Scope

What it deliberately is not

Those markets are crowded and well served. This one wasn't served at all.

Not an itinerary builder

It won't suggest attractions or fill your days. Bring your own plan, from a spreadsheet, a guidebook, or TabiPlanner.

Not a booking tool

No flights, no hotels, no tickets, no affiliate links. It never asks for a payment method.

Not an expense splitter

That's TabiLog's job, and it's a different app on purpose.

And never a source of medical advice. Where TabiPace handles medication, it does exactly one thing: shifts the times you entered into the destination's local time. It will not suggest a dose, a change or a schedule. Anything of that kind is a question for a doctor, and the app says so.
The shape of it

No account. No server. Nothing leaves the phone.

TabiPace is mobile-only and deliberately has no back end at all. There is no sign-up, no sync and no cloud copy. The trip lives on the organiser's device and nowhere else.

That's a real constraint, not a marketing line: everyone else in the group receives an exported PDF rather than a login. The trade is fewer features for a much simpler promise about where your family's health and mobility details are kept.

Health details stay local

What someone can walk, how they handle heat, when they take medication: none of it is transmitted anywhere, because there is nowhere for it to go.

Works with no signal

The whole app is on the device. A mountain village with no bars changes nothing.

Share by PDF

Export the plan and send it however you like. No one else needs to install anything.

Where it's up to

Built, signed, and waiting on a store listing

Version 0.1 is feature-complete and has been verified on a real Android device. The release build is signed and archived. What's left is the Google Play listing itself, which is paperwork rather than code.

When it's live, it'll be announced on the updates page.

A look around

The app, screen by screen

Select any screen to see it larger.

Screenshots from the v0.1 Android build, using the example trip.

The one that's ready today

TabiLog has been in daily use for a while now: separate budgets per traveller, receipts you can file later, and a report at the end that explains itself.