Arteria: from the map to a service
I lead design for a high-precision positioning service: the map, client flows and development handoff. These stories explain interface decisions and how the team works.
Demonstration reconstruction. Original designs and data are under NDA. These interactive examples were made for the portfolio: layouts, names, values and diagrams have been changed. They explain the decisions without reproducing the product.
My role
In a small team, I lead design and work through requirements with the product manager. My scope includes the landing page, coverage map and client services. I clarify flows, describe states and prepare materials the team uses to discuss implementation. The product is evolving. These stories describe design work; they do not imply that every feature has shipped or that improvements have been measured.
Decisions and examples
The map: find a station, then use a service
I separated station status, zones and service access, and designed search, connection parameters and data requests with explicit error and retry paths.
Design Hub: from a scenario to a development task
I built a local tool linking user stories, design work and team questions. Changes made after a manual Jira transfer are flagged separately.
Local components and layout checks
I used AI to assemble components and find discrepancies. I made structure and correction decisions in the context of the product.
A map prototype: search and panel in action
I build demonstrations from layouts so the team can walk through a complete flow, from opening the map to selecting a station.
Explain the network through a slide sequence
For an exhibition presentation, I structured a story about the network and an additional V-RS layer, paying particular attention to what the map claims.