Unity WebLabs← unityweb.studio

Unity Web · Labs

Small, interactive proofs of craft.

The main site runs on Laravel. This subdomain is where we prove the React/Next.js claim — four small tools a prospect can actually click. Every demo is real code, no mock data, open source pattern.

Try the PageSpeed scanner →Back to unityweb.studio

Demos

PageSpeed scanner

Real-time Core Web Vitals check for any public URL.

Real-time Core Web Vitals check for any public URL. RSC action, streaming results, honest about what the scores mean.

  • Next.js 16
  • RSC
  • Server Actions
  • Streaming
Open demo

Case-study explorer

TanStack Query against an in-memory dataset.

TanStack Query against an in-memory dataset. Stack and year filters, optimistic updates, client-side caching.

  • TanStack Query 5
  • Client components
  • Suspense
Open demo

Component playground

shadcn-style primitives (button, input, card, tabs, dialog) built against the Unity Web design system..

shadcn-style primitives (button, input, card, tabs, dialog) built against the Unity Web design system.

  • Radix UI
  • CVA
  • Tailwind v4
Open demo

MDX micro-blog

One post on App Router patterns, demoing RSC + streaming + render-time syntax highlighting..

One post on App Router patterns, demoing RSC + streaming + render-time syntax highlighting.

  • MDX
  • RSC
  • Shiki (shared theme with main site)
Open demo

About this subdomain

Why a separate Next.js app?

The main Unity Web site is a Laravel + Filament + Blade SSR build — fast, cheap, and ideal for a brochure surface. But clients reasonably ask whether we really do React. This subdomain is the honest answer: four tools, deployed to Vercel, using the patterns we'd use on a client project.

Shared design tokens keep the two surfaces visually identical. The fonts, the warm cream background, the terracotta accent — everything you see here is driven by the same token file that drives the main site.