What we build with it
Every piece of web work we do is TypeScript, not JavaScript. Admin panels, merchant dashboards, marketing sites, and the Node services that sit alongside them.
The value is not the type annotations themselves — it is that the contract between the front end and the API becomes checkable. When a backend field changes shape, the build fails in the places that consume it, instead of a customer finding it. On projects with several front ends against one API, that difference compounds quickly.
Where we have shipped it
The web side of our white-label cashback platform — a merchant app for configuring cashback rules and an admin UI that launches new branded apps — is TypeScript, as is the Formtastic web application. This site is TypeScript too.
When we recommend it
Always, for anything that will be maintained past its first release. The setup cost is a day; the alternative is discovering type mismatches in production for the lifetime of the project.
The one case where plain JavaScript is defensible is a genuinely throwaway prototype that nobody will extend. In our experience prototypes rarely stay throwaway — see taking an AI prototype to production — so we start typed.
TypeScript work generally falls under web development.
