I make confusing rules legible.

Six of them are live. None were assigned to me — the first commission is open.

01

The work

052025

DiaBuddy

Photograph a meal, get the numbers that matter to a diabetic.

  • 174commits
  • 3locales

React Native · Expo · Supabase · Gemini 3 Flash

Read how it was builtNot deployed yetwith a co-author
DiaBuddy — Photograph a meal, get the numbers that matter to a diabetic.

02

What you can commission

Price and timeline are agreed per project. I would rather quote you honestly than publish a number that means nothing until I know what you need.

  • Websites

    Next.js · Tailwind · i18n · SEO

    Landing pages and multi-page sites on Next.js. Multilingual, prerendered, fast, with the lead form wired to wherever you actually read messages.

  • Telegram mini apps

    Telegram Web Apps · React · Payments

    An application that runs inside Telegram, signs the user in through Telegram, and takes payment there.

  • Telegram bots

    Telegram Bot API · Node · Webhooks

    Scripted flows, order intake, and integration with whatever system already holds your data.

  • Mobile apps

    React Native · Expo · iOS · Android

    React Native and Expo, one codebase for iOS and Android, shipped to both stores.

03

How I work

  1. The product is the explanation, not the arithmetic.

    Anything can compute a number. The work is making someone believe it — showing which rule produced each line, when it took effect, and where it came from.

  2. Multilingual from the first commit.

    Language is not a feature added at the end. It changes routing, metadata and layout, and retrofitting it costs more than building it in.

  3. Real payments, real rules.

    Checkout that takes money, and regulations read at the source rather than remembered. Both of those are where projects usually break.

  4. When I do not know something, I ask my teacher.

    Two years in, there is plenty I have not met yet. Guessing in someone else's project is not a thing I am willing to do.

04

How this goes

  1. 01

    You send the form.

    It lands in my Telegram. I read it the same day — usually within the hour.

  2. 02

    We work out what it actually is.

    In Telegram or on a call. What must it do, who uses it, and what already exists on your side.

  3. 03

    You get a fixed price and a date.

    Both written into a contract before anything starts. Neither moves unless you change the scope.

  4. 04

    Deposit, then I build.

    You watch it run as it goes, on a live link, rather than seeing it once at the end.

05

Terms

Short, and the same for everyone.

  1. 01Work begins after a deposit that confirms the order.
  2. 02If I have not started, the deposit comes back in full.
  3. 03If I have started, 85% comes back and 15% covers the work already done.
  4. 04Scope, timeline and price are fixed in a contract before anything begins.
Full terms

06

Tools

Counted across the six products, not aspirational.

  • Next.js4
  • TypeScript3
  • Astro1
  • Bun1
  • Clerk1
  • Drizzle1
  • Elysia1
  • Expo1
  • Gemini 3 Flash1
  • Neon1
  • pdf-lib1
  • Polar1
  • PostgreSQL1
  • React Native1
  • Redis1
  • Supabase1
  • Telegram1
  • Vitest1

07

About

I am 15, born and living in Tashkent. I have been writing code for about two years — I was taught, and I still ask my teacher when something is beyond me. I work alone. Nobody has commissioned any of this: every product on this page exists because I decided it should. That part is about to change.

Uzbek · Russian · English

08

Start a project

Describe the job in two sentences. I answer in Telegram the same day.

Message me on Telegram