Skip to content
Write to me

Open to a conversation · Moscow

Danil Zablotsky

Design engineer · product design and frontend

I design interfaces and build them into working products on iOS, Android and the web myself.

Layer of the first screen

Language

Colour theme

How I got here

From a menu for a game to a product of my own: nine chapters on how I became a design engineer.

Keep scrolling

Two children by a radiator, a cat beside them
A curly-haired young man in profile among birches
Two young men in suits taking a mirror photo
A selfie with an open student record book
A view from a window of mountains and snowy roofs
A desk with a large monitor and a keyboard
A cat in a Santa hat
A street in central Moscow, a building with a globe on its front
A laptop with Figma open in an airport lounge
  1. It started with a menu for a game

    A maths and physics class. We wrote websites in Notepad, in plain HTML, CSS and JS: they taught us the hard way. From the seventh grade I lived in Photoshop, then found Illustrator, and in the eleventh, Figma.

    In it I built a menu for a game I played all the time and posted it in the game's groups. People asked how to install it. It reached the developers: they offered me work, then opened my file and stopped answering.

    Over a hundred frames. Not one component.

    I was furious at the time. Now I understand them.

    The menu's video on YouTube and three comments under it, in Russian: “If they really made one like this, it'd be a great update”, “Damn, cool”, and a question about where it's from and what the chances are it will happen
    The menu's video on YouTube, with the comments under it
  2. Maths first

    I wanted to study product design, but a teacher talked me out of it: get your maths up first. So I ended up at Omsk State University, in applied mathematics and computer science.

    I always had top marks in programming, and in group projects I always ended up as the designer.

    At night: a textbook on the monitor, below it a laptop with notes in LaTeX
    Lecture notes in LaTeX, autumn 2024
    A laptop with topology notes in a lecture, a cap beside it on the desk

    It's a pain to check my own class schedule.

    Some universities had apps for that. From 2023 Maxim, a classmate of mine, and I kept talking about building one for ours, and kept putting it off: the idea felt too big.

  3. VCourse

    In our third year we were given a semester to build a product of our own, and neural networks had just grown up enough. We went for it. I took product design and the front end, Maxim the back end and DevOps.

    I had no experience in mobile development at all. The first semester went on Swift, SwiftUI, Xcode and Apple's guidelines.

    The VCourse profile screen in Xcode's view debugger, pulled apart into layers
    The profile screen in Xcode's view debugger
    A lock screen notification: VCourse updated to version 0.1.0

    By the end of the semester my own app was on my phone.

    Icon Composer with an icon of two circles on blue
    The icon in Icon Composer

    The next semester and the summer went on polish. The app was rewritten from scratch several times: I wanted it perfect.

  4. Launch

    We agreed with the university on a post in its Telegram channel. The post went out, and we sat refreshing the pages, watching the numbers.

    I had never felt anything that good.

    A presentation of VCourse on a big screen in front of a hall

    The launch in numbersSeptember 2025

    57rank among education apps on the Russian App Store at launch

    The first three days, 1–3 September

    App Store impressions
    2,800
    page views
    1,287
    downloads
    632
    Downloads per day, 1–14 September 2025 632 downloads in the first three days, 411 of them on 2 September.
    downloads in two weeks
    823
    downloads by 4 October 2026
    3,428

    Source: App Store Connect

  5. The fork

    In the semester after the launch came Android and the website, and five more colleges and universities joined. It all worked, and the question came up: what next? We couldn't keep growing it seriously and earn nothing from it.

    Ads in the app, or a service for universities.

    We really didn't want ads. We took the second road: our own service for building timetables, with the apps as a pleasant extra for students and teachers. We started talking to the people who make the timetables and took apart how it's really done.

  6. One night

    My bachelor's was ending and I was looking at master's programmes in Omsk. One night a newsletter from Central University arrived: a programme in Human Experience Design. Literally what I had wanted to study from the start.

    They asked for a portfolio. I didn't have one.

    I decided not to sleep until I had built something worth sending.

    git log, 23 June 2026, Omsk time
    1. 06:56 66f50fd Портфолио: первичная сборка на Next.js
    2. 09:34 3b88940 assets: add portrait and product screenshots
    3. 09:34 fb0936a feat: build out the portfolio

    The site went up on Vercel and the application went out. Then a call, and several weeks of silence.

    And then a letter: the largest grant they give.

    One letter changed the plan: I was moving to Moscow.

  7. …and now I had to pay for a flat somehow

    A plane's cabin: seat backs and the aisle
    A bright empty room with a desk by the window
    The main building of Moscow State University under a cloudy sky
  8. Ten prompts

    I moved at the end of the summer and started work: several iOS app designs a week, plus their ASO. Doing that by hand would have driven me mad.

    I tried agents in Figma. That took a whole pipeline, and it worked.

    A cat on a beanbag beside shelves and boxes
    A selfie in a mirror
    A red sunset over a street
    A laptop in a large lecture hall

    I got a personal designer, and I became the boss.

    I won't claim a complete app, with icons and an App Store page, comes out of one prompt. I will claim it comes out of ten thoughtful, consecutive ones.

  9. Still going

    I have plenty of components now.

    • vcourse

      VCourse

      Running: 1,049 people a day on average, September 2026

    • masters

      Master's

      Central University, since 2026

    • pora-na-paru

      Pora na paru

      The web client and the timetabling service. 2,642 commits across three clients, 2 June to 31 October 2026

