I built the first version of Phora alone, from scratch, with my own money. No design team, no research budget, no three months of user testing. Just an idea, a tech stack, and limited time.
Most of the decisions weren't mine. The constraints made them for me.
Tight spaces aren't obstacles — they're design tools
When everything is possible, you deliberate. You shuffle. You spend a week on a button. But when time is finite, budget is zero, and the team is just you — there's nothing to shuffle. You decide because you have to.
Phora's scene selector was supposed to be a complex editor. Prompt fields, dozens of settings, manual fine-tuning. But there wasn't time to build it. So it became a single button: the AI analyzes the product and suggests scenes. That's it. It became one of the strongest features — and it never would have existed if I'd had the time to build the original version.
Not all constraints are useful
There's a difference between strategic constraint and poor planning. If you don't test because you ran out of time — that's not a virtue, it's laziness. If you ran out of time because you committed to three unnecessary features — that's not a constraint, it's a bad decision.
Useful constraints filter out the irrelevant. They force you to choose what actually matters. Bad constraints just block you — and the difference isn't always obvious while you're in it.
Freedom is overrated
After 16 years of building, I know this: projects with unlimited budget and time almost never turned out better than those built under pressure. Usually worse — because freedom doesn't push you to decide. It pushes you to delay.
Constraints aren't the enemy of good design. Constraints are the design.
There's always a next level.
If you like what you see — whether you're building a product or a team — I'd love to hear about it.