Skip to content

Laravel development

Laravel with Inertia, Vue and Nuxt: the right front end for the job

Laravel is the engine, but the front end is what your users see, and there’s more than one good way to build it. I’ll help you choose between Inertia and a separate Nuxt front end based on what you’re building, not what’s fashionable.

What I build on the front end

01

Inertia apps with Vue

Modern, snappy interfaces driven by Laravel with no separate API to maintain. My go-to for dashboards, portals and prototypes.

02

Laravel APIs for Nuxt and mobile

A clean, documented API that powers a Nuxt front end today and a mobile app tomorrow, with sensible authentication.

03

Server-side rendering for SEO

Public pages that load fast and are fully readable by search engines and AI crawlers, using Nuxt’s rendering.

04

Real-time features

Live updates, notifications and chat using WebSockets, so the interface reacts as things happen.

05

Reusable UI, not one-off pages

A consistent component library with Tailwind CSS, so new screens are quick to build and look like they belong together.

06

Secure by default

Authentication, authorisation and validation handled carefully on the server, whichever front end you choose.

Worth knowing

How I choose between Inertia and Nuxt

Inertia when you want speed and one codebase, usually for logged-in apps. A Laravel API with Nuxt when public pages, SEO, or a future mobile app matter. Often the answer is both: Nuxt for the public site, Inertia or Nuxt for the app.

How we’d decide and build

  1. Map the experience

    Who uses it, from where, and which pages need to be found in search? That shapes the architecture more than anything.

  2. Choose the architecture

    I recommend one approach, explain the trade-offs in plain English and note what would change my mind.

  3. Build in thin slices

    One real feature end to end first, so we prove the approach before building the rest.

  4. Polish and launch

    Performance, accessibility and SEO checks before go-live, plus monitoring afterwards.

Ways to work together

Every business is different, so I keep this flexible. I’ll recommend the simplest option that gets you what you need.

Option 01

Architecture advice

A short engagement to choose the right stack and plan the build, before you commit to a team.

Best when: You’re at the start and want to avoid a costly wrong turn.

Option 02

Build the product

End-to-end Laravel and front-end development to an agreed scope.

Best when: You want it built and handed over cleanly.

Option 03

Join your team

I join your existing developers for a period to ship features and raise the standard.

Best when: You have a team and need senior capacity.

FAQ

Laravel, Inertia & Nuxt: your questions answered.

What is Inertia?

Inertia lets you build a Vue (or React) interface on top of Laravel without writing a separate API. Laravel handles routes and data; Vue renders the pages. You get a modern, fast-feeling app from a single codebase.

When should I use Nuxt instead?

When you want public pages that rank in search and load fast, or a separate front end that other apps (like a mobile app) can share an API with. Nuxt renders pages on the server, which is excellent for SEO.

Can I use both?

Yes, and it’s common: a Nuxt marketing or content site for search, plus an Inertia or Nuxt application behind the login. The two share the same Laravel back end.

Is a Laravel API good enough for a mobile app?

Yes. A well-designed Laravel API can serve web and mobile clients. We’d plan authentication and versioning carefully so the API can evolve without breaking older app versions.

Do you use React?

My main front-end tools are Vue, Nuxt and Inertia. I have worked with React and Next.js too, but I’ll usually recommend the Vue ecosystem for Laravel projects because the pairing is mature and productive.

Will my site be SEO-friendly?

If it needs to be, yes. I’d use server-side rendering with Nuxt or well-structured Blade pages for anything public, with proper metadata, structured data, sitemaps and fast loading.

Get in touch

Tell me about your project.

No sales script and no pressure. Share a few details and I’ll reply personally, tell you honestly whether I can help and, if I can’t, point you to someone who can.

I’ll only use your details to reply. See the privacy policy.