Product

Product Design · Fintech / Brokerage

FXTrading.com: Investment & Trading Platform

A mobile app and a copy trading dashboard for a leading Australian brokerage making high-density financial data genuinely usable on mobile without losing the depth traders depend on.

Role
Product Designer
Year
2021 - 2022
Industry
Fintech · Forex / CFD Brokerage
Deliverables
Mobile UX · Dashboard Design · Information Architecture · Design System · User Flows
Overview

FXTrading.com is an Australian brokerage offering retail forex and CFD trading to individual investors — from complete beginners to experienced traders. I was brought in initially as a freelance consultant to solve mobile UX problems. After delivering that work successfully, I was retained to lead two larger projects: the complete mobile platform build, and a copy trading dashboard designed entirely from zero.

FXTrading.com App case preview1
Mobile welcome screen
The Challenge

The company had a fully built web trading platform - complex, data-dense, feature-rich. The mobile experience was the problem. The web platform had been compressed onto a phone without rethinking what mobile users actually needed: multiple data panels, real-time charts, complex navigation, and detailed portfolio views all visible at once. The result was overwhelming, difficult to navigate, and not suited to how people actually use a trading app on the move.

The core challenge: take a platform with this level of data complexity and make it genuinely usable on mobile without removing the functionality traders depend on.

FXTrading.com Web case preview1
Web platform login
FXTrading.com Web case preview2
Web dashboard overview
FXTrading.com Web case preview3FXTrading.com Web case preview4
Onboarding screens
FXTrading.com Web case preview5
Copy trading discovery
FXTrading.com Web case preview6FXTrading.com Web case preview7
Deposit methods
ElevateOS
2023
White-Labeled Residents App
Go to Next Project
My Approach
1
Rethink the IA for mobile behavior
I mapped every feature on the web platform and asked the same question for each: what does a mobile user actually need from this, in this context? Trading on a phone is a different behavior: users check positions, monitor prices, and make quick decisions; they don't sit and conduct deep analysis. High-priority actions -checking open positions, placing a trade, account balance, depositing funds were brought forward in the navigation. Complex analytics and detailed reporting stayed accessible but out of the primary navigation.
2
Adapt the existing design system
Rather than starting from scratch, I adapted the web platform's design system for mobile keeping visual consistency between web and mobile while redesigning how information was structured and prioritized at a smaller scale. This preserved brand recognition across platforms while solving the layout and hierarchy problems.
3
Research copy trading before designing it
When retained for the copy trading dashboard, I had requirements and user stories but copy trading has its own domain logic I needed to genuinely understand first. I researched how it works from every perspective: how traders earn when others follow them, how followers deposit and allocate funds, how performance is measured, what a new follower needs to evaluate a trader, and how the system handles withdrawals without disrupting open copied positions. Only with that understanding did I start designing so every decision was grounded in how copy trading actually works.
Information architecture restructure web navigation adapted for mobile usage patterns, high-priority actions surfaced, complex analytics moved to secondary access.
The Hardest Problem — Data Density

The most persistent challenge across both projects was data density, how to show real-time financial data clearly on a small screen without losing the information traders depend on. Financial data is inherently complex: P&L figures, open positions, trade history, market data, percentage changes, charts - each piece matters, and removing any of it would reduce the product's usefulness. The solution wasn't to show less; it was to establish clear visual hierarchy so traders could scan the most important information first and drill down when they needed detail.

For the copy trading dashboard specifically, I designed trader profile pages that needed to communicate performance credibly and at a glance because followers make actual financial decisions based on what they read there. The IA of those profiles had to build trust while remaining immediately scannable.

