The GIS App
A routing tool for reaching disaster zones when the roads, the risks, and the map itself all keep changing.
Overview
A GIS routing app for the hours after an earthquake, built for two kinds of users: civil defense employees and NGO field workers who need to reach a specific point in an affected area while roads are blocked, security conditions are shifting, and the map itself may already be out of date. The job isn't to display a map — it's to help someone decide, under pressure, which route is still passable and worth the fuel.
Post-disaster devastation, environmental damage and security risks make it difficult to reach the area where help is needed — and the best route can turn into the wrong route within hours.
Let responders read and act on environmental and security data directly, so the route they choose accounts for what's actually happening on the ground, not just distance.
Research
Four interviews — NGO field workers who had worked in the aftermath of the February 2023 earthquake in Turkey, plus a developer who builds mapping data and software for that same field — alongside a review of humanitarian routing research1 and a competitive audit of ArcGIS, QGIS, ABetterRoadPlanner and OpenRouteService.
Velia Mazzi
Doctor · 37Works for the Italian Civil Defense Department. Joined Médecins Sans Frontières after graduation and worked in South Africa for two years.
Introvert, creative, time-poor, active, risk-tolerant
Save people's lives · reach places quickly · get the patient to the hospital
Using tech devices · being late · finding the place where help is needed
Cosmo Milan
Vet / NGO worker · 29Veterinary and INGO worker with the Civil Defense Department in post-disaster emergencies, and an animal rights activist. Previously in search and rescue.
Extrovert, analytical, team player, safety-first
Save animals' lives · get them out of the shelter to safety · travel safe
Accessibility considerations · being late · encountering any security alert situation
Marta Bachman
Logistics manager · 42Logistics manager at the Civil Defense Department in post-disaster emergencies, with extensive field-coordination experience.
Balanced introvert/extrovert, analytical, organized, safety-first
Deliver supplies to the people who need them · travel the most energy-efficient way
Preventing damage to the goods · running out of gasoline · encountering something new the app doesn't map
1 — Anuar, W. K., Lee, L. S., Pickl, S., & Seow, H. V. (2021). Vehicle routing optimisation in humanitarian operations: a survey. Applied Sciences, 11(2), 667.
Ideation
A competitive audit of four routing tools made the gap clear, then an affinity map — built directly from the interview notes — converged on five needs no single competitor covered well.
| Tool | Strengths | Weaknesses |
|---|---|---|
| 01ArcGIS | User-friendly interface, advanced mapping tools, wide range of plugins, integration with ArcGIS products. | Steeper learning curve, limited compatibility, higher system requirements, expensive pricing. |
| 02QGIS | Open-source and free, extensive plugin library, community support. | Steeper learning curve, limited technical support, performance can be slower. |
| 03ABetterRoadPlanner | Focus on road planning, seamless collaboration, customizability. | Limited scope, smaller user base, potential learning curve. |
| 04OpenRouteService | Powerful routing capabilities, open data integration, flexibility. | Limited full GIS capabilities, interface design, lack of offline functionality. |
Five insights
An interface a non-specialist can operate — no assumed GIS literacy.
A system that adapts to conditions changing hour to hour, not a static route.
A way to hold data no one has verified yet, without treating it as fact.
Enough customization that a doctor, a vet, and a logistics manager can each shape the route around what matters to them.
A map layer system responders can navigate and understand at a glance.
Design
Two flows carried the rest of the work.
From wireframe to prototype
Five of the mid-fidelity screens were taken to full high-fidelity, working from the same research and the same flows — shown in the next section alongside this matching set of low-fidelity wireframes.
Three of the screens below are captured live, right off the working prototype, not flat mockups: the login form switches between "Log in" and "Create account" and reveals the password; the dashboard opens and closes its Layers panel and Preferred features; the route-finding flow steps through all four moments, with working toggles at each one. Free-draw stays a screenshot — everything else here responded to a click.
Key screens
The live dashboard, the login flow, and the route-finding assistant — captured mid-interaction, not staged.
18 minutes ago
Four moments from the route-finding flow that go beyond a straight A→B search: looking up an address in the field-assignment table, reading a security alert before keeping or ignoring a route, adding a fuel stop, and choosing to be notified of last-minute changes.
Responsive — one direction, sketched
Built primarily for a desk: control-center and civil-defense staff working from a PC is the core case, with field staff expected to log in from a PC where one's available. Tablet and phone support was scoped in for the moments a PC isn't available — which is why desktop got the full pass and this got one sketched direction, not a matched system.
Empty & error states
Three states the hi-fi pass skipped the first time around, designed against Nielsen Norman Group's empty-state guidance2: say why it's empty, never blame the person looking at it, and give them a next step instead of a dead end.
No field assignments yet
No one has logged field work in this zone yet. Check back once your team starts a task here.
First use — nothing has happened yetYou're offline
Showing the map as of your last sync, 2 minutes ago. Move to a signal area to reconnect and load new reports.
Degraded — stale data, not no dataNo active hazards nearby
Nothing reported around Guastalla right now. Markers will appear here as soon as a field report comes in.
All-clear — reassurance, not a gap2 — Nielsen Norman Group, empty-state and error-message guidance.
Notifications — toast pattern
Route and hazard updates surface twice: as a toast the moment they happen, and logged in a running list behind the bell icon — the same updates also feed the stats-row charts on the dashboard. Left border and icon carry the meaning, so the message still reads with color alone removed.
Design decisions & heuristic evaluation
A heuristic pass against Nielsen Norman Group's usability heuristics, crisis-response UX research, and Esri's GIS accessibility guidance pushed eight changes into the screens above.
Hazard markers read by icon shape now, not color alone
A flame, a shield, a wave — so the distinction holds for colorblind users.
Secondary text raised to WCAG AA
In both light and dark theme, across every screen.
The wheelchair transport mode says so directly
Rather than showing a blank duration where it had no route data.
An "offline-ready · synced" badge
Every field interview raised the need to save a route before connectivity drops.
Unverified field reports get a dashed marker
Instead of looking identical to a confirmed hazard.
The layers panel now starts closed
One less thing competing for attention under stress, opened only on request.
"Avoided features" got an inline explainer
Jargon that tested fine with GIS specialists, badly with everyone else.
An accessibility-mode toggle sits at the map's bottom-left
Carried over from the mid-fidelity wireframes' icon rail, where it lived all along.
This was a solo, seven-day sprint, and these are the trade-offs that came with it:
- The collapse affordances on the sidebar and stats row signal intent, not a finished feature — the collapsed-state layouts weren't designed, because the sprint's scope didn't reach them.
- Accessibility mode — the corner toggle is real and clickable; the alternate reading it promises, per its tooltip, isn't built yet. Designing those screens properly didn't fit in seven days, so the toggle names what it would do rather than pretending to do it.
- Language selection — Settings was scoped to include a language picker, for field teams who don't work in Italian, but the screen itself was never designed. Flagged here as a known gap, not silently dropped.
Onboarding & trust
A second pass benchmarked the app against Waze's hazard reporting, Esri's ArcGIS Field Maps, Google My Maps' drawing tool, and research on trust in crisis informatics. Four decisions came out of it.
Sign-up stayed a single step, not a wizard
The disability and vehicle questions are as load-bearing as identity here — splitting them into a later step would let someone start planning a route the app can't yet route them through.
Security zones carry a verification-status pill
Unverified, or confirmed by multiple reports — following the same confirm/dispute logic Waze uses for hazards. The full confirm-or-dispute loop behind it wasn't designable in this pass; the pill is where it would surface.
Reporting is open, managing it isn't
Any field worker can submit a report from the road — that's the whole point of putting this in as many hands as possible. What reaches the dashboard is then verified and managed by an office-based admin team, not by the field workers themselves.
Accounts are personal, not tied to an organization's SSO
Unlike ArcGIS Field Maps. Disaster response spans civil defense, NGOs, and volunteers with no shared identity provider between them, so the map has to work for whoever shows up.
Design system
Framed as a style guide, not a full design system in NN/g's sense3 — no component-state documentation, pattern library, or governance model. Right-sized for one case study; it would need those layers before scaling to a real product.
Color
500 (#5B2E8A) is every primary action; 100 tints backgrounds, 900 is the brand surface. Warning renders as #9C5605 on text to clear WCAG AA — the fill stays #C9740B, since icons only need 3:1. Neutral runs background through to ink, light theme top row and dark theme bottom row, each mirrored across both.
Type & grid
An 8/14/20/28px spacing scale; a fixed 336px sidebar, 64px top bar, 196px stats row.
Iconography
Single-weight line icons, 24px grid, 1.5px stroke, rounded joins — 32 in active use across the five screens, grouped below by what they do.
Buttons & inputs
3 — Nielsen Norman Group, "Design Systems 101."
Reflection
UX is never done. What's here is the finished high-fidelity pass — built from the same research and the same flows as the wireframes above, with the login, dashboard, and route-finding steps genuinely responding to a click rather than just pictured.
Usability testing with real field teams is the honest next step — the one still open, and where this case would go next. This was solo work, too: the research phase talked to several disaster-response specialists and went deep, and in hindsight the balance tipped further than it should have — more time in the screens themselves, detailing states and edge cases, would have been the better trade against how thoroughly the research ran.
Next time the fix is simple: time-box research to two or three days no matter how good the conversations get, and protect the rest of the week for the screens themselves.