Ilya Mokhov

2023 · as a product designer

Another VPN that never launched

A subscription VPN sells one tap: press it, you are somewhere else

By the time it was ready the market was overheated with no extra chairs, so we shelved it

Two rules held it together: the app behaves like the ones already on the phone, so nothing has to be learned, and the first session ends connected, where a subscription is decided

We borrowed this animation from a site with fancy backgrounds. If the app had lived, we would have drawn ours

Finished, and never opened outside the team

Ilya Mokhov

the card promo as another card in the stack

2023 · as a product designer

Nefin is a crypto wallet that also does fiat

We grew Nefin out of a cash exchange counter in Kazakhstan. Take money, send it, bill someone: a business runs on those three

I cut the app back to those three and built it from the pieces it cannot work without. Three screens, any action two taps in. Modals, input frames and decorative icons went out

We assembled new screens out of parts that already existed, and a bank this size took far less design and code than its size suggests

Sending is where a mistake costs the most, so I took it apart and rebuilt it as one line

The amount and the address are set in type, so the screen you fill in is the one you read back. No review step

The confirmation modal, the checkbox and the screen behind them went out with it. Icons stayed where one shape means one thing

Topping up, swapping, sending, signing up: four mechanics on one frame. You meet it on the sign-up screen, before you have anything to lose

send: the amount and the address as type

the invoice created, ready to send as a link

The invoice makes this a business tool: it leaves the app as a link and opens for a client who never installed anything. Edge cases live in the same receipt: a network fee, a short payment, each a line, no separate screen

You finish what you came for and leave. Nothing here keeps you longer

Nefin has not launched yet: it is waiting on a licence. The screens are finished, and they are what this case shows

What the client sees: how much is owed, and how much has arrived

the admin cockpit: money at risk, revenue and antifraud

June 2026 · as a product designer

Bot protection for ads traffic

Agencies buy ads and bots eat the budget

Clyro catches them and collects the proof to claim the money back. In production

Live prototype

the client account: traffic, bots and protection

This product is all data: clicks, bot scores, invoices, money at risk. I built it from the smallest parts up: PRD, Claude Code, Figma as a temporary variable that came back as tokens

two tables, the same cell holding different value types

Almost everything here is a name and a value, so I made the table cell first, with 27 types.
It edits in place, no edit screens

the cell taken apart into its value types

Everything after that was the same cell in another wrapper: the sources widget, the dropdown form, the contact block.
I used it 31 times, and screen 37 needed nothing new

a block takes one to four modules of the grid

A card stacks up, a table keeps its width and scrolls. The developer who reviewed my code then built screens from the same parts: 75 commits into screens, 17 into parts

2024–2026 · as a product designer

Blask counts who is winning the market, country by country

Three designers, more than a hundred and fifty Figma files. My four big jobs are all details that repeat on every screen

blask.com

the new navigation in four states at once

I built the header and the filters with Claude and handed them over as working code

Analysts pay for comparison. The product grew by slices: All Countries, then Games and Events as tabs inside a country, then All Brands as its own section. The same brand sat in two places, and each new slice was another tab inside a tab

I put the market on top, a country or the whole world, and the categories under it: brands, games, events. Any section is two clicks now, and nothing sits deeper than three levels

A task on its way to the developers

the affiliate badge spec on its way to the developers

the old widget header against the new one

The old widget header took three rows before the chart started. The new one is one line at the same left edge: title, metrics, periods

It holds a chart, a table, a widget with no chart, and the team stopped drawing headers and started picking a state of it

the analyst drags widgets into their own layout

The analyst watching one country and the one watching five brands were getting the same page. Now they build it out of the same widgets

One payment form with seven states

The plan is a table of 126 countries against the modules, and the price adds up as you tick the cells. The checkout panel stays open, so the total moves while you tick

I built it out of parts the product already had, so the customer works with the product before paying

May 2026 · my own project

The Watcher checks what a trading channel actually did

A channel tells its readers what to buy and when. The calls that worked stay up, the ones that missed get edited, half of them are spoken in a voice note or drawn on a screenshot. Nobody checks six months of that by hand

The Watcher checks. It listens to the channel around the clock, turns every post, voice note and chart into a record of what was promised, then looks up what the price actually did

A month of a channel is just a list of calls, so the screen is a feed. One line per call: the price it started at, the price it ended at, what the market did in between. Colour only on the direction and the money

the order line taken apart into its states and controls

A review agent walks the live app and checks every new screen against this one

Not every message is a trade. Someone predicts, someone admits what they already hold, someone claims they won, someone is paid to post. Counting a prediction as a trade is how a channel's score turns flattering

Every call gets two endings: the one the trader claims, and the one you get if you cap what a losing call may take. The grey third number is that second ending, and the distance between the two is the whole product

I drew that line first and built the rest of the app out of it

Then I tested the obvious idea: repeat every call the channel makes. Over a falling month, 52 finished calls lost 4.8% each on average. But 14 of them, closed by my own cap, later reached the trader's target. The damage came from that cap, and the real difference was between channels, not between rules

The Watcher tells a pattern that works from one that only looks like it does. It finds no good trades, and I pointed it at my own work first

An idea gets replayed on old data, with the system seeing only what was known back then. Five of mine went through that, and all five came out negative