Frontend technologies
The frontend stack we actually ship.
Chosen on hiring pool, total cost and how easily you could leave — not on what we enjoy writing.
Most frontend problems aren't framework problems. They're state management, rendering strategy and performance-budget problems. These are the tools we've found hold up when an application grows past its first year.
What we use
And why we picked each one.
React
The component library the majority of the industry standardised on.
WhyDeepest hiring pool in India by a wide margin, which matters when you eventually take a project in-house.
Next.js
React framework with server rendering, routing and build tooling included.
WhyOur default for anything that needs SEO. Static and incremental rendering keep hosting costs near zero.
TypeScript
JavaScript with static types.
WhyNon-negotiable on anything above a few thousand lines. The refactoring safety pays for the setup within weeks.
Tailwind CSS
Utility-first styling with a design-token system.
WhyProduces small CSS and stops the stylesheet growing forever, which is what actually happens on long-lived projects.
Vue & Nuxt
The main React alternative, with a gentler learning curve.
WhyWe build in it when your team already knows it. Migrating a working Vue app to React is rarely worth the cost.
Astro
Content-focused framework that ships almost no JavaScript.
WhyExcellent for marketing sites and documentation where interactivity is limited and speed is the point.
Motion
Animation library for React.
WhyDeclarative, respects reduced-motion, and doesn't fight React's rendering model the way imperative libraries do.
Playwright
Browser automation for end-to-end testing.
WhyRuns the same tests across Chromium, Firefox and WebKit, which catches the Safari-only bugs that reach users.
Comparison
React vs Vue vs Angular
Including what to watch out for in each. There is no option without a downside.
| Option | Strengths | Watch out for |
|---|---|---|
| React | Largest ecosystem and hiring pool; most third-party libraries target it first. | Unopinionated — two React codebases can look nothing alike without discipline. |
| Vue | Gentler learning curve, excellent documentation, cohesive official tooling. | Smaller hiring pool in India, which matters when you scale the team. |
| Angular | Batteries included and highly opinionated, which suits large enterprise teams. | Steeper ramp-up and heavier output; overkill for most product work. |
How we choose
Four criteria, in this order.
Fit
Does it solve your actual problem, or a more interesting one?
Hiring pool
Could you hire for it in India if you took the project in-house?
Total cost
Licences, hosting and the operational time to run it — not just build cost.
Exit risk
How hard would it be to leave? We don't build things you can't walk away from.
Services
What we build with it.
- 01Website DevelopmentHand-coded sites that load fast, rank high, and convert.
- 02Web Application DevelopmentComplex, data-heavy applications that stay fast at scale.
- 03UI/UX DesignInterfaces designed around the task, not the wireframe.
- 04Mobile App DevelopmentNative and cross-platform apps shipped in 10–16 weeks.
Next.js unless you have a specific reason not to. It's React plus routing, rendering strategy and build tooling you'd otherwise assemble yourself. Plain React makes sense for an app embedded inside an existing page or a purely internal dashboard behind a login.
On anything you'll maintain for more than a few months, yes. The cost is a few days of setup and slightly slower initial writing; the return is refactoring without fear and far fewer runtime surprises.
Yes, including older stacks — jQuery, AngularJS, early React. We'll assess honestly whether incremental improvement or a rewrite is cheaper rather than defaulting to the rewrite.