Work

  1. My own product · since 2024

    Pora na paru

    New version in development

    A timetable for universities. I began with VCourse, tested the idea on real users and am building the product again from scratch.

    Design, iOS, Android and web: me. Backend: my co-founder.

    Mockup: website
    Mockup: iPhone
  2. One service for a whole university

    A university keeps its timetable in one place, and students and teachers see changes in every app at once.

    Mockup: service
  3. Native on iOS and on Android

    Not one layout for two platforms: each has its own gestures, widgets and system features.

    Mockup: iPhone
    Mockup: Android
  4. Publishing without conflicts

    The editor catches clashes before anything is published. Move a lesson yourself: the rule is real, the data is made up.

    MonTueWedThuFri

    No conflicts, ready to publish

  5. It began with VCourse

    The first version shipped on iOS, Android and the web and was tested by real users.

    The exact number of users, dated, goes here

    VCourse:App StoreGoogle PlayRuStore

    Screen recording: VCourse

Pora na paru

To Flow ↓Open the page →

  1. iOS app design · since 2026

    Flow

    A system of my own: agents, a terminal and a Markdown knowledge base carry a task from the brief to finished screens.

    The tasks in the demo are made up.

  2. 01

    Brief

    A task becomes a short brief and a list of questions.

    > /new-task demo-app

    Screenshot: brief
  3. 02

    Research

    References from real apps, a breakdown of patterns and a map of screens.

    > /research

    Screenshot: screen map
  4. 03

    Screens

    An agent assembles screens from base tokens and components, and I make the decisions.

    > /screens

    Screenshot: screens in Figma
  5. 04

    Handoff

    The finished file goes to development.

    > /handoff

    Screenshot: handoff
  6. 05

    Back to the base

    Review notes become rules in the knowledge base, and the next task starts from them.

    > git commit rules.md

Flow

To Projects ↓Open the page →

  1. Everything else

    Projects

    What I make beside the product and the job: one screen for each project.

  2. In progress

    This site

    A portfolio built like a product: Next.js, GSAP, a theme system of its own, strict checks before every commit.

    Code on GitHub
    portfolio/
    Screen recording: site
  3. Defended, 2026

    A thesis in LaTeX

    A bachelor's thesis as a code project: LuaLaTeX, GOST formatting, PDF builds and releases through GitHub Actions.

    Sources on GitHub
    bachelor-thesis/
    Pages of the thesis

Projects

To experience ↓Open the page →

Experience

  • since 2026Pora na paruCo-founder and CEO: design, iOS, Android, web
  • since 2024VCourseCreator: design and client development
  • since 2026iOS apps teamDesigner
  • 2025FreelanceWeb designer, under contract

Education

  • Central University, master's in Human Experience Design, since 2026
  • Omsk State University, applied mathematics and computer science, 2022–2026

Also

  • Student Startup grant, second stage participant, 2026
  • Pitch to investors, Tramplin tech park, April 2026
  • English B2
Portrait of Danil Zablotsky

About me

I live in Moscow. I care about where design meets code: one person holding both the decision and how it works.

Let's talk

Telegram is the fastest way to reach me.

Write to me