Showcase or use case — what does a smart city actually need?
🤖 This essay was generated with AI from the sources linked throughout. It has not had a complete human review — treat it as a starting point and follow the sources. How this works.
Self-driving buses win headlines; digitising a permit process wins Tuesdays. Helsinki's world-famous mobility app is gone; the boring interface behind its journey planner now runs in three countries. The evidence says both matter, but for very different reasons.
In March 2024, the company behind the world's most famous smart-mobility app went bankrupt. Whim had made Helsinki the global reference for mobility-as-a-service: one monthly fee covering transit, taxis, bikes and rental cars, and a decade of conference stages to go with it. It no longer runs. What does still run in Helsinki is the thing nobody made a keynote about — the transit authority's journey-planner interface, opened to developers in 2009, which quietly turned into open-source software that Estonia, several German cities and Oklahoma City now run too. Which raises the question this piece tries to answer without picking the winner in advance: what does a smart city actually need — the showcase or the use case?
Two words that get used interchangeably — and shouldn't be
A use case starts from a problem that already exists, usually an analog process that wastes time: applying for a residence permit, renewing a licence, reporting a broken streetlight. The smart-city version is rarely photogenic. Offenbach's AI-assisted document check for residence permits or Buenos Aires putting city hall inside WhatsApp are use cases: their success metric is whether Tuesday got easier.
A showcase — in funding language, a lighthouse project — demonstrates what is newly possible: drone deliveries over Berlin, a hydrogen-piped housing district, an entire city built from scratch in the desert. Its success metric is different: what it attracts (funding, talent, attention) and what it teaches.
The evidence against showcases is really evidence against orphaned pilots
The research critique has a name: pilotitis. The most careful study of it, by Van Winden and van den Buuse in the Journal of Urban Technology (2017), followed smart-city pilots in Amsterdam and found that many simply fade out — because scaling up demands different people, funding and governance than piloting, and nobody planned for that handover.
— paraphrased from Willem van Winden's own summary of the Journal of Urban Technology study (2017) on why smart-city pilots fail to scale
A 2021 study in Nature Humanities & Social Sciences Communications coined "pilot project purgatory" for autonomous-vehicle trials that never graduate into service, and Germany's driverless-shuttle scene illustrates it: some twenty pilots, completed and ongoing, have run in Munich, Hamburg and Ulm alone, and the transport association VDV's own president has pleaded to stop adding test labs and get autonomous services into regular operation. Germany's own programme evaluation points the same way: the federal institute BBSR commissioned dedicated studies on scaling because keeping pilots alive and transferring them beyond the 73 funded projects, to the roughly 11,000 municipalities the programme is meant to benefit, is the acknowledged weak spot.
This atlas's source-checked entries sharpen the point: Dhaka's automated signals and Algiers' camera-linked network were installed and never operated, and Masdar City delivered a fraction of its zero-carbon promise. The pattern in every case is not "the technology failed" — it's that nobody owned the operating model after the ribbon was cut.
What showcases actually buy
And yet the ledger has a second column. The EU has put, by its lighthouse community's own tally, some €920 million into eighteen smart-city lighthouse projects precisely because demonstrations do things spreadsheets can't: prove replicability, create city-to-city learning structures in which lighthouse cities mentor followers, and pull in private investment. Some showcases convert directly into infrastructure: London's congestion-charge cameras — a bold demonstration in 2003 — became the ANPR backbone that now runs the ULEZ. Barcelona's Poblenou superblock began as a cheap, contested demonstration and ended as permanent public space — the showcase was the method.
Munich's Smarter Together is the cleanest German example: being picked as an EU lighthouse city alongside Lyon and Vienna was pure showcase — and what it bought Neuaubing-Westkreuz was refurbished buildings, eight mobility stations, smart lampposts and a data platform. The EU money stopped in 2021; the infrastructure it paid for is still in use. The showcase paid for the use cases.
The quiet counter-model: infrastructure for use cases
The purest use-case strategy on record is Estonia's. Its X-Road data-exchange layer is invisible, unphotogenic plumbing — and it carries, by the operator's own figures, some 3,000 e-services, with the operator's current count putting 100% of state services online. Germany's "Einer für Alle" principle (one state builds a service, all reuse it) applies the same logic: Offenbach's residence-permit AI wasn't built in Offenbach — it was built once, piloted in seven authorities from February 2026, and switched on nationwide by late June, with trade-press reporting some 350 immigration authorities already running the shared service. Use cases compound; each one makes the next cheaper.
Side by side
| Use case | Showcase | |
|---|---|---|
| Starts from | An existing problem (usually an analog process) | A new possibility worth proving |
| Success metric | Daily value: time saved, errors avoided, services used | What it attracts and teaches: funding, talent, learning |
| Typical funding | Operating budget; reuse programmes (EfA) | Competitions, federal/EU project grants |
| Typical failure | Invisibility — loses political backing before it compounds | Orphaned pilot — nobody owns it after the funding ends |
| Atlas examples | Offenbach permits, Boti, Bad Nauheim | U-Space Berlin, Harumi Flag, Masdar |
Helsinki, live: what outlived the showcase
Which brings the question back to where it started — and the honest reading of Helsinki is not that the showcase failed and the boring thing won. Whim did what showcases do: it made a small northern capital the reference case for an entire category of transport policy, and it proved the model worked well enough for others to copy. What it could not do was survive on its own economics once the attention moved on; MaaS Global filed for bankruptcy in March 2024, and the buyer did not bring the service back to Helsinki.
The journey-planner interface did the opposite in every respect. It launched with no fanfare in 2009, was never a product, and grew from a handful of registered developers into the open-source platform now running in Estonia, several German cities and Oklahoma City. Nobody was ever going to fly to Finland to look at an API. Fifteen years later it is the piece still doing work for residents every morning — and, unlike the app, it is the piece other cities could actually take home. That is the pattern in miniature: the showcase bought the attention, and the use case kept the value.
So: showcase or use case?
The honest answer from the evidence is that they are not competitors — they run on different clocks and fail in different ways. Showcases are how a city buys its future options: attention, funding, partners, and proof that something works at all. Use cases are how a city pays its present debts: services that quietly compound. The failure mode is symmetry-breaking — all showcase and you collect orphaned pilots (the sandbox that stays a sandbox); all use case and you may never attract the money, talent or political spark that makes the next leap fundable.
If a single test cuts through it, it is the one this atlas applies to every entry it verifies: who operates it in year five? A showcase with a year-five answer is an investment. One without is an event. A companion pillar pushes the same scepticism onto the data itself: your city's problem map is really a map of who complains, not of what is broken.
Frequently asked
What is the difference between a showcase and a use case?
A use case solves an existing everyday problem — typically digitising an analog process, like residence permits. A showcase demonstrates a new possibility — autonomous shuttles, drone delivery, hydrogen districts. Use cases are judged by daily value; showcases by what they attract and teach.
What is "pilotitis"?
The pattern of pilots that never become permanent. Research (Van Winden & van den Buuse 2017; Nature HSSC 2021) shows scaling needs different people, funding and governance than piloting — and Germany's federal evaluation names exactly this transfer as the model programme's weak spot.
Why build showcases at all?
They buy visibility, external funding, talent and structured learning — and sometimes convert into infrastructure, like London's charge cameras becoming the ULEZ backbone. Munich's EU lighthouse status paid for buildings, mobility stations and a data platform that outlasted the funding.
What happened to Helsinki's Whim?
Whim, widely credited as the world's first commercial mobility-as-a-service app, was discontinued when its operator MaaS Global filed for bankruptcy in March 2024; the acquirer has not relaunched it in Helsinki. The city's much older open journey-planner interface, opened to developers in 2009–10, is still running — and became the open-source Digitransit platform now used well beyond Finland.
Projects mentioned
Sources
19 checkable claims in this essay are annotated — select any dotted-underlined passage to see exactly what its source says. The evidence links were prepared with AI and are not yet individually verified — follow the sources.
- Whim-maker MaaS Global files for bankruptcy open source ↗ archived copy
- 10 years of open data in Helsinki metropolitan area open source ↗ archived copy
- Case Study of Digitransit open source ↗
- HSL Open Transit Data & the Digitransit Platform — atlas entry open source ↗
- Smart City Pilot Projects: Exploring the Dimensions and Conditions of Scaling Up open source ↗ archived copy
- Smart city pilots: scaling up or fading out? open source ↗ archived copy
- Pilot project purgatory? Assessing automated vehicle pilot projects in U.S. cities open source ↗ archived copy
- Rund 15 Modellprojekte für autonome Shuttles in Deutschland open source ↗ archived copy
- Liste autonome Shuttle-Bus-Projekte open source ↗
- VDV: Deutschland als Leitmarkt für autonomes Fahren open source ↗ archived copy
- Von der innovativen Idee in den Regelbetrieb (BBSR-Sonderveröffentlichung zur Verstetigung von Smart-City-Maßnahmen) open source ↗ archived copy
- Modellprojekte Smart Cities — über uns open source ↗ archived copy
- Smart Cities — Modellprojekte (programme page) open source ↗
- SCC1 Projects (lighthouse project family) open source ↗ archived copy
- Smart Cities Community open source ↗ archived copy
- Smarter Together — site Munich open source ↗ archived copy
- Smarter Together — Landeshauptstadt München open source ↗ archived copy
- X-Road — interoperability services open source ↗ archived copy
- Facts and figures open source ↗ archived copy
- Pilotprojekt zum Einsatz von KI bei Ausländerbehörden gestartet open source ↗
- KI für Ausländerbehörden open source ↗ archived copy
- „Aufenthalt Digital“ kommt mit KI ab sofort bundesweit zum Einsatz open source ↗
- umob acquires MaaS Global, Finnish creator of mobility app Whim open source ↗ archived copy
- Central London Congestion Charging Scheme — atlas entry open source ↗
- Ultra Low Emission Zone (ULEZ) — atlas entry open source ↗
- Whim (Mobility-as-a-Service) — atlas entry open source ↗
