Marius C.

I design interfaces engineers can build, and I stay involved until they ship. I'm a UI/UX designer working across SaaS products, mobile apps, and embedded touchscreen devices. Most of my projects run alongside development teams, so I design with real components, technical constraints, and timelines in mind, and I hand off files ready for implementation. WHAT I DO - UX design: research, user journeys, information architecture, wireframes - UI design: SaaS dashboards, mobile apps, and embedded touchscreen (HMI) interfaces - Design systems: token-based Figma libraries (variables, components) that map 1:1 to code - Prototyping: interactive Figma prototypes and working coded prototypes built with AI-assisted tools - Handoff and build review: UX specs, component states and design QA on the real product SELECTED WORK - Embedded touchscreen HMI for a laboratory instrument Lead UI/UX designer for a dual-channel lab instrument running on hardware with very little graphics memory, where every font size and icon had a cost. I wrote the UX spec before drawing a single screen, then designed landscape and portrait layouts in dark and light themes on a token-based design system that engineers implemented directly. Every phase passed the client's acceptance reviews, and final build reviews came down to spacing details. - JustEnergy: energy-market analytics SaaS, web and mobile Lead UI/UX and brand designer for an app that tracks electricity production, consumption, and cross-border exchange across European countries. The app was already built, so I redesigned it within the existing product: a new brand identity and logo, a design system based on it, and a responsive dashboard for desktop and mobile in light and dark themes. Key features include an interactive country map, time-range filters, production by energy source, 5-day forecasts, and drill-down detail views. The client called it "extraordinary work" with a very good understanding of the subject. HOW I WORK 1. Write before I draw: user journeys reviewed with your team first, so scope is settled while changes are cheap 2. Design to the constraints: platform, screen size, performance, and development effort set the rules before visual style 3. Build on a system: semantic tokens and components, so a change happens in one place 4. Stay through implementation: I review builds against the design and give precise, actionable fixes TOOLS Figma (Variables, Components, Auto Layout, Dev Mode), written UX specs, HTML/CSS, SVG Web Animations API (element.animate), AI coding tools (Claude) Tell me what you're building and where you're stuck. I'll reply with how I'd approach it.