Skip to content

Product designer Design engineer

Martyna Wójcik

I design software, but my background is in code. Over the last seven years, I've learned that the best products happen when you understand both sides. My goal is always the same: to solve a problem. Whether it's geospatial software, a complex dashboard, or a completely new app, I enjoy being involved from the first sketch straight through to the finished product.

Selected work

Things I've designed and built

Yaca Properties

Live partner testing

Marketplace architecture · B2B SaaS

A property marketplace connecting agency credibility, real-world listing feeds, and neighborhood context through responsive map search.

View case study
Yaca Properties desktop property cards, search filters, and linked price markers
Yaca Properties mobile listing cards with prices and essential specifications
Yaca Properties: desktop and mobile property search.

Yaca Places

Live community beta

Community local discovery · Vector maps

A community-curated guide to local places, with vector maps, moderated contributions, and shareable neighborhood lists.

View case study
Yaca Places desktop discovery with local cards and a neighborhood map
Yaca Places mobile map and nearby places in Lisbon
Yaca Places: desktop and mobile neighborhood discovery.

Unloops

Live PWA

Behavioral product design · React & AI

A CBT-inspired habit app designed to help people pause during urges, prepare for triggers, and reflect after setbacks.

View case study
Unloops urge check-in with an intensity scale
Unloops timed pause with a reminder and helpful action
Unloops: check in with an urge, take a timed pause, and practice guided breathing.

My approach

Designing for High-Density Systems

  • 01 // Information architecture

    Structuring complex data

    I spend a lot of time organizing layered maps, dense filters, and real estate feeds. The goal is always to give people access to all the data they need without overwhelming them. You should be able to explore complex systems and still feel in control.

  • 02 // Reducing overload

    Designing to reduce overload

    Nobody likes a screen that throws twenty different decisions all at once. I do my best to keep interfaces simple by revealing details step by step as you need them. And because people always remember the hardest moment and the finish line, I put the most care into smoothing out the toughest steps so finishing feels effortless.

  • 03 // Design & code

    Mixing design & front-end

    Thanks to my front-end background, I know the memes about over-designed dark mode toggles are real, and Dribbble shots rarely survive actual production data. You have to think carefully about how a system behaves before you start drawing it. Around 80% of the work is logic, edge cases, and system behavior. The UI in Figma is just the final 20%.

Tools & methods

UX & product

  • User flows
  • Information architecture
  • Research

UI & systems

  • Figma
  • FigJam
  • Design systems
  • Design QA

Frontend & delivery

  • HTML/CSS
  • React
  • Next.js
  • Material UI
  • Git

AI-assisted prototyping

  • Google AI Stack
  • Gemini
  • Codex
  • OpenCode
  • ChatGPT
  • Claude