Something's shifted in how I build web apps at the agency and I don't think I'm going back.
For years the process was linear and it always started the same way. User research, flows, UI/UX, graphic design, then hand it to dev. Design was the anchor. Everything orbited around it. You didn't write a line of code until the designs were signed off.
That's flipping.
I've been running on GPT 5.4 through Codex and it's remarkably good at database design. Not just fast — it thinks structurally about relationships in a way that used to take a senior dev and a whiteboard a full afternoon. For app projects I'm now starting there. Schema first, core logic second, design plugged in afterwards. A process that used to take months now compresses into weeks.
Here's the thing people get wrong about this: it's not skipping design. Schema design is design. Every table, every relationship, every field is a decision about what the product can and can't do. The entry point for design thinking just shifted from mockups to data relationships. If anything, that's a more substantive place to start.
But the real unlock is what happens next. When the skeleton goes up in hours instead of weeks, designers aren't working against static mockups anymore. They're working against a real thing with real data flowing through it. Design decisions made against a working prototype are better than decisions made against a Figma file. Every time.
The creative work doesn't disappear. It just stops being the first bottleneck.
I think this is where web app development is heading. Not for everything — if the interaction itself is the product, you probably still need to design your way to it. But for the vast majority of app work? The stuff agencies and product teams actually build day to day? Start from the data, work backwards. The design will be better for it.
I'm fully prepared to look back on this and cringe. But right now, it feels like the more honest way to build — and a faster one.