UI/UX Designer & MERN Stack Developer · Indore, Madhya Pradesh, India
I'm a UI/UX designer and MERN developer in Indore. Mornings are usually Figma, afternoons are React and Express, which means the handoff is a conversation I have with myself.
Selected work
Design files, shipped code, and the experiments that feed both. Hover or focus a card to see what changed.
UI/UX Design2026
End-to-end UI/UX for a platform where people find a lawyer and lawyers handle intake.
What changedTook intake from nine screens to five, and wrote the handoff doc the developers built from directly.
UI/UX Design2025
A property search and viewing concept built around what renters complained about.
What changedSix interviews with people who had recently rented in Indore; three of their complaints became the shortlist, saved-search and agent-contact flows.
UI/UX Design2025
A mobile ordering app where building a custom juice takes three taps, not a form.
What changedSplit one long customisation screen into three tap-sized choices, with constraints set so the layout holds from 320px up.
UI/UX Design2024
A clothing store interface with a checkout short enough that people finish it.
What changedCheckout went from six steps to three, and one token set held more than forty screens together.
Full Stack Development2026
Responsive React components wired to REST APIs, plus the Express routes and Mongo schemas behind them.
What changedComponents survived three rounds of API changes without a rewrite, because the data shape lives in one place instead of in every component.
Full Stack Development2025
A responsive job-search landing page built from a design concept, in semantic HTML.
What changedMobile-first from the first line — the layout holds at 375px with no override hacks, and the markup reads well enough to hand to someone else.
Full Stack Development2024
A close rebuild of the Netflix home page to get Grid and Flexbox properly into my hands.
What changedRow carousels, hero overlay and card hover states rebuilt from scratch; the gap between looks-right and measures-right is where the learning was.
Creative & Experimental2026
This site: one token set driving four visual systems, shaders included.
What changedSwitching themes re-skins the CSS tokens and the WebGL shader uniforms in the same half-second, so the 3D background never looks borrowed from another site.
Creative & Experimental2025
Short SVG and typography experiments I use to test an idea before it reaches a project.
What changedThe staggered skill reveal and the counter animations on this page both started as sketches in this folder.
9 projects shown
About
I started in design. My first job was drawing screens at Makerspace Technologies in Indore while I was finishing a UI/UX certification there, and for about a year I thought that was the whole job — hand over the file, watch what comes back.
What came back was rarely what I drew. Not because anyone was careless, but because I had not told them what happens when a list is empty, or which of my two spacings was the real one. So I started writing the boring parts down, and then I started building the screens myself.
Right now I am finishing an MCA at Devi Ahilya Vishwavidyalaya and interning on the MERN stack at NovaEdge Digital Labs, on a legal-tech platform I designed a month before I started building it. I write React components against REST APIs in the morning and open the Figma file in the afternoon to fix what I got wrong.
2021 — 2024
Devi Ahilya Vishwavidyalaya, Indore
Information technology. The years where C and C++ taught me to read an error message properly.
2023 — 2024
Makerspace Technologies, Indore
Wireframes, prototypes, and the first time someone told me my spacing was inconsistent.
May — Oct 2024
Makerspace Technologies, Indore
Six months of real screens for real deadlines. Learned what a developer does with an ambiguous file.
2024 — 2026
DAVV, School of Computer Science & IT, Indore
Studying while working. Most of what I know about databases came from needing it that week.
Jan — Mar 2025
Vyan Webs Technology, Indore
Wireframes and interactive prototypes in Figma, sitting with developers to check the build matched.
Jan — Feb 2026
NovaEdge Digital Labs, Indore
End-to-end design for a legal-tech platform, including the handoff documentation.
Feb 2026 — now
NovaEdge Digital Labs, Indore
Building the platform I designed. React and Tailwind on the front, Express and Mongoose behind it.
Skills
Labels instead of percentages. A number on a skill bar is a guess with a decimal point in it.
Where a project starts, and where I go back when the build starts fighting me.
MERN, mostly. Front-end first, but I write the routes and schemas behind my own screens.
The habits that decide whether the first two columns are worth anything on a team.
Process
The order does not change much between a design job and a build job. What changes is which artefact comes out of each step.
I start with the thing going wrong — the screen people abandon, the form nobody finishes, the page that takes four seconds. If nobody can name it, we are decorating.
Design outputA one-page note: who is stuck, where, and how we will know it stopped.
Build outputA list of the constraints — data, deadline, browsers, who maintains it after me.
I write out every screen and every decision a person makes on it, then delete the screens that only exist because the last version had them.
Design outputInformation architecture and a screen list with the decisions marked.
Build outputRoute map, and the API shape each route needs to exist.
Low fidelity, fast, reviewed at 375px before anything gets a colour. Most layout arguments end early when the thing is in a hand.
Design outputGreyscale wireframes and a clickable prototype in Figma.
Build outputA rough HTML pass to check the layout survives real text lengths.
Type scale, spacing scale, colour tokens, component states — including empty, loading and error, which is where most files go quiet.
Design outputA token set and component library the rest of the file consumes.
Build outputShared components reading the same tokens, so a change lands in one place.
Real responses, real latency, real empty states. A screen only stops being a picture once it has shown me a Mongo document it did not expect.
Design outputDesigns revised against what the API actually returns.
Build outputReact components against REST endpoints, tested in Postman first.
Spacing, grid, component behaviour and copy for every state, written down. Then I stay available for the questions, because the document never covers everything.
Design outputA handoff doc a developer can build from without messaging me.
Build outputDeployed on Vercel or Render, with the repo readable by whoever is next.
Contact
If you have a product that looks right in the deck and falls apart at 375px, that is the kind of thing I like being sent. Tell me what it does, who it is for, and what is currently annoying you about it. I read everything and reply within a day or two — and if it is not something I should take on, I will say so and point you somewhere better.