The Dream Steps Journal

Working notes on design, technology, and AI.

No fluff. No listicles. Writing from inside the work — for founders, product teams, and marketers who care about getting the details right. We publish what we wish someone had told us before we shipped.

From the journal

React Native vs Flutter — which one for your mobile app in 2026?

React Native and Flutter both ship serious production apps. They make different trade-offs. Five real differences, the scenarios where each wins, and the decision framework that resolves the choice.

Next.js vs React (CRA / Vite) — when do you actually need a framework?

Vanilla React (CRA, Vite) and Next.js look similar but solve different problems. Five real differences, the scenarios where each wins, and the decision framework that resolves the choice.

Native (Swift / Kotlin) vs cross-platform — when do you actually need native?

Cross-platform is the right default for most products in 2026. Three specific scenarios where native earns its 70%+ time-to-ship premium. Outside those, picking native is engineering vanity.

Laravel vs Node.js (Express / Nest) — which backend for your build?

Laravel and Node.js are both excellent choices in 2026. They optimise for different things, attract different developers, and shape different products. Five real differences and the decision framework.

Laravel + Inertia.js vs Laravel API + React — which architecture fits your team?

Two paths from Laravel to a React frontend. One keeps everything in one codebase. The other decouples for flexibility. Three scenarios for each — and the decision framework that resolves the choice.

Headless Shopify with Hydrogen — when do you actually need it?

Headless trades engineering complexity for storefront flexibility. Three scenarios where Hydrogen + Oxygen genuinely earn the complexity — and five where standard Shopify wins.

App Router vs Pages Router — when to use each (and what Server Components changed)

Two routers, two mental models, one decision. Three scenarios where App Router and Server Components earn the complexity. Three where Pages Router is still the right call.

When does your product need a design system (and when is it a waste)?

A design system is not a Figma file. Not Material. Not Tailwind. Here's the threshold for building one, the four-layer anatomy of a real system, and the minimum viable version you can ship in 7–9 weeks.

Headless WordPress vs traditional — when do you actually need each?

Headless trades engineering complexity for editorial flexibility. Three scenarios where it earns its complexity — and five where traditional wins.

Packaging design vs Amazon A+ content: what’s the actual difference?

Two visual sales tools, two completely different jobs. One earns the pickup on a shelf; the other closes the click on a listing. Treating them as the same design at different sizes is the most common mistake in product launches.