Annotated trader profile design decisions behind the copy trading information architecture
FXTrading.com Web case preview8
Accounts dashboard
FXTrading.com Web case preview9
Support Hub
FXTrading.com Web case preview10FXTrading.com Web case preview11
Performance dashboard
FXTrading.com Web case preview12
Copy trading profile
ElevateOS
2023
White-Labeled Residents App
Go to Next Project
FXTrading.com App case preview2
App preview screens
Mobile home screen
FXTrading.com App case preview4FXTrading.com App case preview5
Stock Overview
FXTrading.com App case preview6
Stocks discovery
FXTrading.com App case preview7
Mobile home screen
FXTrading.com App case preview8
Stocks buying flow
FXTrading.com App case preview9FXTrading.com App case preview10
Notifications hub
FXTrading.com App case preview11
Trading accounts management
Outcome
40+
mobile app screens covering account management, fund flows, the live trading interface, position management, and portfolio analytics.
50+
copy trading dashboard screens from zero: trader discovery, performance profiles, follow and copy flows, and fund management.
Retained
from the initial freelance engagement to lead the full platform build, based on the quality of the first delivery.

Product

Product Design · SaaS / Legal Tech

HubSign: eSignature Platform

A legally binding eSignature platform designed from zero: competitive analysis, design system, every screen, and complete developer documentation.

Role
Product Designer
Year
2025
Industry
SaaS · Legal Tech
Deliverables
Product Design · Information Architecture · Design System · Competitive Research · Developer Handoff
Overview

HubSign is a legally binding eSignature platform, a tool for businesses and individuals to prepare, send, and sign documents digitally. I designed the entire product from zero: competitive analysis, design system, every screen, and complete developer documentation.

Unlike ElevateOS, where I was joining an existing product with existing problems, HubSign gave me something rare: a clean slate and the ability to make every decision intentionally from day one.

Onboarding / Get started
The Challenge

eSignature sounds simple. The product is not. A document signing process involves multiple parties with different roles: the person preparing and sending the document, each person asked to sign it, and the platform managing the legal validity of every signature. Each party needs a different interface, different permissions, and a different set of actions and all of it needs to feel simple for every user, regardless of the complexity underneath.

The goal: design a product where someone could upload a document, assign signature fields up to three recipients, set a signing order, and send it, in as few steps as possible. And where each recipient could receive that document, understand exactly what to do, and sign it without any instructions.

HubSign case preview 2
Pricing / plan selection
HubSign case preview 3
Document dashboard
HubSign case preview 4HubSign case preview 5
Activity history
HubSign case preview 6
Dashboard view
My Approach
1
Competitive analysis
With no existing product to audit, I started by mapping the signing flows of the leading eSignature platforms where they created friction, where they made smart decisions, and what patterns users had already learned. The key insight: most platforms make preparation complex and signing simple. Users were already comfortable signing the real opportunity was the preparation side: reducing the steps to get a document ready to send so the whole workflow felt lightweight start to finish.
2
Design system first
Before designing any flow, I built the design system. Working with one developer, a shared component library meant we could move quickly and consistently no visual debt accumulating as the product grew.
3
Map every state and edge case before building
I mapped every path a user could take. What happens if someone declines to sign? If a link expires? If the sender needs to edit after sending? If one of three signers completes their part but the others don't? Every screen was connected into a working prototype, and every state was designed before a single line of code was written.
Competitive analysis mapping where existing platforms created friction and where HubSign could differentiate.
The Hardest Problem — Multi-Party Signing

The most complex challenge was the multi-party signing flow what happens when a document requires signatures from multiple people, in a specific order, with automated reminders and expiry dates in play. I had to design three distinct experiences simultaneously:

  • For the sender. A clear flow for assigning signature fields to recipients, setting signing order, adding expiry dates, and tracking who has signed and who hasn't.A clear flow for assigning signature fields to recipients, setting signing order, adding expiry dates, and tracking who has signed and who hasn't.
  • For each signer. A simple, trustworthy experience for someone who may have never used an eSignature tool. They receive a link, understand immediately what they're signing, complete their fields, and get a confirmation, no instructions needed.
  • For the edge cases. Every exception state designed and documented before development: declined signatures, expired links, editing after send, partial completions.

The result is an experience that feels effortless on the surface because all the complexity was resolved at the design stage.

