React & Next.js Developer
I build with React and Next.js. Dashboards, e-commerce, data-heavy apps. The complicated stuff.
What I build
React's component model works well for complex applications. Next.js handles the server-side bits. Together, they're a solid choice when the requirements get demanding.
Dashboards and admin panels
Data-heavy interfaces. Complex state, real-time updates, high-performance data tables (50k+ rows), charts. Apps that stay fast even with a lot going on.
E-commerce
Next.js storefronts with Shopify, Stripe, or custom backends. Server Components help with page speed and SEO.
Full-stack apps
API routes, database connections, auth. Everything in one codebase.
Component libraries
Reusable components with consistent patterns. Storybook docs, proper tests.
Tech I use
Why Next.js
Next.js is the default React framework now, for decent reasons. Server Components mean less JavaScript in the browser. Pages load faster. Data fetching gets simpler.
I've been using Next.js since before any of that existed, so I know the old way and the new way. Useful if you're migrating something or working with a mixed-experience team.
Project experience
Career storytelling platform
Next.js with AI voice narration (ElevenLabs) over generated image backgrounds. Framer Motion animations, Storybook component library.
Automotive microservices
React/Next.js frontend, AWS microservices redesign. Event-driven architecture with SQS, Lambda, DynamoDB.
E-commerce fashion
Vue/Shopify storefront with A/B testing. Figma to production, GraphQL integration.