Toronto · Open to senior rolesAbout

Daniel Boeppler

Founder, Softcode · Senior Product Designer

I design product systems, SaaS experiences, and data-informed interfaces for teams that need digital products to feel useful, usable, and ready to ship.

Bio

Design work with product depth.

With over nine years of professional experience in UX/UI design, I focus on creating innovative and user-friendly digital products. As the Founder of Softcode, I use product design, Hotjar, and design-system thinking to shape solutions around real client needs.

Previously, as Lead UX/UI Designer at mimik, I directed the design and development of applications, web platforms, and dashboards. That work connected product design with business strategy, using data-driven insights to improve usability and make digital interactions easier to use.

I have also built tech-focused businesses around SaaS products, which keeps my design practice close to the realities of product development. Those entrepreneurial experiences help me think beyond screens: market fit, customer value, delivery, and the systems a product needs in order to grow.

Currently

What I’m looking for now.

Open to senior UX/UI, product design, and founder-minded consulting work, especially with teams building SaaS products, dashboards, healthcare platforms, and complex digital services.

Start a conversation
How I work

Four principles that show up in everything I ship.

Taste isn’t a mood — it’s a set of repeatable decisions. These four show up in every project on this site, from healthcare dashboards to brand campaigns, and they’re how I keep the work consistent across teams, surfaces, and timelines.

  1. Structure

    Structure before surface.

    Information architecture is the chassis. I make sure the hierarchy, navigation, and primary jobs are right before I touch a single colour or shadow. A clean visual layer over a tangled IA still feels broken — the cleanest gradient on the wrong screen is still the wrong screen.

  2. Defaults

    Calmly opinionated defaults.

    Ship sensible defaults that 80% of users never need to change. Settings, customisations, and toggles are an escape hatch — not the headline. When I design a system, the un-configured state is the design, not a placeholder waiting for the user to make it work.

  3. Motion

    Motion that earns its frame budget.

    Animations exist to explain state change, not to entertain. Every transition has a job — orient the user, hint at causality, fill perceived load time — and gets a specific duration, easing, and origin. Anything that drops below 60fps or doesn’t serve comprehension gets cut.

  4. Accessibility

    Bilingual and accessible by default.

    Designing in Toronto means EN/FR parity isn’t a phase-two requirement — and WCAG AA isn’t a checklist someone runs at the end. Type scale, focus rings, contrast ratios, and translated string lengths all live in the system from day one, so the design ships ready instead of getting retrofitted.