Carlos Anaya Ruiz
ES

service · web development

Web Development with Next.js and Firebase

Apps that render on the server, load fast on 4G, and can be crawled without running a line of JavaScript.

Get a project quote →All services →

From Mexico City, for teams in any time zone. Spanish or English.

context

Why this matters

Every web project I build starts with the same question: what does Google need to see, and what does the user need to do? The answer shapes everything — rendering strategy, data fetching, URL structure, component architecture.

I use Next.js because it lets me choose SSR, SSG or ISR per page — the right rendering strategy for each kind of content. Combined with Firebase for the database, authentication and serverless functions, it is the stack that gives the most value per engineering hour instead of the most lines of code.

The part almost nobody quotes for is the migration: mapping the old URLs, deciding what earns a 301 and what is allowed to die, and revalidating structured data once the new site is live. If your site already has traffic, that work is the difference between a launch and a drop in positions that takes months to recover.

Key benefits

What I build

Fast, indexable, modern web application development

pendiente · imagen 1600×900public/media/servicios/desarrollo-web.png

  • Lighthouse 90+ scores in performance, SEO, and accessibility
  • SSR/ISR: content ships in the served HTML and revalidates without a redeploy
  • Serverless backend with Firebase: Firestore, Auth, Functions & Hosting

afterwards

What is different afterwards

  • The content is in the HTML of the first response: Googlebot does not need a second pass to render JavaScript and see it.
  • Content updates without waiting for a full site deployment.
  • Predictable infrastructure cost: serverless that scales to zero when nobody is using it.
  • A repository with strict TypeScript and CI that another developer can pick up without archaeology.

How I work

How a build runs, phase by phase

  1. 01 / 05

    Scope and architecture

    We define which pages exist, what renders on the server, what is cached, and what needs live data. The URL map is decided here, before any code, because changing it later costs rankings.

  2. 02 / 05

    Design system and base implementation

    Tokens, components, and layout with Next.js App Router and strict TypeScript. Accessibility and loading states from the first component, not as a final patch.

  3. 03 / 05

    Data and integrations

    Firestore, authentication, Cloud Functions, and whichever third-party APIs the product needs, with security rules written and tested before any data is exposed.

  4. 04 / 05

    Technical SEO and performance

    Per-route metadata, sitemap, robots, hreflang, JSON-LD, and Core Web Vitals work before launch — not as a later rescue phase.

  5. 05 / 05

    Launch and handover

    Vercel deployment with CI/CD, 301 redirects if it is a migration, and documentation so your team can carry on without depending on me.

fit

Who this is for, and who it is not

The second list is the useful one. If you recognise yourself there, I will say so on the first call instead of writing you a proposal.

good fit

Who this is for

  • Businesses that depend on organic search and need the site fast and indexable from day one.
  • Founders who need to move from an already-validated idea to a product in production.
  • Teams stuck with a slow WordPress or a SPA that will not index, who want to migrate without losing positions.

not a fit

Who this is not for

  • Not for projects that need a CMS with dozens of editors and complex approval workflows: a dedicated platform will serve you better than custom code there.
  • I do not take projects without one person on the client side who can decide and review. Without that contact, scope drifts and the result suffers.

What's included

What you get

Every engagement ships all of it. Anything outside the list is quoted before it gets built.

  • Information architecture and wireframes
  • Frontend development with Next.js App Router + TypeScript
  • Firebase integration (Firestore, Auth, Cloud Functions)
  • Technical SEO: sitemap, robots, hreflang, Schema JSON-LD
  • Core Web Vitals and performance optimization
  • Vercel deployment with CI/CD configured

Stack

The stack this runs on

  • Next.js 16 (App Router)
  • React 19
  • TypeScript
  • Tailwind CSS
  • Firebase
  • Firestore
  • Firebase Auth
  • Cloud Functions
  • Node.js
  • PostgreSQL
  • Vercel
  • CI/CD
  • Git
  • Lighthouse
  • Schema.org / JSON-LD
  • Next.js 16 (App Router)
  • React 19
  • TypeScript
  • Tailwind CSS
  • Firebase
  • Firestore
  • Firebase Auth
  • Cloud Functions
  • Node.js
  • PostgreSQL
  • Vercel
  • CI/CD
  • Git
  • Lighthouse
  • Schema.org / JSON-LD
  • Next.js 16 (App Router)
  • React 19
  • TypeScript
  • Tailwind CSS
  • Firebase
  • Firestore
  • Firebase Auth
  • Cloud Functions
  • Node.js
  • PostgreSQL
  • Vercel
  • CI/CD
  • Git
  • Lighthouse
  • Schema.org / JSON-LD
  • Next.js 16 (App Router)
  • React 19
  • TypeScript
  • Tailwind CSS
  • Firebase
  • Firestore
  • Firebase Auth
  • Cloud Functions
  • Node.js
  • PostgreSQL
  • Vercel
  • CI/CD
  • Git
  • Lighthouse
  • Schema.org / JSON-LD

in order · Frontend · Data & backend · Infrastructure & quality

FAQ

Frequently asked questions

What people ask before starting a build.

How long does it take to build a web app with Next.js?

It depends on scope, and scope is closed in the first step: what pages exist, what renders on the server, and what needs live data. Before that is in writing, any number of weeks I give you is a guess. With scope closed I give you dates per deliverable. Those dates assume someone on your side who can decide and review; without that contact the calendar stretches, and that is not mine to control.

Why Next.js and not another framework?

Because of hybrid rendering: each route is served the way it should be — server, static, or revalidated — without maintaining two stacks. And it ships with what other frameworks leave to hand: per-route metadata, sitemap, hreflang, optimized images. On Vercel a deploy is a push and a rollback is a click. Uptime is the provider to control, not me.

What do I keep when the project ends?

The repository with strict TypeScript and CI, the Vercel deployment with its CI/CD, and documentation of how it is built, so another developer can pick it up. If you want me to keep working on it afterwards, that is a monthly retainer with agreed hours.

Services

Related services

A build almost always travels with one of these two.

Or review all four services and how they combine before deciding.

the proof · file pending

pendiente · imagen 1400×900public/media/servicios/desarrollo-web-lighthouse.png

pendiente · imagen 1600×1000public/media/servicios/desarrollo-web-pr.png

three channels · parallel

How you reach me

or write to carlos@carlosanayaweb.com · +52 55 4416 7974

Tell me what you need to build.

Send the URL, the stack you are on today, and what has to be live by when. I reply in under 24 hours.

Get a project quote →See how I work →

You get scope, timeline, and price in writing before I write a line of code. carlos@carlosanayaweb.com