Why I Built Ionic Web Creator

The cornerstone article tells the story behind Ionic Web Creator as a company. This one is more personal. It is about the specific moments that made me stop building software only for other people's companies and start building one of my own.

The moment it clicked

There was a project — the details do not matter, because the shape of it is universal — where I inherited a codebase that had been shipped fast and celebrated hard. On paper it was a success. In practice, changing anything felt like defusing a bomb. There were no types worth the name, no clear boundaries, and no single place any piece of truth lived. Every fix created two new questions.

I spent weeks untangling it, and the whole time one thought kept surfacing: none of this was inevitable. Every painful part traced back to a decision made early, under pressure, with no one accountable for the long term. The software was not badly written. It was badly owned.

What I wanted to build instead

I did not want to start a company that just wrote code faster or cheaper. There are plenty of those. I wanted to build one that took ownership of the decisions — that treated architecture, data modelling, and long-term maintainability as the actual product, with the interface as the last mile rather than the whole road.

1. Own the hard decisions. Be accountable for the choices made early, because those are the ones that compound.
2. Build for the people who inherit it. The next engineer to open the codebase is the real customer of good engineering.
3. Prove it on our own products. Live with our own decisions long enough to know whether they were right.

The name, and the point

Ionic Web Creator is a builder's name on purpose. The whole company is oriented around the act of making — well-made, durable, honest software — rather than around selling the idea of it. The distinction sounds small. In practice it changes every decision, from how we scope a project to how we write this journal.

That belief is why we are building our own products in the open — Pulse, the Pulse CLI, and Business OS — and writing down what we learn as we go. If you want the philosophy in full, read What Product Engineering Means to Us.