Anchor supports people with anxiety disorders and panic attacks through the often lengthy wait for therapy – a time when many feel lost and alone.
With personalized exercises, a mood-tracking tool, and expert-backed insights, the app helps users better understand their anxiety, actively build mental resilience, and track their progress. By providing structure and support, Anchor makes the waiting period a meaningful first step and ensures a smoother transition into therapy.
Responsibilities
User research, qualitative interviews, user journey mapping, wireframes, UI design, prototyping and interaction design
Team
Tianxiong Zhong
A gap nobody was designing for
Anxiety disorders among young adults surged by 26% post-pandemic, and in Germany mental-health-related sick leave climbed from 8% in 2019 to 12% in 2021. Despite over 50% of Gen-Z naming anxiety as a top concern, average wait times for psychotherapy often exceed three months – leaving many to manage panic attacks, sleep loss, and social isolation alone. This untreated gap worsens symptoms and increases the risk of long-term impairment.
Nine conversations that needed care
We conducted nine in-depth interviews with people who experience anxiety or panic attacks, plus one with a licensed psychotherapist. Recruiting participants for intimate, emotionally charged conversations required extreme sensitivity: we built trust through active listening, clear consent, and empathetic prompts. These sessions revealed not only pain points around self-management and stigma, but also the gap in support during therapy wait times.
Mapping two patient journeys
To make sense of our qualitative data, we mapped two patient journeys – one high-level and one detailed – to visualize emotional states, triggers, and touchpoints over time. We then grouped insights thematically to uncover design opportunities. This methodical synthesis helped us identify where users felt most lost, where they needed education versus immediate relief, and where small interventions could boost resilience.
Designing for the waiting period
Instead of repeating existing in-therapy app features, we focused on the unaddressed pre-therapy waiting period. By overlaying our patient journey with stakeholder inputs, we spotted a unique opportunity: create an accessible, structured support system to guide users from crisis toward treatment. Anchoring our strategy on this gap let us craft a service that becomes the meaningful first step in mental-health care.
Three phases, three sets of questions
We framed three journey phases – Beginning/Realization, Struggles, and Seeking Help for Therapy – and for each defined How-Might-We questions to spark targeted solutions. For example, "How might we offer immediate calming exercises without overwhelming new users?" and "How might we track progress so users see their own growth?" This led to a suite of features, from empathetic journaling to challenge-based exercises, that directly map back to our insights.
A conversational diary at its centre
The conversational AI-powered diary is our signature feature: rather than static text fields, users talk through their experiences in a supportive chat interface. Empathetic prompts encourage openness and reflection, while natural language processing tailors follow-up questions. This human-centred approach lowers the barrier to self-disclosure and creates richer data for both users and their future therapists.
More features
Therapy Readiness Report
Automatically generated summaries of mood trends and skill-practice history, reducing therapist onboarding time and lowering healthcare costs.
Interactive Challenges
Bite-sized, CBT-inspired tasks – like guided exposure or positive-reinforcement exercises – to build coping habits.
Psychoeducation Modules
Engaging, gamified lessons on anxiety and panic mechanics, designed to demystify symptoms and destigmatize self-care.
Breathing & Relaxation Tools
Quick-access exercises for acute relief, visually tied to our storm-and-sail metaphor for intuitive feedback.
2025Design sprintProductHealth
Orbis turns complex hormone data into clear, personalized guidance that empowers users on their path to hormonal balance and self-discovery.
By seamlessly combining insights from the ORBIS device with other health platforms, the companion app offers a complete, holistic view of both physical and emotional well-being.
Through intuitive goal-setting, tailored recommendations, and smart data interpretation, the app transforms passive tracking into active self-improvement, making health feel approachable, motivating, and truly personal.
Responsibilities
Solo project – research, concept development and user experience design
Context
4-day design sprint at FLUID Design to create a companion app
The Orbis Hormone Analyzer by FLUID is a sleek, at-home health device that empowers users to monitor hormone levels through painless blood and saliva sampling. Designed with a minimalist aesthetic, it integrates seamlessly into daily life, transforming clinical testing into a sophisticated, consumer-friendly experience.
This approach reflects a broader shift in healthcare – from reactive, provider-centric models to proactive, user-centered care – where wellness is integrated into lifestyle through intuitive, high-quality technology.
An app that had to earn its place
FLUID created the device as a future medical design vision, and my task was to design the companion app around it. The real challenge was making sure the app actually added value: the device already carries a screen that can display plenty of information, so anything I designed risked being redundant.
With four days to go from brief to presentation, I planned the sprint myself – mapping each day from understanding and research through ideation, design and the final handover.
Behavioral design x AI
Research revealed that users are often overwhelmed by raw data and quickly lose motivation when faced with only graphs and numbers. To address this, I explored behavioral design principles to understand what truly drives and engages users in their health journeys.
Additionally, I investigated how AI could enrich the experience – transforming complex data into meaningful, personalized insights that inspire sustained motivation and proactive self-care.
The three user archetypes
The Curious
Tracks out of interest – wants to understand her cycle and stay in balance.
The Performer
Optimises training, sleep and recovery – wants data that moves the needle.
The Patient
Strong hormonal fluctuations – needs actionable advice, early warnings and reassurance.
The three layer structure
To keep the app from overwhelming users, information unfolds across three layers – from a single glance to a full deep dive.
Lead with meaning, not measurements
Research was clear: raw numbers left users asking “okay, but what do I do now?”. So the home screen leads with a plain-language read and a next action – the data sits one layer deeper.
Option A · Data first
Four values and graphs up front – precise, but it leaves the reading to the user.
Option B · Meaning first – chosen
One clear interpretation and a concrete next step; the data sits a layer below.
First layer
Users understand their current status at a single glance.
Second layer
A more detailed overview of all health parameters and tracked hormones.
Third layer
A deep dive into each hormone, with a suggested action to improve its current state.
The companion app
The ORBIS companion app enhances the holistic user experience by seamlessly integrating hormone data with insights from other health platforms. It transforms complex information into personalized, AI-powered guidance and actionable goals – empowering users to actively manage their well-being beyond the physical device.
This app completes the ORBIS ecosystem, making hormone health approachable, motivating, and truly connected.
A central health overview
Orbis connects to the health apps users already use, so sleep, activity and nutrition sit next to their hormone levels.
The app adapts to your goal
Users set one personal goal, and the whole app tailors its insights and actions around it.
Connect Orbis with the doctors you trust
2026Side projectShipped
Vaelo started from a personal problem: there was no meaningful way to guide 1:1 sessions with my manager or track the goals we set together, so I built one.
Vaelo is one private page for a manager and their report. Both add to it during the week: what to talk about, how they're arriving, the goals in focus and what they promised each other. The 1:1 then starts with what actually matters.
I built version 1.0 for my own 1:1s during my internship and redesigned it from the ground up three months later.
Role
Concept, product design and build, with help from Claude
Timeline
1.0 in July 2026, redesign in October 2026
Team
Just me
Tools
VS Code with Claude, GitHub
Months in use
2.5
1:1s run in Vaelo
7
Goal milestones reached
8
How 1:1s actually happened
Before designing anything, I looked at how 1:1s actually happened: an official performance tool used top-down across the company, and a Mural board I'd set up with my manager to make our check-ins work.
The official tool was the one people kept describing as cold and corporate. The Mural board fixed some of that, but week after week it grew into a sprawl of stickies, making it hard to look back and track where a goal actually stood.
Imposed tools and forgotten goals
Talking to colleagues about their own 1:1s confirmed it wasn't just dissatisfaction with features. The current tool felt imposed, and its corporate tone created distance instead of trust.
The conversations also surfaced two deeper gaps: nobody felt supported through the full goal journey, from figuring out a goal to setting it and following through, and once set, goals quickly faded from memory instead of staying visible.
Trust
Feels cold, not personal
The tool feels imposed. Its corporate tone creates distance rather than trust.
Journey
No support for the whole goal journey
Figuring out a goal, setting it clearly and working toward it: none of it is supported well.
Memory
Goals don't stick
Once set, goals fade from memory instead of staying visible.
Why I redesigned it
Version 1.0 worked, and we used it every week. But it had no system and no component logic, elements sat out of line or broke, there were bugs, and I wasn't happy with the visual direction. It lacked craft, so I rebuilt it from the ground up.
1.0, JulyThe redesign, October
How I worked with AI
I designed and built Vaelo myself, in VS Code with the help of Claude. Everything happened in code: Figma only came out to try a detail quickly, and GitHub kept every step.
The problem, the concept, the features, the flows, the visual direction, usability and strategy were mine. Claude helped me write the code fast. My part was to give direction, challenge and refine, bring in ideas, think the product through as a whole, and remove things, then remove more.
01I designConcept, flows, look
02I build with ClaudeIn VS Code
03I testIn the playground
04I cut and refineThen ship via GitHub
Testing in a playground
To test without real accounts, I built a playground: the real app against a fake backend in the browser, with the real database rules. I could seed a whole team, open several people at once, read sign-in codes from a fake inbox and switch between scenarios and roles.
Seeding a team, then signing in as Jo with the code from the inboxEvery state one click away: things slipping, a 1:1 that's ready to close, a brand-new workspace
Check-in
Before each 1:1 you both pick a mood and can add a line. It's optional, asked with consent, and can be turned off and deleted in Settings.
Shared agenda
Topics, questions and feedback, written by both. What one person adds shows up for the other right away.
Closing a 1:1
Closing the week takes a minute: tick what moved, name one thing that went well, and the next 1:1 is already set.
Goals
Goals are broken into proof points. When progress looks good but confidence doesn't, Vaelo flags the goal and suggests putting it on the agenda.
To-dos
What you promised each other, in three columns: Backlog, In progress and Done.
History
Every closed 1:1 is kept with its win, what came up and how you both arrived, so the weeks add up to a trend.
Onboarding and People
One person sets it up: pick your side, invite the other, choose a rhythm. A manager with several reports gets one private space per pair, and the reports never see each other.
Details
A code instead of a link, because company mail scanners open links before people doEmpty states that say what to do nextThe same page on a phoneThe cloud keeps you company while things load
Landing page
I prototyped many versions and compared three directions side by side, then cherry-picked the sections that show the tool best.
I went with the clouds. Vaelo should feel worry-free and never like a burden: light and free, like air. Visually it was also my favourite.
We used Vaelo for the rest of my internship: two and a half months and seven 1:1s, in which I reached eight goal milestones. My manager will keep using it with the next intern, and I now use it in my new job.
01
Design in the real material
Working in code meant testing real flows, sign-in emails included, not pictures of them.
02
Judgement is the job
With Claude helping me build, most of my time went into deciding what stays and what goes.
03
Craft needs a system
The redesign started with components and rules, not screens.
This was a confidential project, so the designs and some terms are anonymised. All names and data are recreated, and the assistant has a new name.
2026Conversational AIProduct DesignConfidential
AI Store Assistant is a voice assistant for one of Europe's biggest supermarket chains. It spots problems in the store and hands out tasks, so store teams can stay with their customers. At frog, I designed the companion app for store managers and how it works together with the voice.
The chain already uses a voice assistant in its pilot stores, but it only answers questions and never speaks first. The next step was an assistant that notices problems on its own and tells the right person what to do. Store managers would get a handheld app to go with the voice, and designing that app was my part.
The project is meant to be built and rolled out to the stores. I was part of it for its first four weeks, until my internship ended. In that time I designed the app’s structure and how it works together with the voice, and built it as a working prototype. It helped convince the stakeholders of the full vision, and its structure lets a first release run on the data the stores already have.
Role
Product Designer at frog
Responsibilities
Workshop preparation, information architecture, interaction and visual design, prototyping
Team
Danai Moschona (stream lead, frog), a PM and developers from Capgemini
Timeframe
4 weeks, August to September 2026
At 09:15, three systems want the manager’s attention at once
Fridge sensor
Fridge 3 has been warming for 52 minutes.
Recall system
Recall: organic yoghurt, batches 0412 to 0418.
Staff plan
Tom called in sick. Till 2 is uncovered.
Each of these alerts matters on its own. Heard together on one headset, they turn into noise, and a spoken message is gone after a few seconds, so there is nothing to look back at.
How do you design a screen for an assistant that mostly speaks, without simply repeating what the voice says?
Store staff usually have their hands full and their eyes on the shelf, so voice stays the default way to use Mira. The screen only carries what voice can’t hold: things to come back to later, long lists, charts, an overview of who is where, and options to compare side by side.
A note to come back to
A long list of tasks
A chart in the chat
Who works where
Options side by side
What the store journeys showed
Store-operations stakeholders from Germany and the US, who know the store staff well, wrote down real situations from their stores as short journeys. In the workshop I prepared, three of their notes shaped the design directly.
“Whoever logs it first gets it, even if not the right person.”
So every alert gets one owner, suggested by Mira and confirmed by the manager.
“Too many alerts. Several overnight events: what order?”
So safety comes first, and related updates arrive together as one message.
“Temperature graph needed. The manager should see it on the handheld.”
So the screen carries the evidence that voice can’t, like a temperature trend.
Quotes from the participants’ notes on the journey boards.
The workshop changed who the screen is for
Before the workshop I had designed the app for everyone in the store, with one view for managers and one for staff. Working through the journeys showed that the staff view was just the manager’s view with fewer features, and the stakeholders decided to focus the screen on store managers. So I dropped the staff screens. Staff stay on the headset, and the manager sees their work on the screen.
Lena K., on her headset
On it, heading to Fridge 3.
Lena takes the task by voice. The manager sees it at the top of her plan.
Four tabs and an Ask bar
The first structure had five sections, which didn’t match where managers look for things. After sorting every feature, four tabs held them better: Log, Tasks, Assets and Tickets. They sit at the top, so the bottom of the screen belongs to the Ask bar. Without a home dashboard everything is one tap further away, but a clear structure was worth that trade-off.
How I chose where the tabs go
I worked on the navigation and the information architecture side by side. I collected navigation patterns on Mobbin and had Claude Code build each one into the real screens, so I could judge them in context instead of as sketches. I looked for the one that needs the fewest taps between pages and keeps every page clean and uncluttered.
Tabs under the Ask bar
Two rounded bars stacked on top of each other looked odd, and they sat so close that a tap could easily land on the wrong one.
Tabs at the top
One tap between pages, and the bottom belongs to the Ask bar alone, the way to talk to Mira.
Ask, note or task
My first idea was one input where Mira works out whether you asked a question, took a note or created a task. The model couldn’t tell these apart reliably yet, and a misfiled note simply disappears. So you say what you want, and the Log stays organised.
A small set of cards instead of free layouts
Rather than letting Mira generate any layout, I designed a small set of cards for the most important cases. The situation and the data decide which card she shows. When she can’t vouch for a number, the card says so with a quiet flag.
Temperature, with missing readings flaggedStock, with an uncertain figure flaggedA procedure as a checklist to tick offAn illustration of what to look for
The full vision, and a first release on today’s data
The data for tasks and the team plan isn’t available yet. The prototype shows the full vision, which we needed to win the stakeholders over, and I built the structure to work without the Tasks tab, so the first release runs on Log, Assets and Tickets.
[ Information architecture ]
Mira
Log
Conversation
Notes
Voice tasks
History
Tasks
Alerts
Workforce
Open tasks
Completed
Assets
Shelf labels
Reports
Report a fault
IT support
Tickets
Open
Closed
Ask bar on every page
AI can be wrong, so the design plans for it
Mira can notify, log and draft on her own. Anything that assigns people, changes the plan or touches money, safety or compliance needs a person’s yes.
Mira suggests, and explains why
When Tom calls in sick, Mira proposes the colleague whose work can pause and explains why. The manager can still pick someone else.
People make the call
For a product recall, Mira proposes who should take it, but the manager decides.
People confirm what Mira can’t see
Mira can’t see the shelf, so she turns the recall procedure into a checklist, and Marco ticks it off once the products are gone.
Proof instead of a confirmation
A message like “Added to the agenda” proves nothing. So Mira shows the result itself, and the manager can see that it worked without opening anything.
Designed in code, so the timing could be judged
Most open questions were about timing: when Mira speaks, and what moves on screen while she does. Static screens can’t answer that, so I designed the product as a working prototype, with a playground that runs every flow step by step.
Claude Code did the building, and I directed it. I gave it the store rules, the briefing and the data we had as context, and my design rules and references as direction. When I wanted to try out a small detail myself, or show Claude Code exactly what I meant, I built a quick version in Figma first. Then I used every change in the playground, at the pace of the voice, and gave feedback the way I would in a design review, round after round, until the flow felt right.
The conversation got its own place
One of those rounds changed where the conversation lives. In the first version, talking to Mira opened it in a drawer over the page. The drawer covered the tabs, so tapping anywhere else only closed it, and once it was closed there was no way back. But managers often need to check the plan in the middle of a conversation and then carry on.
A drawer works when you keep an eye on what’s behind it. Here the conversation is what you come back to, so it became its own tab in the Log. The manager can leave it, look something up and return to the same place.
Before
Tapping a tab closes the drawer, and the conversation is gone.
After
The conversation waits in the Log, right where the manager left it.
09:15 again
With the new design, the same morning sounds different. One voice speaks, the most urgent problem comes first, and the right person takes it.
Where I left it
My part ended after four weeks, while the project kept going. I handed over the working prototype of the vision, a structure the first release can be built on, and the playground the team kept using. Nothing has launched or been tested with store staff yet.
01
The screen has to earn its place
With voice as the default, the screen should only show what voice can’t, like lists, plans and charts.
02
Design for the data that exists
A vision helps sell the idea, but the structure has to work with the systems a store has today.
03
Timing is part of the experience
Only a running prototype could show when Mira should speak.
Designed at frog, part of Capgemini Invent, with Danai Moschona as stream lead and Capgemini as programme partner. All visuals, names and data are recreated.
This work is confidential. Everything below stays deliberately high level – no unreleased features, screens or numbers. What I can share is the shape of the work and what I took away from it.
2025 – 26InternshipConfidential
At BMW Group I shipped two products as the sole designer and designed interior UX concepts for millions of drivers, looking as far ahead as 2030.
Six months as a product design intern at BMW Group in Munich, split across two departments at opposite ends of the car. In interior UX, I designed screens and interaction concepts for current and future vehicle software, up to 2030. In vehicle software testing, I was the only designer: I shipped an internal app to the BMW Marketplace and a division-wide dashboard, turning unclear, highly technical requirements into clear, easy-to-use interfaces together with engineers and product owners.
Both sit inside unreleased product work, so the specifics stay confidential. What follows is the shape of the work and how I approached it.
Responsibilities
Interior UX concepts, screen and interaction design, product design for an internal app and a division-wide dashboard, design workshops, alignment with designers, developers and product owners
Timeframe
October 2025 – March 2026, Munich
Based at BMW's research and innovation centre
Both departments sit in the FIZ, BMW's research and innovation centre in Munich – the place where the company's future vehicles are developed. Working there meant being surrounded by the engineering side of the product every day, which shaped how design decisions had to be argued and handed over.
Screens for the inside of the car
The first department owns everything about the in-car user experience – all the interfaces in the interior of the vehicle. I worked on a lot of different screen concepts and screens, both for the main infotainment system and for the Panoramic iDrive, building interaction concepts for current and future vehicle software.
My focus was the Panoramic iDrive. I worked in a small team trying to enhance its user experience by giving it more intelligence, working on new AI features for it. I can't go into more detail than that.
Most of the work happened across teams: participating in design workshops, and aligning constantly with both developers and other designers.
Sole designer in a deeply technical team
The second department is responsible for vehicle software testing – still a design role, but sitting inside a very technical software development organisation. I was the only designer there, which meant translating unclear, highly technical requirements into something clear and easy to use, in close collaboration with engineers and product owners.
The app I designed from zero to one is live in the BMW Marketplace
I designed it as the sole designer and shipped it together with my product managers and one developer.
The app is built for test drivers and software engineers who track street unevenness and speed signs to improve their machine learning models. They use it to validate unevenness or speed limits the car detected by itself, and they can also record unevenness or speed limits themselves and add those straight into the model's database.
The hard part was the flow. It had to be usable while driving, so the whole design was about efficiency: as fast as possible, as easy to understand as possible, with as few clicks as possible.
The second project was a software testing dashboard. Again as the sole designer, this time in a team of around fifteen people – a project lead, project managers, software developers and testing experts. We worked in an agile product development process, shipping features of the dashboard continuously.
What I took away
01
Design inside a very large company
How design systems are structured, how decisions get made, and that it is always about getting the approval of people further up.
02
Being the only designer in the room
How to work as the sole designer – where part of the job is proving to everyone else what design is worth, especially in the era of AI.
03
Translating complexity into something usable
How to turn genuinely complex topics, like car software testing flows, into interfaces that are easy to use and easy to understand.
Adaptive Park Lighting prevents light pollution to protect nocturnal ecosystems, responding only to human presence – minimal disruption to wildlife, a safe experience for people.
With a focus on sustainability and respect for nature, this project aims to prevent light pollution in order to protect nocturnal ecosystems. Through the use of adaptive lighting technology, this system responds only to human presence, ensuring minimal disruption to wildlife while ensuring a safe experience for humans.
In addition, an explanatory website helps visitors to find out more information about the project and learn about the animals in this park.
Responsibilities
Research, concept development, industrial design and web design
Exhibited
Munich Creative Business Week 2024 – “How to Co-Create with Nature”
A problem growing 6% every year
Every year millions of birds get injured or die by colliding with buildings and towers due to bright city lights during migration. Many insects are attracted to the light and are completely trapped flying around the light source until they die. Additionally, excessive lighting near water disrupts aquatic ecosystems, affecting species interactions and biodiversity.
These and many more are causes of light pollution for animals, our environment and also for us humans. As if that weren't enough, light pollution is even increasing by 6% every year in Europe. In my project, I have dedicated myself to exactly this problem.
What the Hirschgarten gets wrong today
I chose the Hirschgarten in Munich as the location to apply my concept there as an example. First, I analyzed the entire park and looked at the current lighting there. Although the light from the streetlights cannot shine upwards, it still shines too far outwards, causing unnecessary light pollution.
Besides that, the street lights are lit all night long. In addition, some smaller paths are illuminated that do not necessarily need to be illuminated.
A park that stays dark until you walk through it
I next looked at what animals live in the park and which ones are particularly affected by light pollution. Amongst several animal species, I then decided on a very light-sensitive bat species, as this represents many of the problems of nocturnal animals very well.
As bats move by flying, this light system is located on the ground to reduce the light in the air. Because bats are very much disturbed by artificial light, this park is permanently dark in its normal state, and the lights only go on when there is human movement. The lights go on as the person is walking through the park and guide them through while ensuring a safe experience for them.
The light color of the lights is also very warm at 1800K, which has a positive effect on insects and is less harmful to them.
Explaining the concept on site
I also designed a website for my project, which can be accessed via QR codes on signs at the park entrances. On this website, users can find information about the park concept, how exactly the lighting works and what advantages it has over the current lighting. I wanted to prevent park visitors from feeling lost and confused about the new parking concept.
The website also provides information about light pollution and its negative effects on nature, animals and us humans. Users can also find information on the website about the animals living in the park, their needs and problems.
2024ResearchAccessibility
EasyBrew is a screen concept for an accessible coffee machine. From voice-control to increased contrast, depending on the type of disability, the machine offers different modes to fulfill the needs of the user.
EasyBrew is a screen concept for an accessible coffee machine. From voice-control to increased contrast, depending on the type of disability, the coffee machine offers different modes to fulfill the needs of the user.
Responsibilities
Market analysis, user interviews, usability testing and UI design
Our task for this project was to design a screen for a coffee machine. We initiated the process by a market analysis of coffee machines and their screens.
Following this, we engaged in insightful interviews with users from diverse fields like the office, gastronomy and private home, gaining valuable insights into their experiences with various screen interfaces.
A market that overlooks barrier-free operation
In our research, we recognized the oversaturation in the coffee machine market, with only subtle distinctions among many.
Surprisingly, we observed a widespread neglect of barrier-free operation in all coffee machines. To address this oversight, we undertook a series of interviews with individuals facing physical and mental disabilities, aiming to directly understand their unique experiences and requirements.
Testing with the people we designed for
Due to our briefing, we were very limited in the design of the screen, but I learned to find the most suitable solution even under strict specifications.
To ensure the best user experience for our specific audience, we meticulously tested all prototypes with individuals facing physical and mental impairments. Their valuable feedback played a key role in refining our designs.
The final interface
The result is a screen that adapts to the person in front of it – switching modes for voice control, increased contrast and simplified flows depending on the needs of the user.
2024ProductTravel
Schleasy is an app that helps tourists plan their perfect trip in just a few minutes, bringing every step from choosing a destination to booking a hotel together in one place.
Schleasy is an app that helps tourists plan their perfect trip in just a few minutes. With this app, we wanted to solve the problem of users spending a lot of time planning and researching for their trip. Schleasy brings every step from choosing a destination to booking a hotel together in one app.
This project was part of a cooperation project with the Thomas & Yvonne Wilde Family Foundation and Kulturerbe Bayern.
The municipality of Schleching reached out to us, expressing concerns about a decline in tourism and a desire for fresh, sustainable ideas. Our analysis involved an in-depth study of tourism offerings, statistical insights, and the unique geographical features that define Schleching.
To truly understand the community, we spent several days on-site, immersing ourselves in the local environment. We engaged in insightful interviews with both locals and tourists, gaining valuable perspectives that would lay the foundation for our solutions.
Five problems in the way of a good trip
Information dispersed across multiple platforms: users faced the inconvenience of scouring various websites for information.
Time-consuming trip planning: the process of organizing trips, excursions, and related activities proved to be very time-consuming.
Overlooked events and destinations: users often missed out on events or excursion destinations.
Confusing route apps: existing route apps were found to be confusing for users, causing potential navigation difficulties.
Limited awareness of Schleching. These insights laid the groundwork for our strategic interventions to address and overcome these challenges.
Five questions instead of hours of research
Schleasy is designed with simplicity and practicality in mind. Using a minimalistic approach, it leverages AI to craft personalized travel plans through just five straightforward questions, eliminating the need for extensive research and planning. In just a matter of minutes, users receive a tailored itinerary, freeing them from the hassles of manual trip coordination.
In addition to its core functionality, the app includes features such as a map, news updates, helpful tips, and real-time weather information to enhance the overall travel experience. We take pride in our commitment to sustainable tourism by prioritizing eco-friendly transportation options like trains and buses.
In a world where time is a luxury, our app gently nudges users to explore nature like in Schleching despite their busy schedules. It's a tool that encourages a connection with nature, providing a refreshing break from the demands of daily life.
The planner and its features
The planner sits at the heart of the app, with the map, news, tips and weather supporting it around the edges.
Coming soon
Imprint
Fabio Burmann Lothstraße 17 80335 Munich Germany
fabio.burmann@gmail.com
Responsible for the content of this site under § 18 Abs. 2 MStV: Fabio Burmann, at the address above.
This is a personal portfolio. All project work is shown with permission of the respective clients or as personal, unaffiliated work.
Privacy policy
This site uses Google Analytics (Google Analytics 4, by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland) to see how many people visit and which pages they read.
Google Analytics sets cookies in your browser and receives the pages you view, the time, your approximate location, your browser, operating system and device type, and a pseudonymous identifier. IP addresses are not logged or stored by Google Analytics 4. The data may be processed by Google in the United States under the EU–U.S. Data Privacy Framework.
You can switch Analytics off with Google’s browser add-on or by blocking cookies and trackers in your browser.
Apart from Analytics, every page, image and font is served from this site itself, so simply reading it sends no request to Google or any other third party.
Hosting is provided by Vercel Inc., 440 N Barranca Avenue #4133, Covina, CA 91723, USA. Like any web server, Vercel writes a short technical log of each request – your IP address, the time, the file requested, and your browser and operating system. Those logs exist only to deliver the site and keep it available and secure, which is my legitimate interest under Art. 6 (1) (f) GDPR. They are not combined with anything else and I do not use them to identify you.
Because Vercel is based in the United States, those logs may be processed outside the EU. Vercel is certified under the EU–U.S. Data Privacy Framework, and the processing is additionally governed by a data-processing agreement under Art. 28 GDPR that incorporates the European Commission’s standard contractual clauses. Details are in Vercel’s privacy policy.
If you email me, your message and address are used only to reply and are never passed on.
You can ask me at any time what data relates to you and request that it be corrected or deleted, and you may complain to a supervisory authority. For anything on this page, write to fabio.burmann@gmail.com.
My work is driven by the desire to create meaningful digital products. In an era increasingly defined by AI, I believe our role as designers is more critical than ever: technology has to serve a purpose and be intentionally designed for the good. I bridge the gap between human behaviour and complex systems, so every interaction – physical or digital – stays human-centred and intentional.
Japanese culture inspires that stance: their design philosophy, their minimalism, their approach to everyday life. Away from the screen I shoot analog film, windsurf across the Bavarian lakes and hike somewhere in the Alps.