Multi-party signing state diagram: designed before development to cover all user roles and exception states.
HubSign case preview 7
Document preparation
HubSign case preview 8
Document configuration
HubSign case preview 9HubSign case preview 10
Account settings
HubSign case preview 11
Document signing summary
Outcome
From zero
complete product designed end to end: design system, all screens, full user flows, multi-party signing logic across every state and edge case, and developer documentation.
Minimum steps
signing workflow designed for the fewest steps from preparation to completion, across all user roles.
Shipped
platform successfully built and launched.

Product

Product Design · PropTech

ElevateOS: Property Hub

The operations dashboard property managers use to run their buildings day to day, the manager-facing counterpart to the Resident App, owned simultaneously as the sole designer.

Role
Product Designer
Year
2023 - 2025
Industry
PropTech · Operations
Deliverables
Dashboard Design · Information Architecture · Design System · User Research · Prototyping
Overview

While the Resident App was the tenant-facing product, the Property Hub was the other side of ElevateOS - the operations dashboard used by property managers to run their buildings day to day. I owned the design of both products simultaneously as the sole designer on the team.

Where the Resident App was about simplicity and findability for residents, the Property Hub was a different problem: giving managers real-time clarity over a large, growing, increasingly complex operational dataset without overwhelming them.

ElevateOS Web case preview1
Property Manager Dashboard
The Challenge

The Property Hub started as a relatively simple booking calendar: a view for amenity reservations and service requests in one place. But as ElevateOS grew and added features, the platform kept absorbing more operational data into that same interface.

By the time I took it on seriously, the dashboard was trying to show everything at once: amenity bookings, maintenance requests, events, resident profiles, integrations, transactions, messaging, and analytics. The calendar (the central operational view) had become the catch-all for the entire platform. It was breaking under the weight.

At the same time, the design files had diverged from the live product. What existed in Figma and what had been built were no longer the same thing making it nearly impossible to understand where the product was or plan where it needed to go.

ElevateOS Web case preview2ElevateOS Web case preview3
Resident profile & activities
ElevateOS Web case preview4
Calendar view
ElevateOS Web case preview5
Login
My Approach
1
Establish a source of truth
Before redesigning anything, I audited every screen reconciling the design files with the live product to understand what was actually built versus what existed only in Figma. Then I rebuilt the design system and wired every screen into a navigable prototype. Before me, the files were isolated frames with no connections; I connected them so engineering, PMs, and the CEO could walk through the actual product experience for the first time. It changed how the whole team communicated about the product.
2
Observe property managers in context
I joined sessions where managers used the platform live working through their real daily workflows, flagging what was confusing. My role was to observe rather than lead: watching where they hesitated, clicked the wrong thing, or muttered when something didn't work. The consistent finding: managers needed to understand what was happening right now, today, at a glance. Detailed historical analytics mattered far less than operational clarity in the moment.
3
Restructure around operational priority
Using the same approach as the Resident App,  analyzing usage patterns and observing real behavior, I restructured the dashboard's IA around operational priority. What needed action today was immediately visible. Everything else (detailed analytics, configuration, historical data) was organized into secondary views that didn't compete for primary attention.
First connected prototype built for the team, previously all screens existed as isolated frames with no flow between them.
The Hardest Problem — Redesigning the Calendar

The central challenge was the calendar which had grown from a simple scheduling tool into the most complex screen in the entire platform. It was simultaneously showing amenity bookings, maintenance status, event schedules, resident requests, staff shifts, and features that hadn't even fully shipped. Managers were losing track of what needed their attention. Density had crossed the line from useful to overwhelming.

I catalogued everything the calendar showed, and everything it would need to show as upcoming features shipped. Then I redesigned it, not as a calendar, but as a prioritized daily operations view. The question it needed to answer wasn't "what is scheduled?" but "what do I need to deal with today?" We iterated through multiple versions, validated each with managers in review sessions, and landed on a solution that consolidated the platform's growing complexity without losing any information, just organized around how managers actually worked.

