# Viktor Peschka — UX/UI Designer & Developer I design and code, ship fast and iterate. Proactive. Pragmatic. Detail-driven. Currently open to work. Website: https://viktor.peschka.com Email: viktor.peschka@gmail.com LinkedIn: https://linkedin.com/in/viktorpeschka X: https://x.com/viktorpeschka --- ## Experience **UX/UI Design Lead — YouSir** (Feb 2024 – present) SaaS Design Studio **UX/UI Product Designer — Laborpont** (Dec 2022 – Jan 2024) Preventive Healthcare Provider **UX/UI Product Designer — Storyteq** (Dec 2021 – Nov 2022) Marketing Automation Technologies **UX/UI Designer & Developer — Trans–Europe** (May 2018 – Dec 2021) Official Adobe & Wacom Distributor --- ## Selected Work ### Launching an App That Rethinks Habit Tracking Through Simplicity iOS App Design and Development https://viktor.peschka.com/case/launching-an-app-that-rethinks-habit-tracking-through-simplicity Project: Simply Habits, an iOS habit tracker and daily planner Problem: Habit trackers had become bloated, paywalled, and overconfigured. The category had optimized for features over the actual habit of building habits. Role: Solo designer and developer, from concept to App Store Outcome: Shipped to the App Store and actively iterating based on real usage **The Problem** The App Store is full of habit trackers. It is also full of complaints about them. Reddit threads, App Store reviews, and forum posts tell a consistent story: apps that started simple became bloated over time, basic features got locked behind subscriptions, and onboarding flows began to feel like configuring software rather than starting a habit. The frustration was not with habit tracking as a concept. It was with what the apps had become. The market had a clear, repeated signal and nobody was acting on it. Nothing fit. So I built one myself. **The Design Philosophy** The central question I kept returning to was: what decisions can I make for the user so they don't have to make them? User feedback across reviews and communities pointed to the same friction points: too many options upfront, too much setup before the app was useful, too many choices that didn't matter. That shaped every design decision. Instead of exposing every SF Symbol in existence, I hand-picked icons and grouped them into themes. Instead of an RGB color wheel, I offered a curated palette. Instead of account creation, onboarding takes five seconds with no signup required. Each of these looks like a small decision. Together they add up to an app that doesn't demand anything from you before it's useful. **What I Chose Not to Build** A lot of habit trackers lean into gamification: achievements, streaks with consequences, or abstractions where your habits become a village you're building and neglected habits cause trees to die. It is easy to see the appeal, and reviews of those apps show initial excitement. But the longer-term feedback tells a different story. The game layer becomes the thing people manage. They end up tending to a virtual village instead of building a real habit. Gamification works when a system enforces the rules. Habit tracking is entirely self-governed. Nobody is making you open the app. Simply Habits is almost boring by design. It gets out of your way. No rewards for opening it, no punishment for not. Just a clear view of what you set out to do and whether you did it. **Where Restraint Has a Limit** Simplicity is a principle, not a rule to follow blindly. The color palette launched with 16 options. Within weeks, the feedback was consistent: users wanted more. The constraint had crossed the line from helpful to frustrating. I expanded it to 40 colors and shipped the update within days. The palette is still curated, still intentional, but it now respects the fact that personalisation is part of what makes a habit feel like yours. That distinction matters: restraint should reduce friction, not create it. **The Result** Simply Habits is live on the App Store. Designing, building, and shipping a complete iOS product solo meant every decision, from interaction detail to production code, was intentional and consistent. But the more important proof is in the product itself. The best interface is the one that disappears. When an app stops asking anything of you and just reflects what you set out to do, it has done its job. Not with rewards, not with abstraction, not with a game layered on top of your life. Just clarity. App Store: https://apps.apple.com/app/simply-habits-habit-tracker/id6747362624 --- ### Redesigning a B2B SaaS Platform Without Disrupting Enterprise Users Visual Identity & Design System https://viktor.peschka.com/case/redesigning-a-b2b-saas-platform-without-disrupting-enterprise-users Company: Storyteq — Creative automation platform for marketing at scale Clients: Heineken, McDonald's, KFC, Henkel, Mars, and more Challenge: Architect an enterprise design system from scratch without disrupting complex workflows that enterprise clients depended on daily Role: Sole owner of the design system: visual language, component library, and standards across 3 platforms. Impact: Redefined brand identity, established consistency across a complex product, and shifted team culture from developer-led processes to collaborative, user-centric thinking **The Challenge** As Storyteq grew from startup to scale-up, the product showed its origins. Inconsistent UI patched together over time, with no coherent system underneath it. The stakes were high: enterprise clients like Heineken and McDonald's relied on complex, niche workflows every day. A disruptive overhaul wasn't an option. The system had to evolve without pulling the floor out from under them. Constraints: - Product already in market with paying enterprise customers - Complex, niche workflows that couldn't be disrupted - Had to maintain core experiences that were working The constraint that shaped every decision: "If something works, don't break it" **Shifting How the Team Worked** Before I joined, design and engineering worked in sequence: designers solved, developers built. Problems stayed siloed. Decisions got made without the people who'd implement them. I ran collaborative sessions that brought both disciplines into the same room and eventually the same desk. Designers and developers attended the same meetings, worked through the same problems together. Every new challenge became a shared one. This wasn't just a process change. It increased design maturity across the team and created a culture where feasibility and user needs were considered together from the start, not after the fact. **Research & Validation** I used Hotjar to map common flows and user behavior across the platform, validating assumptions with real usage data before making design decisions. This was especially critical given the constraint: I needed to know what was actually working before deciding what to change. **Introducing Consistent Patterns** Rather than rebuild from scratch, I introduced consistent patterns that made the platform more learnable across its complexity. One key pattern I established was the "control strip", a top bar on overview pages that standardized navigation, version control, and primary actions across the app. One pattern, applied consistently, made the whole product feel more coherent. **A Deliberate Visual Direction** The visual direction was contested. The obvious path was a friendly, approachable aesthetic, rounded corners, soft tones, the look most of our competitors had already adopted. It tested well with general audiences and felt safe. I argued against it. Storyteq's users weren't general audiences. They were marketing teams at Heineken and McDonald's running hundreds of campaigns simultaneously. What they needed wasn't warmth. They needed precision, clarity, and a UI that got out of their way. I pushed for a flat aesthetic with 0px corner radiuses and a strict 10px spacing grid. Every edge aligned perfectly. Far from alienating enterprise users, the tightness of the system matched how they actually worked. It gave the platform a distinct identity that reflected the seriousness of the work happening inside it. **The Impact** The design system redefined Storyteq's brand identity and established visual consistency across a complex, multi-platform product without disrupting the workflows enterprise clients depended on. Beyond the system itself, the team left the project working differently. Design and engineering were no longer two separate phases. They were one process. --- ### Building a Scalable Product Website and Designing Constraints to Protect Consistency Website Design & Frontend Development https://viktor.peschka.com/case/building-a-scalable-product-website-and-designing-constraints-to-protect-consistency Company: Trans Europe, official distributor of Wacom and Adobe in Central Europe Challenge: Outdated site, expanding product lineup, and a brief that turned out to be asking for the wrong thing Role: Solo designer and frontend developer, collaborating with a backend developer Impact: Launched a cohesive, scalable site that a non-technical team could maintain independently from day one **The Brief vs The Reality** The original brief pointed toward a straightforward e-commerce site. A product catalog, a way to buy, the standard approach for a distributor. Before committing to that direction, I spoke with the customer support and sales teams who worked with actual users every day. What they described was a more complex picture. Users could not buy directly. The site needed to educate and guide purchase decisions without completing them. And the audience was not just consumers: partners and resellers needed it as a resource to keep their own sites current. The research reframed the entire project. Not less work, but fundamentally different work. **Designing for Three Audiences** Three distinct audiences, one site. The navigation had to route each of them to what they needed without making any of them feel like a secondary consideration. - Partners and resellers landed on a dedicated section with downloadable product specs, press materials, and the latest product information, everything they needed to keep their own channels current without contacting anyone. - Potential buyers were guided through product overview pages structured to educate first: use cases, comparisons, and detailed specifications to support a confident purchase decision, even though that decision would happen elsewhere. - Existing customers could reach drivers, firmware, and documentation directly, without navigating through product marketing that was irrelevant to them. Each path was clear from the homepage. The goal was that none of the three audiences would ever feel like they had arrived at the wrong site. **Defining the Visual Direction** Wacom's own brand is playful and expressive, built around hand-drawn illustrations and a consumer-facing warmth. Aligning with that was the obvious starting point, and we considered it seriously. I pushed for a different direction. This site was not primarily a consumer portal. It served three audiences simultaneously, including partners and resellers who needed to extract accurate technical information efficiently. A playful, illustration-led aesthetic would have signaled the wrong thing to two of the three people arriving at the site. The direction I argued for was clean, spacious, and precise. Generous white space, minimal ornamentation, and product photography carrying the visual weight. Clear over expressive. The products were the most compelling thing on the page, and the design had to get out of their way. **Designing the Constraints** The marketing team responsible for maintaining the site were often students on summer placements. They needed to create and update product pages without any design or development support. I proposed a modular template system with intentional constraints built in: locked section order, enforced image sizing, automatic image positioning, and consistent backgrounds. The team pushed back. They wanted creative freedom, the ability to make layout decisions themselves and adapt pages to individual products. It was a reasonable argument. I pushed back harder. Creative freedom without design knowledge produces inconsistency. Every page would drift from the last depending on who built it and what mood they were in that day. The constraint system was not there to limit them. It was there to make the right result achievable by anyone, without studying the system or second-guessing decisions. They would not need to think about image positioning because the system would handle it. They would not need to judge section order because it was already determined. The structure was the support. They came around. And once they started using it, the original objection disappeared. **The Impact** The site launched with a cohesive visual identity and a system that worked without a designer in the room. Within days, the marketing team had independently created over 40 product pages, uploading all content themselves without design or development support. Before this, updating the site required contacting a specific backend developer and waiting. After, the team had full autonomy over the product catalog. The constraint system did exactly what it was designed to do: it made the right output the only output. --- ### How I Turned a Repetitive Design Task Into A Single Click with a Custom Plugin Figma Plugin Design and Development https://viktor.peschka.com/case/how-i-turned-a-repetitive-design-task-into-a-single-click-with-a-custom-plugin Project: Add Section, a Figma plugin for creating and maintaining sections with consistent padding Problem: Figma's section tool lacked custom padding control, making proper file organization too slow to bother with consistently Role: Solo designer and developer Impact: Approved on Figma Community, adopted by the team, and turned a task people were avoiding into a single click **The Problem** I organize Figma files by wrapping flows in sections with consistent padding: 500px around individual flows, 1000px around the groups that contain them. It keeps large files navigable and readable for anyone who opens them. The problem was doing it properly took 10 to 20 seconds per section. Figma wraps selections in a new section with a fixed padding you cannot control, and since sections do not support auto-layout, every adjustment meant manual resizing. Across a large file, the cost compounded fast. The team felt it in two different ways. Some people absorbed the cost and spent the time, manually nudging sections into place every time content shifted. Others decided it was not worth the effort and left sections inconsistent, different padding here, a skipped section there. Neither was a good outcome, and the two groups kept running into each other: the ones who cared about consistency were regularly cleaning up after the ones who had given up on it. The friction was small enough to seem trivial and large enough to quietly damage the quality of every file the team shared. **The Solution** I built a Figma plugin that does exactly one thing well: add a section around any selection with custom padding. 1. Select any elements, including frames, rectangles, or other sections 2. Set your desired padding, horizontal and vertical independently 3. Click "Add Section" to wrap the selection precisely It also works on a single selected element, which Figma's native function does not support. That detail mattered more than it sounds: a lot of the sections I was creating started with a single frame. **What I Learned by Using It** Once I started using the plugin daily, I realized I had solved the wrong half of the problem. Creating sections was faster now. But maintaining them as designs evolved was still painful. Every time content shifted, sections needed resizing, and that was still manual. I had built a tool for the moment a section is born. The harder problem was everything that happened after. **The Second Feature** I added a resize function based on that insight. Select one or more existing sections, set the desired padding, and the plugin recalculates and resizes all of them at once, consistently. That is the part that made it genuinely useful rather than just convenient. A file stays consistent not at the moment of creation but across every change that follows. **The Impact** The plugin was approved on Figma Community and adopted immediately by the team. What had been a task people quietly avoided became a single click. But the more useful outcome was the one you cannot see: the files got cleaner. Not because anyone tried harder, but because the right behavior became the easy behavior. Figma Community: https://www.figma.com/community/plugin/1500130125545579676/add-section