Building your frontend before your API is like painting a house before pouring the foundation.Building your frontend before your API is like painting a house before pouring the foundation.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Building your frontend before your API is like painting a house before pouring the foundation. 🏗️
Adopting an API-first design mentality completely changes how teams collaborate. When you establish the API contract before writing the UI, backend and frontend developers can work in parallel without blocking each other. It’s the ultimate hack for accelerating your product timeline.
After 6+ years of building websites, I’ve learned to ask one question early: “Who will update this after launch?”
The answer shapes the CMS, navigation, and handoff.
Fellow developers, what’s one question you always ask before starting a project?
The 404 was treated as a proper page rather than a fallback state.
The number is constructed as an architectural drawing. The 4 and the 0 are formed from walls at true thickness, with furniture laid out inside the resulting rooms and dimension strings running along both edges. It sits inside the same drafting system as the rest of the site rather than borrowing a display typeface.
The error message then repeats. Instead of a single dialog, identical windows cascade back across the canvas, each one carrying the same 404 notice. It reads as a system throwing an unresolved warning over and over, which is the exact behaviour Heron is built to prevent inside a model.
Error pages are never in the brief. They're a good measure of whether a team understood the product or just styled it.
Treating a 404 as an actual page instead of a dead end is such a good instinct, where did the architectural drawing idea come from, personal interest bleeding into the work?