Helsinki, Finland Product design, end to end Web and mobile Open to product roles
I turn complex ideas into clear, complete digital products. Not just how a product looks, but how it behaves when the easy path is not the one a person takes.
01of 06
Concept redesign for a Paris architecture practice
Investors in London, Munich and Dubai could not read the practice’s French site and decided in a minute, on a phone. One English page now shows scale, proof and a real before and after before the first scroll ends. First load 418 KB, one pinned section.
Website redesign for a biotech company fighting antibiotic resistance
A biotech’s mechanism needs a paragraph to explain, and investors give it a minute. I kept every word of the company’s content and rebuilt the order around the argument. Thirteen pages and a design system with its own specification.
E-commerce redesign: a plant shop built around the room, not the species
Plant shops sort by species names nobody remembers. I rebuilt the catalogue around light, space and pets, with care facts beside the price and delivery cost before the first form field. Eighteen screens, desktop and mobile.
Personal finance app that shows what is actually safe to spend
Your balance is not what you can spend: rent, bills and goals have already claimed part of it. The app shows the safe number first, then your buying habits, without judging. Flows, rules and first screens are done.
Gift planning app where the list owner never learns who reserved what
The person who made the list must not see who reserved which gift. That one rule shapes the data, the permissions and every state a guest can be in. Owner and guest views are designed.
Habit app for children, with a parent mode and a child mode
Helps children build habits without feeling bad about a missed day. A parent sets tasks and the reward; the child sees only today and collects stickers toward it. Two interfaces on one set of data.
About
I'm Tanya.
I design apps and websites.
I started with websites, working on my own for clients: someone would come with a rough idea, and my job was to turn it into something that made sense, then make it look right.
At some point the part I liked best stopped being the page and became the product. What is this for. Who opens it. What happens when someone does something I didn't plan for. So now I do the whole thing: structure, flows, screens, and a prototype you can click.
What I do
Product design
UX and interface design
Information architecture and user flows
Design systems and components
Prototypes you can click
Websites, mobile apps, SaaS
How I work
01
Understand
Who it is for, what it has to do, what gets in the way. I look at competitors and real user tasks, and I say out loud which parts are still assumptions.
02
Break it down
Functions, roles, data and scenarios. I decide what belongs in the first version and what can wait, and I argue for cutting scope when cutting helps.
03
Structure
Information architecture, user flows, permissions, states, rules and the edge cases nobody thinks about until one of them breaks something.
04
Design
Visual direction, grid, typography and components in Figma. Responsive from the start, not adapted afterwards.
05
Prototype
I build a working version with Claude Code, then rewrite the parts the first attempt got wrong. Getting there is quick now. Deciding what is wrong is still the job.
06
Hand over
Specs for developers, then checking that what shipped matches what was designed, down to spacing and behaviour.
Tell me what you are building. I read every message and write back myself.
Your message is on its way. I will reply to the email you left.
malinovska.design