I Build Apps and Fix Broken & AI‑Built Ones | TypeScript, React, Rust
If your backend is slow, broken, or was generated by AI and nobody can maintain it, I can fix it.
A Supabase backend for a desk that trades election prediction markets. Scheduled TypeScript functions snapshot Kalshi order books, find new election markets, draft candidate profiles and raise alerts; an LLM (Qwen) writes hourly race summaries for the traders and scores YouTube comments. It also has a news feed, RAG prep on pgvector and CI on every push to main.
Supabase · PostgreSQL · TypeScript · Deno · pgvector · Qwen
The panel is where orders are processed, the catalog is kept and stock is tracked. Staff have different access rights, and sign-in can be protected with two-factor authentication. Each visitor gets a private sandbox with no sign-up, kept apart by PostgreSQL row-level security.
Next.js · TypeScript · PostgreSQL · Drizzle · Docker
A storefront with collection filters, a cart and a Stripe checkout in test mode.
Next.js · TypeScript · Tailwind · Stripe
Four small fixes to the Xero pages bookkeepers use every day: an Approve button that does the action you choose, invoice printing without a PDF download, a pager at the top of long lists and sorting by description in Find and recode results. It runs in the browser and sends nothing to the developer or to third parties. Not affiliated with Xero.
TypeScript · Manifest V3 · Vitest · Playwright
A website that works on phones, tablets and desktops, loads fast and belongs to you afterward. I design the interface and code it by hand in React or Next.js. When the site needs a backend, I write that too, on Node.js or in Rust. Everything ships to your repository and your hosting, in your accounts. No builder lock-in and no monthly fee to me.
You have a design and a backend, and you need the part users actually see. I turn Figma screens into a React or Next.js front end in TypeScript, responsive from phone to desktop, and connect it to your API. Every screen has loading, empty and error states. Spacing, type scale and colors come from the Figma file.
A mobile app that shares code with your web product, or a first app to test an idea. I build it in React Native with TypeScript, so one codebase covers Android and iOS. I connect it to your backend and hand over builds ready for testing and store submission. The app is published from your developer accounts under your name, and the code stays in your repository.
A desktop application is the right answer when the work happens on the machine and not in a browser: files that never leave the office, a tool the team opens every morning, a window that keeps working when the connection drops. I build such applications in Rust, with the interface in Tauri.
A useful extension does one small job, such as saving what you are looking at or pulling numbers off a page. I build new ones in JavaScript or TypeScript on Manifest V3. I also fix existing ones broken by a Chrome update or a site redesign, or stuck on Manifest V2, which the Chrome Web Store no longer accepts. Every permission comes with a written reason, and the extension is published from your own developer account.
Something in your project broke or got slower. I reproduce the bug, find the cause and fix it. Then I write down what went wrong, what changed and how I checked it. The fix arrives as a pull request, a patch or a change on the live site, whichever suits you. I also work on projects someone else started.
Your app works when you click through it, but you are not sure it will hold up with real users and real money. In an app built with Lovable, Bolt, Cursor or v0, I find what breaks, leaks or blocks the launch, then fix it in your code without starting over. I start with what generated code usually gets wrong: database access rules, secret keys that ended up in the browser, payment webhooks and error handling.
Your app got slower one release at a time. I measure which problems actually cost your users time, then fix them. You get LCP, CLS, INP and bundle size per route, measured before and after on the same throttled connection, in one table. Work happens on a branch in your repository, commit by commit.
Your front end still runs on jQuery, old class components or an outdated Next.js setup, and every change takes longer than it should. I move it to modern React or Next.js in TypeScript one page at a time while the product keeps running: old and new code work side by side, URLs and the backend stay as they are, and each page switches over only when you decide.
New WordPress sites and WooCommerce stores, and work on the ones you already have. I build custom themes from your design or a site you like, set up WooCommerce with the checkout your customers need, and keep the admin simple enough for your team to add pages and products without calling a developer. On existing sites I fix what broke after an update, speed up slow pages and checkouts, and rebuild pages that became hard to edit.
A REST API on axum, a worker that processes files or a queue, or a service that sits between your system and someone else's API. Every service comes with tests, a README and the source in your repository.
I write the REST API your web or mobile app talks to, in TypeScript on Node.js with Express or NestJS. I also build workers for uploaded files or queued jobs and connect your app to third-party APIs. Data goes to PostgreSQL, MongoDB or Redis, and every endpoint gets input validation and tests.
If your app code alone decides who can read which rows, one missed check lets a user see someone else's data. I move the access check into PostgreSQL itself with row-level security policies and roles, then prove with tests that it holds. The same policies work in Supabase, which runs on PostgreSQL.
If your app runs on one laptop and ships by hand, I put it in Docker, add a GitHub Actions or GitLab CI pipeline that lints, tests and builds it on every push, and set up deployment from the repository to your server or platform. Keys and tokens live in your CI secrets, not in the code, and the README says how to run, release and roll back.
Rust tools for the jobs someone does by hand every week: converting or checking files, renaming and sorting in bulk, or calling an API and saving the result as CSV or JSON. A tool can run on a schedule and report what it did. It ships as one binary, with nothing to install on the machine that runs it, and stays fast on large files.
Reply the same day, Monday to Friday, 10:00–20:00 Almaty time (UTC+5).