Atelier Monolith
A working Next.js storefront for a fictional leather brand, with search, filters, cart, gift options and one-tap WhatsApp ordering.
FRONTEND ENGINEERING
Salman Faris is a React developer in Kerala who builds dashboards and product interfaces in React and TypeScript, and search-friendly sites in Next.js. He also wrote NexGo, a Go web framework inspired by Next.js, so he understands how routing and server rendering work underneath.
For startups and teams that need a frontend built properly, or a React codebase put back in order.
React and Next.js solve different problems. React is the right base for an interface that behaves like an application, such as a dashboard behind a login. Next.js adds routing and server rendering, which matters when pages need to load fast and appear in search.
I pick based on the project, and I will tell you when neither is needed. For content-first sites, Astro often gives a faster result with far less JavaScript.
State is scattered, components repeat and small changes cause bugs elsewhere.
Client-only rendering can leave crawlers with an empty page and users with a long wait.
Spacing, keyboard access and mobile layouts drift as features pile up.
Agreed in writing before work starts.
Dashboards and product interfaces in React and TypeScript with TanStack Query and Zustand.
Server-rendered pages, routing, metadata and structured data for sites that need to rank.
Feature-Sliced Design, shared components and clear boundaries in growing codebases.
Bundle cuts, Core Web Vitals fixes, keyboard access and reduced-motion support.
Real work where it exists, and clearly labelled concepts where it does not.
A working Next.js storefront for a fictional leather brand, with search, filters, cart, gift options and one-tap WhatsApp ordering.
A Go-powered web framework inspired by Next.js: file-based routing, server-side rendering, hot reload and API routes in a single binary.
For an existing app, I read the code and measure what is slow.
Static, server or client rendering, page by page, based on what each page does.
Layouts, forms and data hooks that the features reuse.
Small releases you can test, in the order that matters most.
I work from Calicut with teams across Kerala and remote startups. Most frontend work happens through shared previews and pull requests, so location rarely matters once the brief is clear.
If the page sits behind a login, plain React is usually enough. If it must load fast and appear in search, Next.js or a static tool like Astro is the better fit. Many products use both.
Yes. I start with a short review, agree the conventions to follow and work through pull requests, so your team stays in control of the code.
NexGo brings the Next.js way of working to Go: file-based routing, server rendering and hot reload in a single binary. Building it meant learning those ideas from the inside, which helps on every Next.js project.
For small businesses, startups and teams that need custom software, not a template.
For businesses that want AI to do a specific job on their site, not AI for the sake of it.
For founders and teams who want design and development from the same person.
NEXT STEP
Share the repository or the idea, and what is getting in your way.