Parking system: user flow designed from zero
ElevateOS Web case preview6
Reputation Management
ElevateOS Web case preview7ElevateOS Web case preview8
Notifications Hub
ElevateOS Web case preview9
Integration Panel
ElevateOS Web case preview11ElevateOS Web case preview12
Transaction details
ElevateOS Web case preview13
Messaging / inbox
Outcome
Source of truth
complete connected flow maps created for the first time, adopted by engineering and product as the shared reference
Unified system
a design system built from scratch, shared across Property Hub and the Resident App.
Calendar
redesigned to handle a growing feature set while keeping clear daily operational focus, validated with managers across review sessions.

Product

Product Design · PropTech

ElevateOS: Unified Resident App

A single mobile platform where residents of multifamily communities manage their entire living experience: rent, amenities, maintenance, events, smart home, and parking. iOS & Android.

Role
Product Designer
Year
2023 - 2025
Industry
PropTech · Multifamily Residential
Deliverables
Information Architecture · Design System · Mobile UX · User Flows · Prototyping · iOS & Android
Overview

ElevateOS is a PropTech platform for multifamily residential communities across the US. The Unified Resident App is the tenant-facing product: a single mobile platform where residents manage their entire living experience: paying rent, booking amenities, submitting maintenance requests, accessing community events, controlling smart home features, and managing parking.

I joined as the sole designer in 2023, when the platform was managing around 100,000 residential units. By 2025 that number had grown to over 200,000. I was the designer supporting the entire product journey.

ElevateOS app case preview2
Home Screen
The Challenge

The app served dozens of different use cases with no coherent structure. Rent payments, amenity booking, maintenance, community events, smart home controls, parking — all present, with no clear hierarchy between them. Residents were getting lost. Features that mattered most were buried next to features that barely anyone used.

Multiple designers had worked on the product before me, each leaving fragments in different styles. There was no unified design system, no consistent navigation logic, and no shared information architecture. More critically, engineers were waiting on designs before they could build. Design had become the bottleneck slowing the entire team down.

ElevateOS app case preview1
Login
ElevateOS app case preview3ElevateOS app case preview4
Amenities browse & booking
ElevateOS app case preview9
Home Screen
My Approach
1
Design system first
Before touching a single new screen, I rebuilt the design system from scratch: a structural decision, not a visual one. A consistent component library gave engineers predictable patterns and let me design new screens significantly faster. This directly unblocked the engineering team.
2
Understand what users actually used
To tackle the IA problem I needed real data, not assumptions. We analyzed platform usage analytics to identify which sections residents used most, combined with direct feedback from property managers and feature-toggle analytics showing which features managers enabled or disabled across communities.
3
Restructure by user value
Using this data, I prioritized features by their actual value to users. High-usage, high-value features were surfaced prominently in the navigation and home screen; lower-usage features moved to secondary levels. The app was reorganized around what residents actually needed, not what the product had accumulated over time.
4
Build in configurability

The most important decision of the project: rather than one fixed feature set for all communities, I worked with the team to give property managers admin controls to toggle individual features on or off for their community.
A community without a parking facility didn't show residents a parking section. Each installation showed only what was relevant, dramatically reducing visible complexity. A systems-thinking solution: instead of simplifying by removing features, we simplified by making the platform configurable, so every community got a tailored experience.

Navigation architecture restructure: based on usage data and property manager feedback.
The Hardest Problem — Parking

The most complex challenge I tackled independently was the parking system — a feature that didn't exist in any form when the CEO first briefed me. The concept: integrate parking management directly into the resident app. Residents could pay for parking, reserve spots for guests, and invite visitors — all without calling the front office. Simple in concept, complex in execution.

There were no existing design files and no precedent in our system. I started with research — studying how parking apps, booking platforms, and venue management tools handled similar flows — then adapted those patterns to feel native to our existing ecosystem: same components, same language, same interactions residents already knew. A completely new feature that felt immediately familiar. It shipped successfully into production.

