About
A map for menus
Metro Menu Map applies the conventions of a railway map to the menus inside a phone: screens as stations, submenus as lines, the current screen as the interchange.
The idea
A metro map is not geographically accurate and nobody cares. It is useful because it answers one question fast: how do I get from here to there, and where do I change lines? Menus on a phone pose exactly that question, and every app answers it the same slow way: tap, look, back, tap again.
Metro Menu Map takes a menu tree and applies the old cartographic rules. The screen you are on is the central interchange. Each submenu becomes a coloured line leaving the hub. Each screen you can reach along it is a station. Stations that branch again are drawn as interchanges, with the double ring every commuter recognises. Tap one and the map re-centres there.
Three rules of the drawing
Eight lines from the hub
Up to eight submenus each get their own line and colour, leaving on a 45° grid. Past eight, the extras share long trunk lines so the drawing stays legible instead of becoming a sunburst.
Bend after two stations
Lines run straight for two stations then turn 45°, which fans them apart and keeps labels from colliding on busy screens such as Accessibility.
Upright labels, always
Station names stay horizontal whatever angle the line takes, alternating sides on horizontal runs. A map you have to tilt your head to read is not a map.
What it is not
iOS does not let one app look inside another, so Metro Menu Map cannot read your Settings live. The Settings map is built ahead of time on a real iPhone, checked line by line, stripped of anything personal and bundled with the app. Pro users build maps of other apps the same way the author does: by recording a walk through the menus and letting the phone's own text recognition read each screen.
It is also not a chatbot. Search is root-word keyword scoring with a hand-kept synonym list. It is fast, it works in flight mode, and it will never make something up.