<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mathis on Medium]]></title>
        <description><![CDATA[Stories by Mathis on Medium]]></description>
        <link>https://medium.com/@mathishanspach?source=rss-e8881e264dd0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fqKB135_dpXHhWe7IxyoTA.jpeg</url>
            <title>Stories by Mathis on Medium</title>
            <link>https://medium.com/@mathishanspach?source=rss-e8881e264dd0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:04:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mathishanspach/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[UX/UI — Mobile Game Redesign]]></title>
            <link>https://medium.com/@mathishanspach/ux-ui-mobile-game-redesign-2f3891956a99?source=rss-e8881e264dd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f3891956a99</guid>
            <dc:creator><![CDATA[Mathis]]></dc:creator>
            <pubDate>Tue, 17 Mar 2026 11:23:57 GMT</pubDate>
            <atom:updated>2026-04-22T07:35:42.984Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*PwpRos0zNMYSSH26mSJ_Aw.png" /></figure><p><strong>Timeline</strong>: 10 days<br><strong>Role</strong>: UX/UI Designer, with a focus on motion design and AI illustration during the UI phase<br><strong>Team</strong>: César Deslandes, Rafael Boavida<br><strong>Tools:</strong> Figma, FigJam, After Effects, AI (Firefly, Gemini, ChatGPT)</p><p>Hej! We finished <a href="https://www.ironhack.com/de-en/ux-ui-design/remote">Ironhack UX/UI Design bootcamp</a>!<br>Our final project was something quite different — the redesign of a mobile game feature: The «Drill Up!» event in HOMA Games’ «All in Hole».</p><h3>Overview</h3><p>For two weeks we worked on UX and UI to redesign a reward ladder event, from research to animation and scalability. We had a major event of our own right in the middle, but all for the better. I’ll come to that.</p><p>This time around, I worked with an all new, all wonderful team with very different, great skills to complement one another:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gmteJ0yfhZbJlBavO9lOzg.png" /></figure><p>The client was HOMA Games, represented by Viktor Kalvachev:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UWY2Ff23y5XtH53BkuVTQw.png" /><figcaption><a href="https://www.homagames.com/">www.homagames.com</a></figcaption></figure><p>It was a pleasure working with him as he’s very down to earth, refreshingly honest and straight in critiques — with our work, but their own, too.</p><p>HOMA is a powerhouse in hybrid-casual gaming with over 80 games and two billion downloads in the short span of only 8 years. <br>All in Hole is one of their success stories.</p><p>That said, our task here wasn’t meant as a real project for HOMA from the get-go and Viktor was very straight forward about that, too.</p><h3><strong>The Game</strong></h3><p>All in Hole is basically the ultimate «clean up» game, but more fun than actual chores. You have a table full of food and other objects and you’re a hole swallowing everything that gets in your way and is small enough!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QkrL_RjkrWSVPteKKLxxaQ.png" /><figcaption>And there’s a glimpse of the character, Molly.</figcaption></figure><p>All in Hole presents different events to the user known as progress reward ladders that function a little like a side quest to make the game more interesting.</p><p>It is a scrollable map that shows a player’s journey from start to finish during an event. Think of it as a vertical or horizontal «track» with milestones along the way and the «Grand Prize» at the end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7YQy8ntP3G8kCx4ivTVu-A.png" /><figcaption>From bottom up to the top: «Drill Up!» as it is</figcaption></figure><h3>The mission</h3><p>For our project, we were to propose an alternative to a progress reward ladder called «Drill Up!», because right now it feels stale and disconnected:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O2FnaTPOYaYXwwRs5ZR-fg.png" /></figure><p>So our mission here was to make this sidequest more enjoyable and purposeful.</p><p>In the initial meeting, Viktor gave us a lot of room: To come up with different storytelling, event direction, graphics and seemingly great freedom in overall approach, which we might have overestimated after all. <br>But I’ll come to that.</p><h3>Research</h3><p>Kicking off, we started checking what the competition was doing. Diving into all these games, we decided on doing a<strong> feature and visual analysis</strong> at the same time:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3MGB5wPW7YDZOnAsK9AaHw.png" /><figcaption>Royal Match</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3lSWyq2bP5PrfjzfjAcv_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4licLxFwoS8lx-rTBSxEpg.png" /><figcaption>Royal Kingdom, Match Villains</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YFAEKGGI_8VrTi9vzJhRtA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UCJqFcVSbXmkQiFFsIWigg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lNrxiIGOVEqEk7NtSiUgug.png" /><figcaption>Toon Blast, Coin Master, Hole It</figcaption></figure><p>What we learned? Well most importantly:</p><blockquote>* Every game has one or more<strong> progress reward ladders</strong><br>* Every game shares one or more<strong> mechanics for progression</strong> (level completion streaks, complete a set amount of levels)<br>* <strong>Simple, in-your-face CTA</strong> colors do the trick, clear color distinctions where it counts<br>* In-game visuals <strong>focused on simplicity </strong>— menu etc. more playful and complex</blockquote><blockquote>* Compared to competition, All in Hole’s storytelling around Molly <strong>could be improved to gain more user retention</strong></blockquote><p>We also did a <strong>Lean UX Canvas </strong>and set up an <strong>online</strong> <strong>survey </strong>catered specifically to power users<strong> </strong>— that one was never used, though, because the immense facebook group didn’t release the post within our very short timeline. Maybe it could have helped us keeping closer to the game, but anyway.</p><p>On that basis, we stepped into user interviews, talking to 5 casual gamers between 20 and 70 years of age. We found that it matched HOMA’s experience of their audience, being mostly twentysomethings, mothers and grandparents. Here’s a few insights:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GIeaX2ELaZAxiLyfcpEKMQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DcW6pUxN_sdRiZss3N_uZw.png" /></figure><h3>Defining the problem</h3><p>With the feedback we received from users we decided to focus on bringing a visually engaging experience that stays connected with the game’s characters (Molly and the Hole), but brings something more exciting with a bit of storytelling.</p><p>All the insights, distilled through our Affinity Diagram led us to our primary Persona, Casual Maria:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_qNM40noBJts-aRPzXM5ww.png" /><figcaption>photo: iStock/ilkercelik</figcaption></figure><p>She’s an avid casual player whose pain points root in information confusion and static backgrounds. When she’s commuting home she plays mainly to take her mind off things while waiting. She is excited about the new event as a side-quest, but ultimately disappointed by the complete lack of interactivity and soulless storytelling.</p><p>That way, we came up with our <strong>problem statement</strong>:</p><blockquote>Casual gamers of All in Hole need to find a way to<br>connect with the Drill up event emotionally and interactively<br>because <br>right now it feels more like a boring chore than an experience.</blockquote><h3>Ideation</h3><p>So: How might we…<br>… make Drill Up more engaging?<br>… give Drill Up its own visual experience?<br>… use the game’s look and feel to open up a new world for the user?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XRglXFDFRyYaxPPBQDY7aA.png" /><figcaption>my HMW’s &amp; first feature ideas</figcaption></figure><p>After ideating about features for a bit, we quickly burst out a round of<strong> Crazy-8</strong> idea sketches and refined some of them before going into a <strong>MoSCoW</strong> map for feature priorization. As the game approach is an uncommon task for us, we allowed for more time in that ideation stage, simultaneously setting up basic storytelling and level structure.</p><p>All things gathered, our <strong>MVP</strong> came out like this:</p><blockquote>At the bare minimum, the new Drill Up event should be an underground journey to pick up Holly’s friends for a party in the night forest. The user should collect items in the main game and be able to make the journey advance with at least some interactivity.</blockquote><h3><strong>Lo-Fi</strong></h3><p>With a basic <strong>Userflow </strong>in place, we went for <strong>low-fidelity </strong>concept sketching, working on different parts of the flow and getting back together every so often to align.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MNTHyyuMYxkAj5dtKYZ34g.png" /><figcaption>Lo-Fi sketches with user feedback</figcaption></figure><p>I started by illustrating the scrollable map (see below, compared to Mid-Fi).</p><p>The first feedback from 5 people gave us a bunch of ideas for improvement already. The users mainly lacked information about the goal to be achieved and how to progress through the event.</p><h3>Mid-Fi</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BXWVwsf4oh4ry9s-K11EsQ.png" /><figcaption>bottom-up scroll from mole home to forest party: Lo-Fi (by me) and Mid-Fi (César)</figcaption></figure><p>At this point, César took over most of the illustration work. I would’ve loved to go on with it more, but he was faster, had more time and did an incredible job — being a professional painter and all :)<br>And this way I was able to focus on animating, which we already started exploring in Mid-Fi. With my background in moving pictures, I did most of that, while Rafael was helping from all sides: Doing additional animation and screens, working on the presentation and a lot more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xm3bTjZVujusGOn3-XZNnw.png" /><figcaption>new icon on home screen (disco ball), new event footer, new event preview screen</figcaption></figure><h3>Transition to Hi-Fi</h3><p>Maneuvering towards High-Fidelity, we used a lot of AI for graphics, specifically Adobe Firefly and Gemini, which gave us the best results.</p><p>Still, there was lots and lots to do with refining our prompts, planning and combining the different parts of it, tons of detail work and not forgetting about the core tasks.</p><p>We had made good progress in translating the concept into images to present the result to our client, Viktor: Mid- and work in progress High-Fidelity concepts:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ocq82YaPlkpoPUvXdUfKqg.png" /><figcaption>bottom-up from left to right</figcaption></figure><p>But after about two days of sketching, first prototyping and testing, it became clear that we had gone too far in our search for a compelling story. For Viktor, the scenario seemed too complex for a hyper-casual mobile game, undoubtedly forcing the typical All in Hole-player to ask too many questions about this new world and going into too much detail for a side-task you might only go to to quickly gather your rewards.</p><p>While hurtful for a moment, this gave us the opportunity to take on a new challenge: Finding a new, much simpler scenario that would meet our UX research as well as stakeholder expectations.<br>Personally, I am strangely fond of these moments of plans seemingly falling apart. I surely am not searching them, but I feel a big transitional power in them and I know it from my filmmaking experience: A calm little stream having transformed to a waist-deep river on shooting day one or a drone crashing moments before shooting with 50 extras? Been there. Tedious planning is great and improvisation is exciting, but only the combination unfolds the full potential in a project.</p><p>But back to topic.</p><h3>Ideation 2.0</h3><p>We quickly recovered to brainstorm new ideas of top-down/bottom-up game scenarios, since the whole party setup wasn’t going to work here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7XsTGn2iUjX2B72hJcnD8A.png" /><figcaption>brainstorming</figcaption></figure><p>Considering the time left, Viktor gave us the freedom to choose a different scenario, detached from Molly and All in Hole to pursue and we did consider it — even though too much freedom is a constraint of its own.</p><p>The new idea needed to have a main character with an understandable goal, milestones that made sense in a storytelling fashion plus as a reward, regression steps making sense in storytelling aaaand potential for scalability/variants to change it up every once in a while… all in one.</p><p>But we found a new path and were quickly able to set up our <strong>MVP 2.0</strong>:</p><blockquote>At the bare minimum, the new Drill Up event should be an exciting, yet very simple journey up a skyscraper to steal items for the main game.</blockquote><h3>Lo-Fi 2.0</h3><p>We were happy to stay with Molly as our protagonist and the tower climb robbery theme seemed to work in all respects:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DlQTS8RHhAWiv56A3ipv_g.png" /><figcaption>lo-fi sketches and some usability test results</figcaption></figure><p>Following user feedback, we revised the low-fidelity and mid-fidelity prototypes to keep the animation simple, with the goal of helping players understand the process more easily and giving them a moment of excitement that keeps them coming back. <br>We reinforced the concepts with new <strong>Brand Attributes</strong> and a <strong>Moodboard</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2sUMupaI07aiNqFWnn_Gcw.png" /></figure><p>Soooo meet Molly! <br>Our very own Tom Cruise, but in a cute way! <br>We went with «Tower Heist» to establish a simple, scalable, exciting, but still light theme.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2i4Hz-fPIWb4JblvXi6yIg.png" /></figure><h3>Hi-Fi</h3><p>Going High-Fidelity, we used a lot of AI for graphics again and once we had a foot in the door, it flowed way more smoothly. Still, not easy-peasy.</p><p>We also had a lot of complex, rather uncommon UI problems to tackle:<br>* Lots of seamless animations big and small (Molly is blinking :))<br>* Lots of components and variations<br>* Combination of fixed and scrollable layers in orders not Figma-supported <br>(the progress bar)<br>* Animations not continuing under overlays<br>* Keeping close to the Heist-theme while making the UI interesting</p><p>But with very efficient teamwork, we were able to move past all of it and here’s the result!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FE1vM68PTlBo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DE1vM68PTlBo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FE1vM68PTlBo%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b932929451e77c49459a15be81889644/href">https://medium.com/media/b932929451e77c49459a15be81889644/href</a></iframe><p>The new ladder event has way stronger storytelling in terms of a recognizable theme and character. The more exciting goals and task further connect the player emotionally. Hand in hand with that, the visuals are way more approachable and the screen flow tells a more coherent, complete story.</p><p>By adding non-intrusive tooltips, we eliminated confusions about the lack of interactivity right at the beginning of the event.</p><p>Aaand it is now suited for variations in event repetitions — I’ll come to scalability in a second.</p><h3>Tablet adaptation</h3><p>We also drafted a tablet prototype, which didn’t give us a lot of trouble since we built our visuals with a bit of breathing room for responsive design in mind:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ts3pmo-KsQPfBa5EOEOWeg.png" /><figcaption>Tablet adaptation</figcaption></figure><h3>Accessibility Tests</h3><p>For Accessibility testing, we worked with the STARK plugin and manual checks to eliminate violations:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K967iRrHJvWKPbigo-sXaA.png" /><figcaption>Accessibility tests</figcaption></figure><h3>Scalability</h3><p>For these recurring events, scalability should be a big factor and with Firefly, I drafted a range of possibilities to introduce new worlds that are easy to grasp at first sight:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wyl525yNnOnZzmOUFdQogQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zBElGlQl2dXu3fvnCXlajQ.png" /><figcaption>Variations of our tower</figcaption></figure><h3>Next Steps &amp; Learnings</h3><p>Our main next steps would include getting feedback from real power users<br>to see what they can identify that we possibly overlooked. <br>Also, prototyping with a full-scale ladder (ours is shorter than the original) and implementation of refined variants would probably make sense after the next longer stakeholder meeting.</p><p>Speaking of which, the first short feedback we got from Viktor was overly positive, surprised at how we managed to recover after the last meeting and what we managed to accomplish in just a couple of days. He said there’s still a lot to talk about and polish, but he would’ve been majorly disappointed if not, for that would mean he wouldn’t do a very good job himself…</p><p>We definitely learned our bit about the requirements of hyper-casual gaming versus classic gaming (more our turf) and even other mobile games.<br>Deep alignment with the stakeholder was an issue we will keep a closer look at from now on, even though not much was lost here and I prefer an open mind to blindly sticking to «the rules».</p><p>And I specifically learned a lot about animating in Figma, including its limitations. Coming from After Effects, there is a lot you can do with quite simple mechanics, but used to sheer endless possibilites, you keep hitting walls very fast and no alpha channel (transparency) for videos makes it hard to combine the two programs.<br>But there’s ways.</p><h3>Stay in contact</h3><p>Thank you for reading this far! We hope you had some hyper-casual fun.</p><p>We want to thank HOMA and Viktor for giving us this opportunity.<br>And Ironhack of course!</p><p>In case you want to say hi or stay connected, do the thing.</p><p>And please feel invited to my portfolio website at <a href="http://www.mathishanspach.de/">www.mathishanspach.de</a>. It’s mostly cinematography, photography, illustration right now, but that may soon change a bit and possibly isn’t the most boringest to look at either.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lkZx-sgbFIq_MNxnJ5ELOw.jpeg" /><figcaption>«Dir en Grey» concert photography</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f3891956a99" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX/UI — HeyCoach Gym App]]></title>
            <link>https://medium.com/@mathishanspach/ux-ui-case-study-heycoach-gym-app-ba5502102c61?source=rss-e8881e264dd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba5502102c61</guid>
            <dc:creator><![CDATA[Mathis]]></dc:creator>
            <pubDate>Sun, 22 Feb 2026 21:52:26 GMT</pubDate>
            <atom:updated>2026-04-22T07:36:33.521Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5V6R0TQ18pQ904libJJY5g.png" /></figure><p><strong>Timeline</strong>: 9 days<br><strong>Role</strong>: UX/UI Designer<br><strong>Team</strong>: Kiran Riaz, Max Butler<br><strong>Tools:</strong> Figma, Figjam, ChatGPT</p><p>Hej! As a fourth and almost final project in <a href="https://www.ironhack.com/de-en/ux-ui-design/remote">Ironhack UX/UI Design bootcamp</a>, we worked on an ambitious app design: to create a <strong>hands-free, voice-powered workout companion</strong> that keeps high-intensity gym-goers in the flow. It eliminates the phone-fumble, allowing you to log reps, set timers, and connect to gym equipment without ever breaking your set.</p><h3>Overview</h3><p>The <strong>client</strong> is San Francisco’s Daily Health Conference, in a competition for the best designs being shown in their upcoming conference. So the topic is the very broad theme of «Wellness», which we wanted to break down very fast as to not be stuck in a wicked problem once again.</p><blockquote>The Daily Health Conference wants designers to rethink how people can adopt and commit to a health-improving routine.</blockquote><p>The project goal was to design an <strong>MVP</strong> (minimal viable product) of a <strong>voice-first app </strong>including <strong>multimodal interactions</strong>. <br>We chose <strong>iOS</strong> as the initial operating system.</p><h3>Setup, Research, Understanding</h3><p>Settling for the workout topic very soon, we hit the ground running, to stay in the sport metaphor.</p><p>Using Notion, Slack, Zoom and Figjam to <strong>organize our remote team workflow</strong>, we dove right into research, including competitive analyses of Nike NTC, Stronger and Strava in <strong>Feature Comparison</strong>, <strong>Perceptual Mapping</strong> and an overview of <strong>USP’s / Strengths / Weaknesses</strong>.</p><p>Our <strong>UX Strategy Blueprint </strong>served as the anchor, giving stability while keeping us flexible enough to stay in the real-world and focus on our users’ actual wants and needs:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z4U1IkiRSxW-eSd5NeDbbQ.png" /><figcaption>UX Strategy Blueprint</figcaption></figure><p>We conducted five user interviews asking about gym and workout habits:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mclGhKFPAXg0I8doTIWSpA.png" /><figcaption>some User Interview questions</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ay1xjf_T9WBRCA7qVMWbgw.png" /><figcaption>Interview Insights</figcaption></figure><h3><strong>Definition</strong></h3><p>With a lot of feedback to go through in our <strong>Affinity Diagram</strong>, we arrived at four main insights leading the way:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ju29ZgryvLpDd4F_mBk6ZA.png" /><figcaption>Affinity Diagram Insights</figcaption></figure><p>We created an <strong>Empathy Map Canvas </strong>to move deeper into definition phase, giving us an overview of who we were trying to represent; What they hear, do, say, see, need to do and what their pains and gains actually are.</p><p>That’s how we came up with our <strong>Primary Persona — </strong>meet «performance optimizer Eliza»:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ThQ6zVSyeVGXxfP9lWrSSw.png" /><figcaption>Primary Persona; Photo: unsplash/Spencer Davis</figcaption></figure><p>Based on the interviews, Eliza views manual logging as a disruption to her flow, requiring a hands-free solution that allows her to track progress without being tethered to a screen.</p><p>The <strong>User Journey Map</strong> visualizes Eliza’s emotional flow to pinpoint where voice technology can bridge the gap between «the zone» and the friction of manual data entry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*07Se7OlvPU1zJq9IHvUYbQ.png" /><figcaption>User Journey Map; Photo: unsplash/Spencer Davis</figcaption></figure><p>Those pain points and opportunities in mind, we arrived at our problem statement:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k5ZrpX3RcxNm6vi1gbONfQ.png" /><figcaption>Problem statement</figcaption></figure><h3>Ideation</h3><p><strong>How Might We…</strong><br>… enable workout tracking that feels invisible during high-intensity sessions?<br>… reduce the need for manual interaction while still capturing meaningful performance data?<br>… support users in maintaining their workout «zone» while ensuring accurate progress tracking?</p><p>These questions in mind, we gathered all kinds of possible features and applied the <strong>MoSCoW method</strong> to define our <strong>MVP</strong>, focusing only on essential flow-preserving features and removing distractions — here’s a selection:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YcOuNDnUcwtp_Xzk7BaA5Q.png" /><figcaption>MoSCoW Method</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8YSQe2DjKphj-funILNQqQ.png" /><figcaption>Minimal Viable Product</figcaption></figure><p>The <strong>main Userflow</strong> maneuvers us through a simple workout setting plus alternative states:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nIxdlLUyHy5aSXWZiNFZQg.png" /><figcaption>Main Userflow</figcaption></figure><h3><strong>Lo-Fi &amp; Mid-Fi prototypes</strong></h3><p>We then went into our first <strong>Lo-Fi Wireframe</strong> <strong>sketches</strong> with two individual approaches, the latter is mine. Combining them for <strong>early usability testing</strong> gave us a lot of insights and hints already.</p><p>Here’s a selection of screens and feedback:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*abIDCr-qAlThRewdXXDKdA.png" /><figcaption>Lo-Fi Sketches &amp; first usability tests</figcaption></figure><p>Same goes for the <strong>Mid-Fi</strong> screens we created next:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4STph8XAhkPUXIHkVeH2rg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O01VN3QHrzBTNmqLjReYJw.png" /><figcaption>selection of Mid-Fi screens &amp; feedback</figcaption></figure><h3><strong>Visual competition</strong></h3><p>We picked two other apps for <strong>Visual Competitive Analyses</strong>, rather mechanical Freeletics and bold, motivational Nike Training Club:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7WTBL2LE6d3bbWWTo9rmSg.png" /><figcaption>Visual competitive Analysis — Freeletics</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yRNYjwjuzWiZ-X83yP1-vw.png" /><figcaption>Visual competitive Analysis — Nike</figcaption></figure><p>We were aspiring to land in between those two worlds with a functional, yet energetic, engaging visual style.</p><h3>Defining our style</h3><p>So our <strong>brand attributes</strong> are approachable, convenient, energetic and straight forward, to go with a very concise concept and app design.</p><p>We checked the <strong>moodboard</strong> with actual testers, too and got feedback with a focus on energy, friendlyness and also straight forwardness. Only convenience was just difficult to visually capture in that context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dEshmoqWvFqwhIPPlbXvfA.png" /><figcaption>Brand attributes, Moodboard, Moodboard test; Photos unsplash: i yunmai, Karsten Winegeart, Mika Wegelius, ronank, Shalom Ejiofor, Pawel Czerwinski, Liu JiaWei</figcaption></figure><p>When tackling <strong>colors</strong>, we were very soon dedicated to a dark, energetic (dark energy, great topic!) look. The yellow «sun» emerged next, giving us a feel for the use of the vibrant yellow we wanted to base our colors on. The contrasty, but smooth blue came in later after some experimenting and we added an energetic gradient blue, too, which you’ll get to know later. There’s no deep black or white.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Vbqk4F3ebdjzYwEQBs4gQ.png" /><figcaption>Color evolution</figcaption></figure><p>For the<strong> typography</strong>, we went for two very straight-forward typefaces for Headings etc. and Body Text. They have some weight and stability, but not too much to make them look overly powerful. We wanted them to still go with a sleek, concise design and a modern feel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lLkK1SnPKTgvwpB405nNPA.png" /><figcaption>Typography</figcaption></figure><h3>Hi-Fi wireframes</h3><p>Now set up for hi-fi, we started with the home screen, of course, but let’s go from a user’s perspective.</p><p>In the welcome-animations and login screen, we already wanted to present our core feature, the voice control. After feedback to make it clearer, we came up with this start flow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t-Aey2JQjrDUBCdhtHbtSQ.png" /><figcaption>login flow</figcaption></figure><p>We went with HeyCoach as a name as it incorporated both core ideas very clearly — voice recognition and an AI focus.</p><p>Here’s the rest of the set-up process, including a system message. Most of it is a draft, but gives you an idea of the journey:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bpJEU58wGgOXDLMX3cqZtA.png" /><figcaption>set-up flow</figcaption></figure><p>Again, we included the clear connection from our «Sun» to the microphone / voice part of the app.</p><p>After that, you end up on the home / workout screen:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KKL0opoNU-oQiVeRGd6alg.png" /><figcaption>home / workout screen</figcaption></figure><p>There’s a clear overview of workout types, workouts, our coach «sun» and the navigation to workouts, repeat last workout, progress overview and the profile page with daily/weekly/overall goals. We wanted to keep it very clean and fast to navigate.</p><p>We included an in-app AI error message, too. And here’s the HIIT- and Strength-paths from category to workouts to exercises. You can change the number of sets and get an approximate workout duration. With strength training, there’s a warm-up function and you will be able to go deeper and see each exercise in detailed instructions / video.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zV0_LZHCT0cWfaU2t6x_YQ.png" /><figcaption>workout / exercise screens</figcaption></figure><p>In the HIIT-path, you will have time to prepare for the first setup on the Treadmill (replacing a warmup, too) and you can connect your phone to the machine, being able to both control it from there and getting valuable information for your summaries / progress from it.</p><p>There’s rest steps, adjustable times and weights and you can swipe the next exercise up, click the «sun» button or use its primary function and simply speak to get to the next page. In the end, you will get a summary page, some interesting data, you can go for a cooldown, do another workout or hit your progress page — the data is saved automatically, of course.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TeZXz1JGCI7DgKG6Ej_VbQ.png" /><figcaption>high intensity workout</figcaption></figure><p>For the strength workout flow, it is quite similar. There’s no exercise timers, as it is not that much about speed, just the rest periods are the same. The exercises have quite big screens to be easily legible from afar. You can adjust number of repetitions and weights before or after the exercise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4EHJ1oTrJwEfEs7Yz-zkyw.png" /><figcaption>strength workout</figcaption></figure><p>And lastly, there’s error and closing messages, too:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8nidIiiMVUkZsMaofqQ2rg.png" /><figcaption>in-app messages</figcaption></figure><p>For <strong>accessibility</strong>, we checked with the Stark plugin and didn’t find any violations. With our big typo and contrasts we did not expect any issues, but that lets us sleep yet a little better.</p><p>If you want to give the prototype a try yourself, please go ahead:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/472/1*CgxQiZKwgTstu7B41hbUqQ.png" /><figcaption><a href="https://tinyurl.com/5t4rdsyw">https://tinyurl.com/5t4rdsyw</a></figcaption></figure><h3>Next Steps</h3><p>All this done, there still is quite a lot left to work on. After the bootcamp, we would work on the animations, especially our «sun» to better mimic spoken words and a light pulsing to know it is awake and awaiting input. Time running out should be animated as well, we hit a wall there, as there seem to have been some changes in German Figma and we couldn’t do it with advanced stroke settings. There’s other ways, but it wasn’t our main focus for the presentation. Smart animations between pages would be third on that list.</p><p>We would create a «real» iOS message, more advanced set-up pages and an onboarding flow, auto-layout all the way, add more than stumps for profile and progress pages and create custom icons to make them match better. On the same page, a deeper look into exercise details would be good to show.</p><h3>Learnings</h3><p>An old design lesson came back to us here. It’s not finished when there’s nothing left to add, but when there’s nothing left to take out. Focusing on taking out friction instead of adding functions really made it come to life.</p><p>Auto-layouting from the start would’ve definitely helped us, at least starting after lo-fi. Speaking of which, the lines between lo- to hi-fi were a bit blurry in this project and I’d like to keep closer to the concept in the future. We struggled with time in the design-half, but neglecting both of these things didn’t help us with that.</p><h3>Stay in contact</h3><p>Thank you for reading this far and thanks to the team! It’s been a pleasure.</p><p>In case you want to say hi or stay connected, do the thing.</p><p>And please feel invited to my portfolio website at <a href="http://www.mathishanspach.de/">www.mathishanspach.de</a>. It’s mostly cinematography, photography, illustration right now, but that may soon change a bit and possibly isn’t the most boringest to look at either:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wczB5eRwQwrXkOU-3eWOtA.png" /><figcaption>feature film «Alle in einem Boot», raw still</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba5502102c61" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX/UI — Redesigning Duolingo]]></title>
            <link>https://medium.com/@mathishanspach/ux-ui-case-study-redesigning-duolingo-e30316097a9a?source=rss-e8881e264dd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e30316097a9a</guid>
            <dc:creator><![CDATA[Mathis]]></dc:creator>
            <pubDate>Sat, 14 Feb 2026 19:00:09 GMT</pubDate>
            <atom:updated>2026-04-22T07:37:12.218Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eXNedYhtQ-FElQIkEi0pWQ.png" /></figure><p><strong>Timeline</strong>: 3 days<br><strong>Role</strong>: UX/UI Designer<br><strong>Team</strong>: solo<br><strong>Tool:</strong> Figma</p><p>Hej! The middle project in <a href="https://www.ironhack.com/de-en/ux-ui-design/remote">Ironhack UX/UI Design bootcamp</a> was a bit different from the earlier and future projects — working <strong>solo</strong> and not following the now-usual process of research, definition, ideation and prototyping plus testing, but learning a few new systems and <strong>copying</strong> plus <strong>redesigning</strong> screens of an existing app.</p><p>My main goal in this redesign of beloved language-learning app Duolingo was to improve user orientation in the progress and provide more customization options while maintaining Duolingo’s playful learning style.</p><p>It was a quick project in that, only about two and a half days plus a weekend… let’s see!</p><h3>Heuristic Analysis</h3><p>First, we added Heuristics to our tool box, checking a list of specific usability features and how they are implemented around the whole app.</p><p>I chose Duolingo, because I’m a power user and am very frustrated of it at the same time. While a lot of Duolingo is working very well, I noticed recurring friction in progress visibility and customization:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zK9KQ1sw_moCUN8_pZKIhQ.png" /></figure><p>The control over things like notification screens and practice focus is unnecessarily limited:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y4sIpj1SglKPZj60DngXkg.png" /></figure><h3>The clone</h3><p>Next up, we were to select three of the screens we were intending to redesign and <strong>clone</strong> them in Figma.</p><p>I decided on going deep and recreating the screens without using screenshots (except for the Android UI) for any icons or effects. And to practice my Figma and use auto-layout from the start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OEklkEzv-l0xjoySovn0PA.png" /><figcaption>Duolingo screenshot vs. Figma clone</figcaption></figure><p>My Illustrator skills surely helped me a lot with aaaall of the comic icons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dGA0f7cK3QjsQW_R1wEdoQ.png" /><figcaption>Duolingo screenshots vs. Figma clones. And yes, that is my streak… mostly in Swedish, though.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/1*ZelPJTdQn0t7hIt3UR8xlA.png" /><figcaption>Yeah, you too.</figcaption></figure><p>Only some visual elements (exact font, «SUPER» banners, Android UI transparency) remain partially unresolved due to the time constraints.</p><h3>Visual Competitive Analysis</h3><p>Next stop: Duo’s competitors. I chose Babbel as the biggest competitor in Germany and Preply, which has a bit of a different approach to language learning:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vw0nSGVi5Je6FKoYTEWSMA.png" /><figcaption>Visual Competitive Analysis</figcaption></figure><p>There’s very different approaches to structure, pacing and lesson delivery, mirroring the wide array of styles and audiences in language learning.</p><h3>Redesigning</h3><p>Which is why, when starting the redesign-process, I oriented on Duolingos learning style, but recalibrated their <strong>brand attributes</strong> and tried visualising it in a <strong>moodboard</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1O4tMME8mU2U-xTUPJnqMg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lh4SUJsyuFZUY0iVF1pDHA.png" /><figcaption>Pictures unsplash: Irvan maulana, Joel Muniz, Gayatri Malhotra, Clay Banks; remaining pictures unlicensed; Moodboard &amp; Brand Attributes</figcaption></figure><p>Now on to the <strong>colors</strong>!</p><p>I chose a complementary contrast, but a smooth one. I really like the fresh, light yellow and the calm, happy purple. But I also wanted to keep a lot of white breathing space and off-black for the typography. The utility-green pops, but still fits right in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-fhNIEVu450RTbLxyq8l6Q.png" /><figcaption>Redesign color palette</figcaption></figure><p>And<strong> typography:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*12XWpsxTl5JaYtWv5mQX-g.png" /></figure><p>Going straight into hi-fi wireframing felt more like my pre-bootcamp approach, but already didn’t feel right and like home anymore.</p><p>I wanted to start strong and find my way back to a more conventional design with less chaos from there, but I might have overreached a bit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OlkJIBYcrRUYOl0jKDT9Lw.png" /><figcaption>Testing the waters in hi-fi</figcaption></figure><p>I liked aspects about it and in retrospect I could come back here and try to loosen the final design up a bit with these inspirations, but at the time it was too much at once. I wanted major mechanical redesigns and didn’t have a complete plan for those. Stressing about colors, photos and craziness at the same time didn’t work. So I took the impulse to take a step back and go mid-fi, getting rid of the colors first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cRR1Uq5t7k9_tZEkQuRzyQ.png" /><figcaption>mid-fi work in progress</figcaption></figure><p>I tried different lesson mechanics, loosening up the now rather strict design, but wasn’t convinced.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w5A1lZ_2o4K5R8kEu_-eMw.png" /><figcaption>final mid-fi</figcaption></figure><p>I settled on a more simplified approach with some major redesign and decided to go back to hi-fi — or well, further.</p><p>So here are the <strong>hi-fi wireframes</strong> vs. the originals.</p><p>Everything is custom-built and I maybe went a bit overboard with the complete and utter redesign. A rebranding could have been way simpler, but there was so much in the mechanics and graphics I did not want to keep, that it felt reasonable to move away from the original to an almost clean slate.</p><p>In this first screen for instance, I examined the lack of progress visibility even though that’s its sole purpose. The redesigned overview screen improves visibility of the real-life language level both in the header and as part of a deeper info text, which helps learners estimate and appreciate where they are in the course and language:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0LUewFplnGVEkAdDt2rKtQ.png" /></figure><p>The feedback I got was ambivalent. People liked the clear overview with the language level in both header and body as well as the text itself very much, but would’ve maybe cut the text shorter and made it more typographically varied and easier to read.</p><p>They liked the color palette, but the overall style was perceived as school-bookish, to which I agree and would like to keep working on. Sometimey.</p><p>The multiple languages offer was well-perceived, too, even though the active language could be way more obvious.</p><p>Next up, the original lesson overview (Home) offers almost no info about the actual contents in a sheer endless scroll. I compressed that into more concise sections with image and title, core vocabulary and grammar to give users a clear overview of what’s ahead or what they already learned:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TDamygcEJJzudrmd-daoww.png" /></figure><p>On here, the key concept found its fans, keeping a clear lesson overview with everything in a glance and useful vocabulary to keep learning even outside the lesson itself.</p><p>The reintroduction of a grammar section (yes, Duolingo used to have it…) was also popular, while the button was a bit unclear. There might be better ways, but I would still keep it unlabeled, since it would be a one-time learning process. We’d maybe have to test it properly.</p><p>The all-in-one button itself was perceived as rather mid-fi, which I agree to. I could also try and give the opposite sides of the circle different shades of green to make it a little easier to read.</p><p>Also, I forgot highlighting the current location in the footer navigation. No time, no testing…</p><p>And self-critically I’ll have to also add that the language tree mechanic isn’t entirely thought-through here. It is unclear how you keep a clear overview of the unit you are in or progression in the language tree (like in the original sticky header, although it’s not of much use either) if it is just scrolling through all them lessons.</p><p>Anyway, here’s the Practice screen (2nd in my footer). Again, the original design takes up a lot of space for rather basic info and introduces weird sub-sections. I compressed it into a one-pager, again focusing on clarity:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RJ8y9wyktBudZDTAUYZxsQ.png" /></figure><p>The four clear categories were seen as very visible and accessible. The colors are a bit stale here, though, and the rest at the bottom felt a bit cluttered. I wanted to include those three categories in a visually different way, because they are not lessons, but places to review information. They would probably not be buttons, but pages to pull up, like notes in a book. Yeah. This page is where the textbook charm really came to life… I did go for some retro-aesthetics earlier, but this wasn’t what I had in mind.</p><p>So for the end, here’s all three at once:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gr_DO0N-iNUt57zZyEjN_Q.png" /></figure><h3>Learnings &amp; next steps</h3><p>Of course there’s the obvious Heuristics concept and a few details, too, but the main learning would be stripping away so much of the process in lack of time and what it does to the final product. The lo-fi and mid-fi and testing especially would have helped me quite a lot here and I could have focused piece for piece instead of doing everything everywhere all at once.</p><p>I am not extremely happy with the final outcome, but keeping in mind the scope of the project and the extremely limited time, I am proud of the process and a lot of the mechanical thoughts and decisions. While it is not quite there yet, I also like the designs and think it could be tweaked into a good direction without changing all too much. A more playful approach would definitely make it more appealing and I think meeting back with the original design halfway could be the right path. As a power user, that’s my peace offer! :)</p><h3>Stay in contact</h3><p>Thank you for reading this far!</p><p>In case you want to say hi or stay connected, do the thing.</p><p>And please feel invited to my portfolio website at <a href="http://www.mathishanspach.de/">www.mathishanspach.de</a>. It’s mostly cinematography, photography, illustration right now, but that may soon change a bit and possibly isn’t the most boringest to look at either.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YiE4neirAJFS7NZ6_XrWSQ.jpeg" /><figcaption>Grafische Leistungen erarbeitet im Anstellungsverhältnis zur KölnMusik GmbH/Kölner Philharmonie</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e30316097a9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX/UI Case Study — The Box]]></title>
            <link>https://medium.com/@mathishanspach/ux-ui-case-study-the-box-80b2c918aada?source=rss-e8881e264dd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/80b2c918aada</guid>
            <dc:creator><![CDATA[Mathis]]></dc:creator>
            <pubDate>Tue, 10 Feb 2026 21:21:34 GMT</pubDate>
            <atom:updated>2026-04-22T07:40:26.046Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX/UI — «The Box» gym web design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1NmRYvaDSwPuIIlYzoei0w.jpeg" /></figure><p><strong>Timeline</strong>: 8 days<br><strong>Role</strong>: UX/UI Designer<br><strong>Team</strong>: Niveditha Kulkarni, Max Butler<br><strong>Tools:</strong> Figma, FigJam, ChatGPT</p><p>Hej! As a second project in <a href="https://www.ironhack.com/de-en/ux-ui-design/remote">Ironhack UX/UI Design bootcamp</a>, we have been working on a website redesign for an actual gym/Crossfit community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ApZNGuk7Qk_IusgDHyQvFQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pE488zu7P7ysy3eK-_hqKQ.png" /><figcaption>That’d be Niveditha, Maxie an me, Mathis.</figcaption></figure><p>We searched for potential customers ourselves and I found a children’s theatre, a film distributor and a community center, which I would’ve also loved to work for, but they didn’t work out for scheduling reasons. So.</p><h3>Overview</h3><p>»Sky Health — The Box« is a Netherlands-based gym focusing on everyday people doing everyday workouts and building a community through group classes in a wide variety of disciplines and with close trainer guidance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wT_V8s2puHbxl2clgT4zZQ.png" /><figcaption>the website in its current state</figcaption></figure><p>Right now, the website is working mainly as a hub for the external course organization tool Gymly. A lot of the buttons are not working since they adjusted to the Gymly setup, there’s missing images and little imagery overall, info stumps and everything’s scattered in an unintuitive navigation.</p><h3>Research</h3><p>Niveditha is a regular and knows the gym, so we could arrange for an interview with Jair, one of the founders — learning about his vision, focus points and issues with the current website, too. He wants to lead the gym away from a CrossFit-only place and focus on the community-aspect a lot. We also learned about the great importance of trial lessons and website-credibility for first contacts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ks2_HgBzzKFo-GgiLcI-_g.png" /><figcaption>some stakeholder questions and notes</figcaption></figure><p>We followed up with a competitive analysis of other gyms and CrossFit spaces in the neighbourhood and wider area, which there are surprisingly many. And with a few surprising differences:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ceHmeUfR9wua3gVGUrrbzg.png" /><figcaption>competitive feature analysis</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uD4Rlze1sRkFgVU51frQHQ.png" /><figcaption>positioning map now vs. intention</figcaption></figure><p>Next up were five UXR interviews with potential users. We tried getting a diverse group on board, but with tight scheduling only managed to get men of different age groups and backgrounds. We focused the questions around trying new courses or places, sense of community and of course blockers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2zNzl4pj3dxEjVqU8YYn7w.png" /><figcaption>UXR interview documentation</figcaption></figure><h3>Definition</h3><p>After working through everything, arranging, refining, clustering and comparing to AI outcomes, we arrived at the final Affinity map:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VX_MN5Lriexen40krOcCMQ.png" /><figcaption>affinity map</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5f9vTm79bWGPyqvhEx-dtQ.png" /><figcaption>a few insights</figcaption></figure><p>Voting on it gave us a few core issues to focus on and enough material to build a primary persona around.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hG5GrUFq_x2e4UimIbAogg.png" /></figure><p>As we were pretty aligned, we built him together from the start, meet:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bTRzCl2sqZhnLJlCIDl9-w.png" /><figcaption>primary user persona</figcaption></figure><p>And his user journey, which revealed harsh pain points around the website and getting to know a gym pre-trial lesson:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l7Slq_U2Encjm9hykyI36w.png" /><figcaption>user journey</figcaption></figure><p>That lead us to the problem statement rather smoothly:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c4cvNWCAZeyjSlM_CdQbwg.png" /><figcaption>problem statement</figcaption></figure><h3>Ideation</h3><p>With the problem defined down to one sentence, we kicked off ideation with our How Might We questions. We brainstormed feature ideas individually to solve the pain points and make the site user-friendly — before dot-voting on them and arranging everything in the MoSCoW map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sXZbHLMq8s83j5DcWVsMhA.png" /><figcaption>How might we?</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*czxjuptODv1dwwe4MaWbeg.png" /><figcaption>MoSCoW</figcaption></figure><p>Feeling the strong wish for clarity and transparency, our MVP focused on just the core wants and needs of our users:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CNsrlGb_tBKE1_boQXDeMA.png" /><figcaption>MVP</figcaption></figure><p>Analysing the current state of the website, the sitemap is a bit messy and vague and so not intuitive to navigate. Prices aren’t in there at all.</p><p>And so our future sitemap was supposed to be clean, clear and transparent. With a trial button available at all times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zuCe3PAXuSd86VbwstSJTw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xHHTSjJA-KSN9ng0Hlyo8g.png" /><figcaption>old sitemap vs. future sitemap</figcaption></figure><p>We streamlined the flow so users can explore and book effortlessly.<br>Our minimal happy path was to check out the website and see whether you trust it, and if, to go and book a free trial lesson:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pL0VHg5shTUi2kjCTrLKaA.png" /></figure><p>We created lo-fi wireframes and tested them with five users to catch usability issues early and refine our design.<br>The key points were unclear labeling, want for better image use and some page arrangement questions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uxlUvqxQ6FP2r-MpUtOuoA.png" /><figcaption>lo-fi wireframe</figcaption></figure><p>We scoped out our competitors’ sites to see get a feel for the visual game and how SkyHealth could fit in and stand out.<br>We definitely saw some patterns there, but also ways we didn’t want to go, like the strongman type — the heavy black and red style.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*td0nnfgoLW7lPTuD_D1ZmA.png" /><figcaption>visual competitors analysis</figcaption></figure><p>With all the research in mind, we now set out to define our brand attributes. Our only differences came down to vocabulary and exchanging that, we were even more aligned on what the single points stand for:</p><ol><li>Energetic</li><li>Inclusive</li><li>Authentic</li><li>Competent</li><li>Trustworthy</li></ol><p>We did moodboards individually first, me focusing on community, invitation and ease, but also searching for lighter colors and trying to incorporate the very positive parts of the name — Sky and Health:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oAOS4Q18GnmZEeZCmCNyIQ.png" /><figcaption>individual moodboard</figcaption></figure><p>Putting it all together, our mood board stands for energy, strength, motivation, community, invitation — basically the digital CrossFit vibe:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L_ZkZQ12WUPZkb3cluMP5w.png" /><figcaption>final moodboard</figcaption></figure><h3><strong>Prototyping</strong></h3><p>We could then level up to mid-fi prototypes and put them through user testing to strengthen weak spots before the final design. Our testers wanted less text and more real visuals, clearer navigation on the homepage, and better explanations of gym terminology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oazzA4fR3QSkARNxUt0mCQ.png" /><figcaption>mid-fi wireframes &amp; feedback</figcaption></figure><p>We decided on colors and a typeface, trying to go for a light, positive look, with still enough stability and professionalism. We wanted to avoid the super-heavy fonts and dark coloring, but not lose the connection to a gym feel altogether:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E0PtdGhUV08gD_KjCbEEaA.png" /><figcaption>Typeface tests</figcaption></figure><h3>Result</h3><p>Our hi-fi wireframe then came to life within less than one and a half days, including dropdown menu, carousel, filterable membership page, the trial lesson overlay and more. Plus a quick mobile version and the project presentation…</p><p>Here you go:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qGzzGZDyaEMSsGTdyxdhQg.png" /><figcaption>hi-fi prototype</figcaption></figure><p>If you want give the prototype a try yourself, you may do so right here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kxG0Gk5YrCV7XrLPNie35w.png" /><figcaption><a href="https://tinyurl.com/ironhack-uxftj26-p2t4">https://tinyurl.com/ironhack-uxftj26-p2t4</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WIvMEGj6X8FaHBQxO2GqtQ.png" /><figcaption>quick adaption to mobile</figcaption></figure><h3>Next steps and learning</h3><p>One major next step is improving how schedules are displayed so users can navigate them more easily and also diving deeper into the mobile version. We did it the other way around for this project, being aware that it makes more sense to go mobile-first.</p><p>Our biggest learning was realizing the importance of testing once again— every time we thought we had the design nailed, users helped us making it even better. Also steps like the sitemap were more tricky than expected.</p><h3>Stay in contact</h3><p>Thank you for reading this far and thanks to the team!</p><p>In case you want to say hi or stay connected, do the thing.</p><p>And please feel invited to my portfolio website at <a href="http://www.mathishanspach.de/">www.mathishanspach.de</a>. It’s mostly cinematography, photography, illustration right now, but that may soon change a bit and possibly isn’t the most boringest to look at either.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6BdVcJKWwrEsxTytV6A6Xg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80b2c918aada" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX/UI case study — The wicked problem]]></title>
            <link>https://medium.com/@mathishanspach/ux-ui-case-study-the-wicked-problem-a50be57e508c?source=rss-e8881e264dd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/a50be57e508c</guid>
            <category><![CDATA[ux-ui-bootcamp]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <dc:creator><![CDATA[Mathis]]></dc:creator>
            <pubDate>Sun, 25 Jan 2026 19:13:20 GMT</pubDate>
            <atom:updated>2026-04-15T07:41:22.291Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX/UI — The wicked problem</h3><p>Hej! I’m Mathis. For the first one and a half weeks in <a href="https://www.ironhack.com/de-en/ux-ui-design/remote">Ironhack UX/UI Design bootcamp</a>, we have been working on a fictional <strong>Wicked Problem</strong> and an app design to go about solving part of it in our team of four:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W_hc3S5dM1_wEK6-VMeTSQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gldLJZFFaIVRK98_9c-W9g.png" /><figcaption>Photo: unsplash/Europeana</figcaption></figure><h3>The task</h3><p>Our main theme was Culture &amp; Heritage and the problem itself didn’t prove to be way more specific:</p><blockquote>Since the 1970s, museums and other public institutions have been suffering a profound crisis. The purpose of this type of institution, is to make heritage accessible to everyone.</blockquote><blockquote>They build bridges between art and people. <strong>How Might We help museums and other public institutions fulfilling their mission of preserving cultural heritage while making it more accessible to a wider audience?</strong></blockquote><p>The challenge of course was to tackle a very broad, highly unspecified problem and cook it down in a structured fashion via the Design Thinking process:</p><p><strong>Empathize <br></strong>– research, focus on understanding users</p><p><strong>Define<br></strong>– refine the gathered information, define the problem you’re trying to solve</p><p><strong>Ideate<br></strong>– brainstorm many different ideas and approaches</p><p><strong>Prototype<br></strong>– validate the idea by setting up a prototype, start minimal</p><p><strong>Test<br></strong>– let users test, test, test and go back if need be</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ix8YZ2xeaJ-hq6xiSIK7pw.png" /><figcaption>Photo: unsplash/Christian Wiediger</figcaption></figure><p>Also, we had to include a <strong>non-digital component</strong> and gathered some <strong>learnings</strong>, which we will come to in the end.</p><p>We used <strong>Figjam</strong> plus a bit of <strong>Figma</strong> for the whole process. With a wide Adobe background, it was one of my first experiences in Figma and I love it. And especially as an InDesign pro and mid-level Illustrator user I felt right at home from the start. And my CSS-skills helped a lot, too.</p><h3>Empathize</h3><p>But back to it! We plunged right into empathizing with our potential users, brainstorming on the problem and kicking off <strong>SECONDARY RESEARCH</strong>.</p><p>Four creative brains, we did have to remind ourselves not to start by striving for solutions, but to fall in love with the oh-so-fuzzy problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gGiVf4Nwlv0BVlwlYfP-uQ.png" /><figcaption>clusters of secondary research findings</figcaption></figure><p>We did find a very interesting piece about <a href="https://www.museumsbund.de/wp-content/uploads/2025/03/250320-studienergebnisse-fabien-dmb.pdf">visitor behavior</a> (german museums), curated services from nieche to very broad, accessibility and motivational issues and shifts towards social<strong> </strong>media. With very limited time, we were already able to cluster problems and compare our findings with AI summaries to start working on an online user <strong>SURVEY </strong>we conducted with google docs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GbWf0hJTs_WfMW6UWtlOPQ.png" /><figcaption>Photo: unsplash/Mike Von</figcaption></figure><p>We used the <strong>Lean Survey Canvas</strong> to structure our way to the finished questions, defining what the goals are, what information we already had, who we’d (not) need to learn from and how to reach them — all the way to the actual questionary, from “Hello” to “Thank you”. With the broad problem, it still was a very hard task to come up with potentially useful, ungeneric questions that covered the whole area and not make the respondents shy away from sheer mass.</p><p>But we did manage to get a few participants on board and to get a few quantitative insights out of it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O9wYW1jS2SKxheYJTqRvpg.png" /><figcaption>Photo: unsplash/Hooman R.</figcaption></figure><p>Not having the time to wait for a lot of survey insights, we had to already progress to <strong>USER INTERVIEWS</strong>, again brainstorming individual question ideas, voting and interconnecting them to find a coherent structure and potential insights. Example questions included:</p><blockquote>Reflecting on the last exhibition that really ‘wowed’ you — what was the event and what ultimately convinced you to visit?</blockquote><blockquote>What usually motivates you to visit a museum or cultural institution?</blockquote><blockquote>Now thinking of previous experiences when you decided not to go, could you name and describe one?</blockquote><blockquote>How much does enviroment, company or social interaction influence your decision to visit?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NT4MRqkCWeJpZ4yRDzdXNg.png" /><figcaption>the interview setup</figcaption></figure><p>We did five of those with fix interviewers and one or two note-takers plus auto-transcription (we asked, of course), which proved very helpful for word-for-word quotes. The combination helped to find what you were looking for, AI helped in summarizing key points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KjE6w7Hx5cizTRo09sAdNA.png" /><figcaption>Photo: unsplash/Mimi Thian</figcaption></figure><h3><strong>Define</strong></h3><p>Which led us to the <strong>AFFINITY DIAGRAM</strong>,<strong> </strong>where we extracted all the info that we deemed relevant to then cluster it in groups and label it with common themes and subtopics. Dozens of post-its and four people in one file, the process felt chaotic in the beginning, then fluid and well-organized and democratic in the end. Which is how we also finished it — by dot-voting for the problems we were most eager to tackle. We might have gone on an unnecessary detour there, second-guessing the vote and combinations we had arrived at, but it felt like a very important step and I guess there isn’t that much wrong about taking a step back and discussing in a constructive fashion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*utr7u4nkdWkCpLviPt84gA.png" /><figcaption>Photo: unsplash/Hasibul Hasan</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ecWzQ5H35MZ9VpGrcdA7Eg.png" /></figure><p>We went with the main problem topics of motivation and discovery in a family context of visits to mainly museums.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vOAXJUrJ_B_JV66XqqTDGA.png" /></figure><p>In the end I think we were all happy with the result and doing the next two tasks individually sure gave us a bit of time to catch our breaths.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yzz6gTYsE8scAAero7IaFw.png" /></figure><p>Which were our first How Might We (<strong>HMW</strong>) questions and an <strong>EMPATHY MAP</strong>. I like the HMWs especially, as they give me a way to come up with different angles to a problem in a very mathematical, yet creative fashion. The Empathy Map helped on our way to creating one of the center-pieces, our Primary <strong>PERSONA</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OKVaryt7vMmvH-iFpWtRBQ.png" /></figure><p>Built from actual insights and the team being fairly aligned by now, we were quick on building individual Persona pieces and then discussing, combining, refining them into “curious expat mom” Johanna — a mid-30s mother of two from Germany, who recently moved to Madrid, Spain and struggles to keep culturally connected for herself and her children.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7OT1uEGdPnF5iz5-qYcTfw.png" /><figcaption>Photo: pexels/Ron Lach</figcaption></figure><p>Johanna then took us on her <strong>USER JOURNEY</strong>, where we imagined a museum visit from hearing about it up until visiting and reflecting about it.</p><p>I struggled a little bit with connecting to my creativity at this point, but luckily my teammates were very active and we could quickly work on a mashup of all ideas, which is when I could realign with it and it felt like a good flow again — four people pushing in the same direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g5ZO0FuB3mX8fY0v-KU2EA.png" /></figure><p>This way we could identify two main opportunities, as Johanna struggled researching about the exhibition’s family suitability and as she was not able to fully enjoy the visit having to take care of her two children.</p><p>Thus, we arrived at the final part of definition, the <strong>PROBLEM STATEMENT</strong>.</p><p>At this point, I focused more on the experience while en route to and attending the visit, but the team pushed more towards the discovery and research phase of the visit. Which was okay, of course, and we planned on not losing sight of that later part of the journey. This is the final statement:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PesVlCN6MXJZbvldyGzyXA.png" /></figure><h3>Ideate</h3><p>As we were now on a very narrow path having defined the actual problem we wanted to tackle, we allowed some time for another <strong>HMW</strong> session to begin our ideation process and finally burst out some ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*scYV0cnSv80PRsLLyrLv6Q.png" /><figcaption>How might we? Me on the far right with my Schnitzeljagd.</figcaption></figure><p>Finding good ideas everywhere, we soon proceeded to our first <strong>CONCEPT SKETCHES</strong>. With tail wind from the HMW discussion, I focused on what we called the “Tour Buddy” feature — a part of the app, that was supposed to focus on the drive to as well as the actual visit:</p><ul><li>giving audio/text information adjusted to children and adults in multiple languages, asking questions you can keep in mind and answer afterwards</li><li>letting children color outlines of a painting they can later find and compare</li><li>a painting face swap feature</li><li>restylings of a photographed painting in different art styles using AI</li><li>a log to keep memories well-sorted</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LY_1YN7XNDK9EgqUaxo2AA.png" /><figcaption>My first concept sketch</figcaption></figure><p>But from the get-go this was supposed to probably be a feature of a larger app — one for finding and booking events, connecting with other people and especially catered for those with children. All-encompassing but still lean and easy to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vtup4EPfSlg63TVclvLuqA.jpeg" /><figcaption>concept sketches, comments, votes</figcaption></figure><p>And we went with Johar’s approach, finding good, good stuff in everyone’s and agreeing to be picking up and swapping this and that feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pjuNGto8E-6H0t4A_YmGXQ.png" /><figcaption>Johar’s beautfiul sketch, from signing up to completed booking</figcaption></figure><p>But first, as we were on a tight schedule, we needed to test it on outside people and each of us did an interview to get more opinions on the concept and features that were missing, not completely thought through, a bit too much or simply made you stumble.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WtSSbK6C96v8g5KNuXrkhw.png" /><figcaption>Gathered insights from our tests</figcaption></figure><h3><strong>Prototype</strong></h3><p>Together with our own thoughts and ideas, we were eager to build our first wireframe and then maybe a prototype, but first we made a happy path <strong>USER FLOW</strong>, deciding on the path through the app we would like to illustrate first and finalizing the number of screens and actions we would need for that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FxMwNierYVziavrpBoEFyA.png" /></figure><p>So after knowing our happy path through the app, we knew what screens we had to design to set up first <strong>WIREFRAMES</strong>. No colors, no images, nothing that would visually distract from the functionality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4bt9FIGA-v3GOYZY9k-rXQ.png" /><figcaption>Luisas wireframe draft</figcaption></figure><p>While André and I worked on the presentation at Ironhack, Luisa and Johar already set up an interactive <strong>PROTOTYPE</strong> that we could show as a video in the presentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qnt53DZWVsfCP0DNgg45Qw.png" /></figure><p>But please! Go and try the happy path prototype yourself! Either click <a href="https://www.figma.com/proto/qoyTPHpLMvvMAtNWLR8PEW/Team-4---Culture-and-Heritage?page-id=5607%3A2&amp;node-id=5663-4114&amp;m=draw&amp;scaling=contain&amp;content-scaling=fixed&amp;starting-point-node-id=5607%3A3&amp;t=oxq9nP36TctJEb1M-1">here</a> or follow the QR with your phone:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/74/1*4F0AMTm9ONQSrRAGV44dHw.png" /><figcaption>go try me :)</figcaption></figure><p>But do come back for more!</p><h3>The non-digital component</h3><p>Our prototype was set up, but we did need and want to include a non-digital component, too. Something you could touch, see, experience at the museum itself, which would somehow be connected to the app but would be able to work on its own, too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-leGO6QSfg6u1Vio5r3Ozg.png" /><figcaption>The treasure hunt, Photo: unsplash/Ben Wicks</figcaption></figure><p>Which is where the Tour Buddy feature comes back into play. Once the visit is booked, you can access a <strong>treasure hunt</strong> — Schnitzeljagd as we say in Germany. There’s info you can get beforehand and creative games customized to the exhibition, but the main part happens on the day itself, when children can explore the exhibition or museum on a completely different level from the adults — searching for clues in paintings, sculptures, architecture and texts, having coloring corners or challenges connected to the actual paintings and being able to collect and connect it all with the app or in an own art passport.</p><p>Further down the road, there could be collectibles like pins or buttons, interconnecting the art world in a gamified, fun way for children.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8whRpS1IqCNaOThp7apTzQ.png" /><figcaption>Photo: unsplash/Lucas Alexander</figcaption></figure><h3>Learnings</h3><p>It was a very extensive process we stuffed into less than one and a half weeks here at the start of Ironhack bootcamp (and by far not the only thing we did in that time) and an ungrateful problem to try solving a small part of. And of course the goal was to continuously move forward without going into too much detail or getting stuck on things that would’ve needed more attention. To get into a flow, get familiar with part of the toolbox, work as a team and learn trusting the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KmWJ8ktZ-LpQlN7vJx_C0g.png" /><figcaption>Photo: unsplash/George Dagerotip</figcaption></figure><p>One of our main learnings was the simple fact that we are not the user. That we need input, be it secondary or primary research, survey or interview, testing and testing and testing and circling back and failing fast.</p><p>And also in that regard, that we should neither be designing for us nor for everybody. Focusing on one problem, one persona, one product was almost the only way possible to end up with anything coherent.</p><p>And the widening and focusing of the double diamond schematic — reaching out in every research direction, then focusing on the insights until we have but one sentence left, then letting loose of ideas to spread in all corners and finally letting only the right stuff flow into one concise product.</p><h3>Thank you</h3><p>for reading this far, for your interest and openness to weird, weird wicked problems.</p><p>Thank you to the team, it’s been a pleasure and an intense one! And thank you, Ironhack. It’s been an intense pleasure.</p><h3><strong>Stay in contact</strong></h3><p>In case you want to say hi or stay connected, do the thing.</p><p>And please feel invited to my portfolio website at <a href="http://www.mathishanspach.de/">www.mathishanspach.de</a>. It’s mostly cinematography, photography, illustration right now, but that may soon change a bit and possibly isn’t the most boringest to look at either.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ySXsBSJgcD5dqUYDiOkQlQ.jpeg" /></figure><p>Thanks again and bye bye!</p><h3>tl;dr</h3><p>We fixed that culture problem thing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a50be57e508c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenge 2: Wireframing NABU world of birds app]]></title>
            <link>https://medium.com/@mathishanspach/challenge-2-wireframing-nabu-world-of-birds-app-b14986de4dea?source=rss-e8881e264dd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/b14986de4dea</guid>
            <dc:creator><![CDATA[Mathis]]></dc:creator>
            <pubDate>Sun, 11 Jan 2026 09:13:54 GMT</pubDate>
            <atom:updated>2026-01-11T09:13:54.618Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JMMuOpP9iBvpLxA4CzthiQ.jpeg" /></figure><p>Have you ever just wanted to be sure about the difference between the tiny, tiny firecrest and the goldcrest or wanted to listen to some of the magpie’s different songs (it is a singing bird)?</p><p>No? Hm. Well, I have! As tens of thousands of my fellow bird nerds in German speaking countries.</p><h3>The app, the wireframe</h3><p>That’s where the app NABU Vogelwelten (world of birds) comes in. It’s not the only bird app by far and not the only one I use (there’s three on my first screen…), but it’s a great overview library of ornithology in all its different areas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zSoIoXRnKn6M1IdGzqssJQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fdTnUWxbtwiJqf1Hs4m87g.png" /><figcaption>home screen — screenshot vs. wireframe</figcaption></figure><p>Even using it rather regularly, dissecting and reverse engineering the app into a wireframe was the first time I looked at it structurally, from a distance and it was quite a ride.</p><blockquote>Here’s a <a href="https://www.figma.com/proto/RgsZE2n9tPdIuzWpmIG9iC/exercises?page-id=42%3A436&amp;node-id=42-441&amp;p=f&amp;t=mwgRI1H83B7hhcxm-0&amp;scaling=contain&amp;content-scaling=fixed&amp;starting-point-node-id=42%3A441">link</a> to the interactive user flow I reconstructed using Figma.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p_5rO2QpzF-zH-MBls7uIA.png" /><figcaption>five slides already make for quite a flow</figcaption></figure><h3>Design thoughts</h3><p>First, I found some inconsistencies from a visual perspective, but the deeper core is well-designed and the flow works. On an intermediate level, there’s some extra functions that seem like afterthoughts glued where there’s space available.</p><p>I am especially missing a consistent header navigation — only sometimes there’s a home button, sometimes a secondary function. The footer’s functions vary in the flow, too, but there’s a lot to cover in the different orni-areas and it looks rather well-thought-out.</p><h3>Experiences</h3><p>Wireframing was fun and quite a bit eye-opening to how simple (not simply) an app can be broken down and what blocking out details or visuals altogether can give you — a lesson I know from painting, too. There sure is a lot, lot, lot to learn for me here, but with my web design experiences, app design suddenly feels a bit managable.</p><p>From a Figma-point of view, the project taught me a lot of basics and my InDesign+Illustrator skills definitely helped a lot. I felt quite at home from the get-go and am eager to dive deep into the program. I’m looking forward to complex user flow building, user collaboration and prototyping especially.</p><p>Let’s go and all the best,</p><p>Mathis</p><p><a href="https://www.figma.com/proto/RgsZE2n9tPdIuzWpmIG9iC/exercises?page-id=42%3A436&amp;node-id=42-441&amp;p=f&amp;t=mwgRI1H83B7hhcxm-0&amp;scaling=contain&amp;content-scaling=fixed&amp;starting-point-node-id=42%3A441">figma</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b14986de4dea" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>