Parking system: user flow designed from zero
ElevateOS app case preview7ElevateOS app case preview8
Smart Home & Thermostat
ElevateOS app case preview12
Profile & Payment settings
ElevateOS app case preview13ElevateOS app case preview14
White-labeled app
Outcome
200,000+
managed units at the end of my tenure, up from 100,000 when I joined.
10 → 20
engineers, the team doubled, directly unblocked after the design bottleneck was resolved.
Configurable
information architecture restructured on real usage data, with per-community feature visibility.
Adopted
a design system built from scratch, used across both the Resident App and Property Hub. Designs I completed before leaving kept shipping for months after.

Contact

Available for new work · Kraków 🇵🇱

Let's work together

I'm open to product designer roles: remote or based in Kraków. If you're building something complex and want a designer who can own the full process, I'd like to hear about it.

About

Product Designer · 6+ years

Product Designer with 6+ years building and scaling digital products across PropTech, fintech, and SaaS

I design end to end: from research and information architecture through to hi-fi UI, design systems, and production builds in Webflow and Claude Code.

I work across research, flows, information architecture, wireframes, design systems, hi-fi, prototypes, and developer handoff. I spent two years proving I can carry that at ElevateOS, where I was the sole designer supporting a platform that grew from 100,000 to 200,000+ managed units.

In 2025 I founded Loonis Studio: a Webflow template business with 20+ published templates and 600+ sales in its first year. A different kind of design work that lives at its own URL.

Based in Kraków, Poland. Open to product designer roles, remote or on-site in Kraków.

Work

ElevateOS App icon
ElevateOS
Unified Resident App
ElevatedOS App icon
ElevateOS
Property Hub
HubSign icon
HubSign
eSignature Hub
FXTrading.com Web icon
FXTrading.com
Investment & Trading Platform
Loonis Studio
Webflow Templates

Expertise

Design:
User Research
User Flow
Wireframing
Hi-Fi UI
Prototyping
Design System
Interaction Design
Visual Design
UX Copywriting
Information Archetecture
AI Tools:
Claude
ChatGPT
Figma AI
Figma Make
Claude Code
Tools:
Figma
FigJam
Miro
Notion
Development:
Webflow (Client-First)
HTML/CSS
Responsive Design
CMS Architecture
No-Code Development
Production Builds
Other:
IA for AI Systems
Structured Content Design
Design Documentation

Adventures

Adventures photo1
Nighttime Pompei
Fortunately, the volcano is still asleep
Adventures photo2
Exploring new places
Discovering new cultures
Adventures photo3
A dance of art and geometry
The golden ratio weaves its magic
Adventures photo5
Two geese, one sunny day
Meet Lupa and Pupa ;)
Adventures photo6
Experiencing nature
Is that you, Loch Ness Monster?

Books

Senior Product Designer book cover
If you ask me, this is the book every designer needs in their collection. The best book for designers by a designer
Get the Book
Flowers for Algernon book cover
A story that hits you in the heart and reminds you of the importance of staying kind and human
Get the Book

Art

I am into exploring modern artists and have a little collecting of artwork created by amazing Ukrainian artist Ivanka Nechyporuk. And yes, I was not joking about geese
Black Goose
Ducks
Robert Lemay artist photo
Robert Lemay
IG
Robert Lemay painting
Manocki artist photo
Manocki
IG
Manocki painting
Karyna Movsha Photo

Karyna Movsha

Product Designer
Currently
Open to roles
Focus
Product Design
Location
from Ukraine
based in Poland
Product Designer · 6+ years

Product Designer with 6+ years building and scaling digital products across PropTech, fintech, and SaaS

Sole designer for a platform serving 200,000+ managed residential units, and founder of a profitable Webflow template business with 600+ sales in its first year. I work end to end — research and information architecture through to hi-fi UI, design systems, and production builds in Webflow and Claude Code.
Studio Work

Loonis Studio

In 2025 I founded Loonis Studio alongside my product work, a Webflow template business with 20+ published templates and 600+ sales in its first year. Systematic UI design at scale across 8 B2B verticals, shipped as production-ready products. It lives at its own URL because it tells its own story.
Visit loonis.co
Schedule a call