Nikita / Product developer

Complex workflowsbecome clear products.

I design the user journey, interface, and technical foundation as one system.

A product does not start with code.

I first learn how people work today: who makes decisions, where information gets lost, and what the outcome needs to be.

01Understand the processFind the sources of errors, manual work, and decision points.
02Design the systemConnect the user journey, domain model, and responsibility boundaries.
03Build and verifyImplement states, tests, operations, and a clear path for evolution.

I design a system, not a set of screens.

I connect roles, states, and data into one continuous user journey.

Legal platform
RequestLawyerResult
Attendance system
PassVisitReport
SiteSupply
LocationProductDelivery

I build the whole product.

I connect the interface, business logic, data, and operations into one maintainable system.

Interface

Business logic

Data

Operations

I verify the path to the outcome.

I test the complete user scenario, including failure states and the next actions, not only isolated screens.

Clear journey

Predictable states

Room to evolve

Three products. One principle.

I start with the real workflow, then shape the interface and architecture around it.

Web platform / Full product flowProduction-like, not publicly deployed

Legal services platform

Clients submit a request, get matched with a lawyer, and follow the case while the team works in one system.

Problem

Documents, conversations, and deadlines were scattered across channels. The client had no complete view of the work.

Solution

One flow from request to result: matching, steps, documents, and a transparent case status.

RequestLawyerStepsResult

The product works as one system.

These two flows show the complete product rather than isolated screens, from the first visit to completed legal work.

Complete product

Built end to end

The landing page, service catalog, request flow, and client workspace form one continuous journey.

A shared visual language and product logic carry through from choosing a service to tracking an active case.

Case lifecycle

Transparent through delivery

The system connects lawyer matching, work kickoff, next steps, and order completion in one process.

Clients know what is complete and what comes next, while lawyers manage the work without fragmented spreadsheets or messages.

My work

Product flow / UX/UI / Frontend / Backend architecture

Foundation

Java / Spring Boot / PostgreSQL / Kafka / Redis / Docker

Android concept / OperationsProduct concept and system design

Gym attendance system

A mobile system replaces the paper log with one short flow for members, passes, visits, and reports.

Problem

Administrators record visits, calculate balances, and rebuild the same data for official reports by hand.

Solution

An Android workflow for a desk without a computer, plus a formal PDF report for the responsible manager.

SearchPassVisitReport

Mobile member search screen for a gym — **Find the member**Search immediately reveals active passes and the next action.

Gym pass screen with visit balance and record action — **Record a visit safely**Balance, validity, coach, and history live on one screen.

PDF attendance report generation screen — **Build the report**The administrator selects a period and previews the document content.

Gym pass operation report layout for a public institution — **Generate an auditable PDF report**Operations, reasons, and responsible people remain in one log.

Find the member
Record a visit safely
Build the report
Generate an auditable PDF report

My work

Discovery / Domain model / UX/UI / System architecture

Planned foundation

Android / Spring Boot / PostgreSQL / OpenAPI / Docker

Android / Local-firstIn active development

SiteSupply

The app tracks products by location, from a shared catalog to quantities and delivery status on site.

Problem

Procurement across locations becomes hard to control when lists and statuses have no shared product model.

Solution

A local Android app with locations, a reusable catalog, quantities, and clear movement for every item.

LocationCatalogQuantityStatus

SiteSupply locations list screen — **Choose a location**Each site keeps its own product set and update history.

Location screen with products and delivery states — **See delivery state**Filters separate unrequested, ordered, and delivered items.

Reuse the catalogA product is created once and then assigned to the locations that need it.

Catalog selection screen with product quantities — **Assign quantities**Selecting several items does not require recreating their details.

Choose a location
See delivery state
Reuse the catalog
Assign quantities

My work

Product design / Android architecture / Compose UI / Local persistence

Foundation

Kotlin / Jetpack Compose / Room / Hilt / Material 3