I'm Hardik — a CS junior at Georgia State, building full-stack systems that turn messy real-world workflows into tools people can actually use. Most of the work sits across AI, cloud, backend, and product. I care about the unglamorous parts: API contracts, auth, deploys, and surfaces that don't make you flinch.

§   PROJECTS

Role-aware task coordination for small teams. Managers spin up a team, share a join code, and assign one-off or recurring work. Employees pick things up, update progress, and close them out. Web and mobile share the same API.

A restaurant inventory and forecasting tool. Tracks stock, surfaces pricing and ordering signals, and uses AI to help with the analysis. Built around dashboards an actual operator would open on a Tuesday.

A household app for groups that share a roof: chores, finance, contracts, and the rest of the shared-life paperwork. Comes with a proper auth boundary, RBAC, OpenAPI docs, structured logs, and tests.

An AI speaking practice app. Generates speech outlines, analyzes recorded video and supporting docs, gives feedback you can act on, and lets you rehearse with ElevenLabs voices. Google OAuth on the front.

My personal site. Built to give the rest of the work a proper front door — fast, opinionated, and a little more designed than the average portfolio.

§   WHAT I WORK WITH

a   FRONTEND

React 18 / 19   Next.js 16   TypeScript   Vite   Tailwind v4   Framer Motion   React Router   Chart.js

b   BACKEND & APIs

Node.js   Express   NestJS 10   Spring Boot 3.5   Spring WebFlux   Zod   OpenAPI / Swagger

c   MOBILE

Flutter   Dart   Dio   GoRouter   flutter_secure_storage

d   DATA, AUTH & INFRA

Supabase Postgres   Supabase Auth   Prisma 5   PostgreSQL functions   Edge Functions   jose / JWKS   Spring Security OAuth2   Pino   Docker   OCI VM   Caddy   Vercel   GitHub Actions   GHCR

e   AI

OpenAI   Gemini 2.5 Pro / 2.0 Flash   ElevenLabs

f   TESTING & DELIVERY

Jest   e2e   structured logging   GitHub Actions pipelines

§   WHAT I CARE ABOUT

i.   Backend contracts that are obvious

If someone has to read the source to figure out what an endpoint does, the contract is wrong. I lean on OpenAPI, Zod, and clear request/response shapes so the boundary is the documentation.

ii.   UIs that are usable, not just shiny

Motion is fine. Motion hiding a confusing flow is not. The surface should explain itself before anyone has to ask.

iii.   Docs and tests so projects survive a handoff

Future me counts as a different person. README, env example, structured logs, and tests at the seams — that's the minimum bar for anything I keep working on.

iv.   Things that run outside localhost

Most of what I build is deployed and reachable. I've been spending time on GSU's HPC / ARCTIC environment for heavier workloads lately — making sure the systems hold up off my laptop is part of the work.