←BaldanAll skillsLet's talk

Web, SaaS & Mobile · Tools

A tool for every layer of a product.

From the screen people touch to the server it runs on: the 17 tools I build with, the wider landscape around them, and how to choose.

My stack, layer by layer

Frontend

ReactVue

Meta-framework

Next.js

Styling & UI

Tailwind CSS

Backend

ExpressFastAPIGo

Data

PostgreSQLSQLiteFirestorePrisma

Auth & payments

AJAuth.js (NextAuth)

Mobile

React NativeExpoKotlin

Hosting & DevOps

Google Cloud RunDocker

01 · The map

52 tools, eight layers.

Every layer of a web, SaaS or mobile product and the tools people actually choose for it. The 17 marked with a dot are the ones I build with. Click any tool.

Frontend

what people see and click: components and state

Meta-framework

routing, rendering on the server, the whole app around the UI

Styling & UI

how it looks: CSS systems and ready-made components

Backend

APIs, rules and jobs that run on a server

Data

databases, caches and the code that talks to them

Auth & payments

logins, roles, subscriptions and checkout

Mobile

apps installed from the App Store and Google Play

Hosting & DevOps

where it runs, how it ships, how you know it broke

02 · Same task, different tools

One job, written in each tool.

The fastest way to feel the difference between frameworks: the same small task, side by side. The preview is what every version produces.

Counter.jsx · 10 lines

import { useState } from "react";

export default function Counter() {
  const [count, setCount] = useState(0);
  return (
    <button onClick={() => setCount(count + 1)}>
      Clicked {count} times
    </button>
  );
}

The result · The smallest interactive component: state, an event and a re-render.

Lines of code for this task

Counted from the snippets above. Fewer lines isn't automatically better: structure pays off as apps grow.

03 · Live popularity

What the JavaScript world installed last week.

Weekly downloads from the public npm registry, fetched by your browser just now. A rough signal of how much a tool is used, not of how good it is: build servers and other packages count too, and Python, PHP, Go or native tools don't appear on npm at all.

Frontend

React…
Vue…
Svelte…
Angular…
SolidJS…
htmx…

Meta-framework

Next.js…
Nuxt…
SvelteKit…
Astro…

Styling & UI

Tailwind CSS…
MUI…
Bootstrap…
Sass…

Backend

Express…
NestJS…

Data

Firestore…
Prisma…
Drizzle…

Auth & payments

AJAuth.js (NextAuth)…
Clerk…
Stripe…

Mobile

React Native…
Expo…
Ionic / Capacitor…

Source: npm registry downloads API. Bars are scaled within each group; orange marks tools I build with.

04 · Head-to-head

Pick a layer, compare up to three.

Five rule-of-thumb ratings from building with these tools, not benchmarks. The text beside the radar is where the real differences are.

Easy to startFast for usersEcosystemFlexibilityGrows with you
ReactVueSvelte

React

Components and state for building interfaces; the most used UI library.

Strong at

Huge ecosystem and hiring pool; runs on the web and, through React Native, on phones.

Watch out

Only the UI layer: routing, data and build need other tools.

For most web apps, especially when a mobile app may follow.

Vue

An approachable UI framework with templates and reactive state.

Strong at

Gentle learning curve, clear official tooling, great for dashboards and portals.

Watch out

Smaller ecosystem than React outside Asia and Europe.

For internal tools and teams that want conventions out of the box.

Svelte

A compiler that turns components into small, fast JavaScript.

Strong at

Little code, tiny bundles, very readable components.

Watch out

Fewer ready-made libraries and fewer developers to hire.

For fast, lightweight sites and interactive widgets.

05 · Stack builder

What would I pick for your project?

Choose what you're building. Each layer gets a pick and the reason for it; click an alternative to see how the choice changes.

SaaS MVP

Logins, teams, a dashboard, billing; ship in weeks, grow later.

01 · Meta-framework

Next.jsI use

because pages and API in one TypeScript codebase, server-rendered where it matters

02 · Styling & UI

shadcn/ui

because accessible dashboard components you can restyle freely

03 · Data

PostgreSQLI use

because relational data with tenants, plans and invoices fits SQL best

04 · Auth & payments

Stripe

because subscriptions, invoices and a customer portal out of the box

05 · Hosting & DevOps

Vercel

because preview links for every change and no servers to manage

★ = my first pick for this kind of project. Layers not listed don't need a separate tool here.