About

The developer behind the interfaces.

I'm Yash Patil, a frontend developer from India. I build web and mobile products that people use every day — and I stay with them past launch, because that is when the real problems show up.

Most of my work is React and Next.js on the web and Flutter on mobile. I care about the unglamorous parts: typed API contracts, states that a designer never drew (loading, empty, error, offline), and a bundle that stays small as features pile up. Good frontend is invisible — it just feels quick and never loses your input.

I work remotely with startups and product teams, usually inside their repository and their standup, so decisions get made in the open instead of in a hand-off document.

Role
Frontend developer — React, Next.js, Flutter
Based in
India · remote friendly, overlapping EU and US hours
Engagements
Freelance or contract, per milestone
Reply time
Within one working day

How I work

A short loop that keeps surprises small.

  1. Audit before code

    I read the repo, run the app, and write down what is actually broken. You get that note before I touch anything.

  2. Plan in milestones

    Small, reviewable chunks with a fixed price each. You can stop after any milestone and still have something that ships.

  3. Build in the open

    Small pull requests, real components in a preview URL, and a weekly demo. Feedback lands while it is still cheap.

  4. Ship and hand over

    Deploy, then document it: how to run, how to deploy, where the sharp edges are. No dependency on me to keep the lights on.

Toolbox

Tools I have shipped production work with.

Web frontend

  • React
  • Next.js App Router
  • TypeScript
  • Tailwind CSS
  • Vite
  • Zustand / Redux
  • React Query

Mobile

  • Flutter
  • Dart
  • Riverpod
  • Method channels
  • App Store / Play Store

Services & data

  • Node.js
  • FastAPI
  • PostgreSQL
  • REST & GraphQL
  • Auth & sessions
  • Email delivery

Quality & delivery

  • Playwright
  • Vitest / Jest
  • GitHub Actions
  • Docker
  • Lighthouse & Web Vitals
  • WCAG AA

What I care about

Four rules I don't trade away.

States, not just screens

Loading, empty, error and offline are designed before the happy path is called done.

Performance budgets

Ship the smallest page that works: fewer client components, real images, measured Core Web Vitals.

Accessible by default

Keyboard reachable, labelled controls, contrast that passes — checked, not assumed.

Code the next person can read

Boring names, small files, tests where they earn their keep.

Work with me Back to home