Three actions. One starting point.
The setup checklist brings language, location, and on-bus confirmation together. Focused subpages carry the detail, while the main screen keeps readiness visible.
CASE STUDY 01 / ARnocular
A new perspective.
A real product business.
Connecting immersive guest experiences with tour operators’ commercial and operational needs—from discovery and pilots to international commercialization and product growth.
Role
Founder & Product Lead
Founding phase
Nov 2015 – Aug 2021
Growth & scale
Nov 2023 – Present
01 / THE CHALLENGETwo customers.
Two customers.
One experience.
A rider needs a compelling, understandable experience. A tour operator needs something that works within a live tour business and has a clear commercial purpose.
I led discovery with both operators and riders to inform pilots, feature priorities, buyer education, and commercialization. The product roadmap had to connect those two perspectives.
02 / MY CONTRIBUTIONFrom discovery
From discovery
to a live market.
I owned product strategy, roadmap, MVP scope, pricing, and commercialization. Early customer relationships and tour-operator partnerships helped establish market presence.
- Created operator-specific pilot packages, multilingual launch materials, and buyer education.
- Commercialized in Seattle, Prague, Frankfurt, Berlin, and other markets.
- Led more than 30 multidisciplinary professionals across product, development, design, finance, and business development—not 30 direct reports.
- Coordinated Unity-based Android and iOS releases, QA, release notes, app-store setup, and operator readiness.
EXPLANATORY RECONSTRUCTION / THE ACTIVATION JOURNEY
01
→Encounter the experience
The rider discovers XR content on the tour.
02
→Understand what to do
Scanning instructions and activation prompts guide setup.
03
Explore and respond
In-app education and feedback capture support the experience.
Illustrative journey based on the written account. Not an original product screen or historical design artifact.
03 / GROWTH & ADOPTIONMake the first
Make the first
experience easier.
In the growth phase, I redesigned marker-scanning instructions, activation prompts, in-app education, and feedback capture to reduce setup friction.
I also built measurement covering satisfaction, channel attribution, usage trends, and customer ROI, connecting field observations to product and release priorities.
20% → 75%Adoption, from initial launchBefore → After
25% → 70%ActivationBefore → After
3 → 20 minAverage engagementBefore → After
Reported before/after outcomes. Measurement dates, denominators, cohorts, and session definitions have not been supplied. These measures are not presented as a single funnel or controlled experiment.
ONBOARDING TO PLAYBACK
A clearer way
to start.
One checklist, focused setup screens,
then the story. Open any screen to inspect it.
View full screen ↗One clear starting point
Language, location and bus confirmation in one checklist.
View full screen ↗Explain the permission
A short explanation before the location request, with details available on demand.
View full screen ↗Confirm the context
One explicit on-board confirmation, with a clear Not yet option.
View full screen ↗Move into the story
Story imagery, playback status and route context after setup.
Real Pixel 6a captures · Frankfurt v85/build118 QA validation · October 2026. Route playback uses a test simulation. Screens show the app interface; embedded content imagery is separate from interface design. This sequence demonstrates the experience, not a production-release certification or a measured conversion improvement.
PRODUCT JUDGMENT / WORKING WITH UI & UX
Make the next step
obvious.
Recent design and device evidence adds
detail to the broader product-growth story.
Explain enough, where it matters.
The main checklist uses the short helper “Internet needed.” The language page carries the fuller download explanation. The intention is to keep the hub scannable without hiding a requirement.
Make readiness explicit.
Incomplete requirements keep Start tour disabled. Once the setup is ready, one clear action leads into the tour.
Supported by the project’s UI/UX handoff, copy amendment, and native captures reviewed with the UI/UX workstream. These recent iterations are not attributed as the cause of the historical growth metrics. The gallery uses one Frankfurt Android QA sequence.
LET’S CONNECT
A good product starts
with a conversation.
Product leadership, AI workflows,
and ambitious startup opportunities.