Why Next.js is the default React framework in 2026
If you're starting a new React project in 2026, the default answer is Next.js. Indian product companies have largely moved to Next.js for new web work.
Indian companies using Next.js in production:
- Razorpay — main dashboard, marketing site
- Cred — web product
- Postman — public website and parts of the product
- Hasura — main website
- Hotstar (Disney+) — Hotstar web app
- Flipkart — selected new features
- Zomato, Swiggy — marketing and selected app sections
- Most YC-backed Indian startups in 2024-2026
- D2C brands (Mamaearth, Boat, Lenskart) — many on Next.js for SEO
Why Next.js won over Create React App:
- Server-side rendering for SEO (essential for ecommerce, blogs, jobs portals)
- App Router with React Server Components
- Built-in image optimization (next/image)
- File-based routing (no manual route configuration)
- API routes (built-in backend for simple endpoints)
- Excellent Vercel deployment integration
- Strong TypeScript support out of the box
What Next.js doesn't do:
- It's not a backend framework — for complex APIs, use a dedicated backend
- It's not great for purely client-side dashboards (Vite + React is lighter)
- It's not for mobile apps (use Expo/React Native)
Indian Next.js job market in 2026:
- ~40% of React job postings now explicitly mention Next.js
- Fresher Next.js roles: ₹4-10 LPA
- Mid-level: ₹12-25 LPA
- Senior: ₹30-60 LPA
- Next.js is a separate skill listed on resumes — knowing it commands a premium
App Router vs Pages Router — what to learn in 2026
Next.js has two routers:
App Router (Next.js 13+, default since 13.4):
- File-based routing in /app folder
- React Server Components by default
- Streaming, Suspense for data
- Server Actions for mutations
- Layouts that nest cleanly
- New convention: page.tsx, layout.tsx, loading.tsx, error.tsx
Pages Router (legacy, still supported):
- File-based routing in /pages folder
- All components are Client Components
- getServerSideProps, getStaticProps for data fetching
- _app.tsx, _document.tsx for global wrappers
What Indian companies use in 2026:
- New projects: ~80% App Router, 20% Pages Router
- Existing projects: hybrid (Pages Router for old routes, App Router for new ones)
- Some teams stick with Pages Router because their stack is mature and they don't want migration risk
What you should learn:
- App Router first — it's the future and what new jobs use
- Basic Pages Router — you'll need to read existing code in mid-senior interviews
- Don't try to learn both simultaneously — pick App Router for depth, learn Pages Router for survey-level knowledge
The interview signal: If a candidate confidently explains the difference between Server and Client Components, when to use each, and how Server Actions work — that's senior-level Next.js knowledge. Most fresher candidates can't articulate this.
10-week Next.js learning roadmap (free)
Prerequisites: solid React (use our React Deep Guide for context) + TypeScript basics + at least 1 deployed React app.
Weeks 1-2 — Next.js fundamentals
- Install Next.js with TypeScript and Tailwind:
npx create-next-app@latest(use App Router) - File-based routing: page.tsx, layout.tsx, dynamic routes [slug], catch-all [...slug]
- Navigation: <Link> component, useRouter, redirect()
- Metadata API for SEO: title, description, OpenGraph
- next/image for image optimization
- next/font for font optimization
Free resources:
- Next.js official tutorial — best free Next.js course
- Next.js documentation — exceptional quality
- JavaScript Mastery Next.js projects
- Code with Antonio Next.js series
Weeks 3-4 — Server Components and data fetching
- Server Components vs Client Components mental model
- "use client" directive — when and where
- Async Server Components for data fetching
- fetch() with caching options (no-store, revalidate, force-cache)
- Generate static, dynamic, and ISR routes
- generateStaticParams for SSG
- Build a blog site with markdown posts loaded server-side
Weeks 5-6 — Server Actions and forms
- "use server" directive — running server code from client
- Form handling without API routes
- useFormState, useFormStatus, useTransition for form UX
- Optimistic updates
- Server-side form validation with zod
- Build a CRUD app with full Server Actions (no separate API endpoints)
Weeks 7-8 — Database, auth, and full-stack
- Database integration: Prisma or Drizzle ORM
- Database choice: PostgreSQL on Neon (free tier), Supabase, or Railway
- Authentication: NextAuth.js (now Auth.js) or Clerk (paid but easy)
- Session handling, protected routes
- Role-based access control
- Build a complete app: user registration, login, dashboard with personal data, edit profile
Week 9 — Advanced patterns
- Middleware for auth checks, redirects, A/B testing
- Route Handlers (API routes in App Router style)
- Parallel routes and intercepted routes
- Streaming with Suspense
- Internationalization (i18n)
- Image optimization deep-dive
- ISR (Incremental Static Regeneration) for dynamic-yet-cacheable pages
Week 10 — Deployment and production
- Deploy to Vercel (free tier — easiest)
- Deploy to Cloudflare Pages (alternative — also free)
- Environment variables, secrets management
- Analytics with Vercel Analytics or PostHog (free tier)
- Performance monitoring with Sentry (free tier)
- Lighthouse score optimization
By end of 10 weeks you'll have 2-3 deployed full-stack Next.js apps and be ready for Indian fresher-to-mid Next.js interview rounds.
Deploying Next.js apps — Indian developer's free hosting options
Vercel (recommended for beginners):
- Free tier: unlimited static sites, 100GB bandwidth/month
- Created by the Next.js team — best integration
- Zero-config deployment from GitHub
- Automatic preview deployments on every PR
- Limitations of free tier: limited serverless function execution time, can't use commercially
- Pricing for paid tier: starts $20/user/month (steep for Indian solo devs)
Cloudflare Pages:
- Truly free with no commercial restriction
- Unlimited bandwidth (huge for Indian audience apps)
- Slightly less seamless Next.js support (needs adapter)
- Better choice if your app might have heavy traffic and you want to stay free
- Edge functions for SSR (Cloudflare Workers)
Netlify:
- Free tier similar to Vercel
- Good Next.js support
- Less popular for Next.js but works well
Self-hosted on VPS:
- DigitalOcean, Hetzner, Hostinger VPS: ₹400-800/month
- Use docker + nginx
- More control, more responsibility
- Better economics if you have multiple apps
- Indian developers often choose this for client work
Cost comparison for Indian developers:
- Hobby project: Vercel free
- Side project that might monetize: Cloudflare Pages free
- Commercial product: VPS (₹500-2000/month) or Vercel Pro ($20+/month)
- Mass-market app: Cloudflare Pages (no bandwidth limits)
Database hosting (free tiers):
- Neon (PostgreSQL) — best Postgres free tier
- Supabase — Postgres + auth + storage, generous free tier
- PlanetScale (MySQL) — free tier with branching
- Turso (SQLite at edge) — interesting for low-latency
Authentication services (free tiers):
- Auth.js (NextAuth) — fully free, self-hosted
- Clerk — free up to 10k monthly active users
- Supabase Auth — free with Supabase project
Common Next.js mistakes Indian developers make
Mistake 1 — "use client" everywhere: The biggest App Router mistake. You add "use client" to one component, then accidentally add it to everything because of import chains. Result: zero benefit from RSC, larger bundle, slower app.
Fix: keep "use client" boundaries tight. Server Components should be the default; only add "use client" when you need useState, useEffect, or browser APIs.
Mistake 2 — Fetching data from a Client Component when you could fetch on the server: Client Component → useEffect → fetch is the old React way. In Next.js App Router, fetch in the Server Component and pass data as props. Much faster and SEO-friendly.
Mistake 3 — Not understanding caching: Next.js 13+ caches aggressively by default. Your fetch calls are cached, your pages are cached. New devs are confused when data doesn't update. Learn cache(), revalidatePath, revalidateTag, and dynamic = "force-dynamic".
Mistake 4 — Using API routes when Server Actions would be better: For form submissions and simple mutations, Server Actions are cleaner and don't require a separate API endpoint. Use API routes when you need: external HTTP clients calling your API, webhooks, or third-party integrations.
Mistake 5 — Mixing Pages Router and App Router incorrectly: You can have both in the same app, but be deliberate. Don't put a /products/ route in both /pages and /app — App Router takes precedence and Pages Router routes silently get ignored.
Mistake 6 — Forgetting next/image limitations: next/image requires either width/height OR fill. Images from external domains need configuration in next.config.js. Many Indian devs spend hours debugging this.
Mistake 7 — Not optimizing for Indian network conditions: Indian users often have slow 3G or 4G. Test your app at 3G throttling in Chrome DevTools. If first paint takes >3 seconds, redesign with more SSG / less client JavaScript.
Mistake 8 — Deploying with default tsconfig: Default Next.js TypeScript config is lenient. Enable strict: true and noUncheckedIndexedAccess immediately. Production-grade Indian companies have strict configs.
Mistake 9 — Not using TypeScript: In 2026, every serious Next.js codebase is TypeScript. Don't use plain JavaScript with Next.js — you'll struggle to apply to mid-senior roles.
Mistake 10 — Skipping testing: Most Next.js tutorials skip testing. Indian product companies expect: Playwright or Cypress for E2E, Vitest + Testing Library for unit. Learn at least one of each.
Frequently asked questions
Should I learn React first or jump to Next.js?▾
React first. Next.js is React + a framework around it. Without solid React fundamentals (hooks, state, rendering), Next.js feels like magic. Spend 3-4 months on React, build 2 React projects, then add Next.js. Total ~5-6 months to Next.js job-ready.
Is Next.js overkill for small projects?▾
For pure client-side dashboards or internal admin tools — yes, Vite + React is lighter. For anything with public pages needing SEO, ecommerce, blogs, or marketing sites — Next.js is the right default. Most Indian projects benefit from Next.js because mobile-first Indian users need fast first paint.
Vercel vs self-hosting for Indian developers?▾
Vercel free tier for learning and hobby projects. Self-host on a VPS (Hostinger, DigitalOcean) for commercial / client work where you control costs. Vercel paid plans are expensive in INR terms — most Indian solo developers and small agencies self-host once they grow beyond hobby scale.
App Router vs Pages Router for new projects in 2026?▾
App Router for any new project. Pages Router is legacy — still supported but no new features are added. Every modern Next.js course in 2026 teaches App Router. If you join a company using Pages Router, you'll learn it on the job in 2-3 days.
How is Next.js different from Remix or Astro?▾
Next.js: most popular, best ecosystem, default at Indian companies. Remix: similar philosophy, less mature in India. Astro: best for content-heavy sites with minimal interactivity (blogs, marketing). For job market in India, Next.js wins by huge margin — learn it first.
Can I get a Next.js fresher job in India?▾
Yes. Many Indian product startups now post 'React/Next.js Developer' roles. Salary range: ₹4-12 LPA at startups, ₹6-15 LPA at funded companies. Need: 2-3 deployed Next.js projects on GitHub + solid React fundamentals + basic TypeScript.
Is Next.js dying because of new frameworks like Qwik or Solid?▾
No. Qwik, Solid, Astro are interesting but have ~1% of Next.js market share. Indian product companies overwhelmingly use Next.js. New frameworks will mature over years, but Next.js is the safe career bet for the next 3-5 years.