🚧 COMING SOON — WEBSITE UNDER CONSTRUCTION 🚧
METRO MENU MAP

Features

What the app does, line by line

The home page gives the headlines. This page is the timetable: how each part actually works, what it reads, and what it ignores.

The map

A Canvas drawing you can pinch, pan and tap. The hub is where you are; everything else is where you could go.

Moving around

  • Tap a station to centre the map on it. Interchanges (double ring) have screens beneath them.
  • Up button or any breadcrumb crumb climbs back out.
  • Pinch to zoom, drag to pan, one tap on Fit to frame the whole drawing.
  • Lines beyond the eighth collapse onto trunk lines of up to six stations, one level deep.

Tuning the drawing

  • Line spacing slider, 40 to 140 points, live preview.
  • Stations per line, 4 to 15, before a line wraps onto a second ring.
  • System, Light or Dark appearance, applied instantly to open sheets too.
  • Eight-colour line palette tuned for both appearances.

Map any app Pro

No API, no permissions, no cloud. You record a walk through an app; the phone reads the recording.

Record

Open the app you want mapped, then start a screen recording from Control Centre. Anything on screen before the app opens ends up on the map, so open it first.

Walk

Open each menu, pause a moment on every screen, scroll slowly through long ones, go back. You don't have to be thorough; you can record more later and merge.

Import

Stop the recording and pick it from Photos. The app pulls a frame every half second, skips near-identical frames, and runs Vision OCR on the rest. A long recording takes a few minutes; it runs on the phone, so keep the app open.

Review and merge

Each detected screen is listed with its parent and row count. Delete anything personal, then merge. The summary tells you how many stations were added, refreshed and kept.

Screenshots work too. Pick them from Photos instead of a recording; the out-of-process picker means the app never gets library access. Tip from the app: Back Tap in Accessibility can take a screenshot when you double-tap the back of the phone.

How screens become a tree

The reader keeps three things per screen and nothing else.

TitleThe large heading. This is the station.
ParentThe small back-button label, top left. This is the line it sits on.
RowsLeft-hand labels only. Right-hand values ("On", "12%", network names) are discarded on purpose.

A row becomes a submenu only if some other screen has that row as its title and the current screen as its parent. Screens that never link are reported as orphans for you to fix. The app never guesses a tree into shape.

My Maps Pro

One map per app, each saved as its own file. The bundled Settings map is always there and can be reset to the shipped version.

Managing maps

  • Switch maps from the Maps sheet; the current one carries a tick.
  • Rename with the pencil, delete with a swipe, reset the bundled map to factory.
  • Station count and last-updated time shown per map.

Editing stations

  • Long-press any station (with a haptic tick) to open the edit sheet.
  • Rename an OCR misread, delete a station and everything beneath it, or centre the map there.
  • Rename the map itself by editing the hub.

What stays private

Concrete, not slogans.

Never happens

  • No network requests of any kind. There is no networking code to audit.
  • No analytics, crash reporting or advertising SDKs. No third-party code at all.
  • No Photos library permission; the picker is Apple's out-of-process one.

How data is handled

  • Recordings are copied to a temp file for decoding and deleted when done. Images stay in memory.
  • Maps are saved with complete file protection, encrypted whenever the phone is locked.
  • The bundled map was hand-sanitised: no Apple Account, Wi-Fi or Bluetooth names.
⇧