What we build with it
Angular's opinionated structure is its point. Dependency injection, a defined module layout, a router and forms system in the box, TypeScript throughout — on a large application with several developers, having one way to do things is worth more than the flexibility of picking your own.
Our Angular work is mostly on applications that already exist: adding features, untangling state management, improving the parts that have grown slow, and building the mobile client that sits alongside the same API.
Where it fits
Enterprise-scale front ends and admin applications, where the app will outlive the team that started it and consistency is the constraint that actually binds.
When we recommend it
When it is already there, or when an organisation has standardised on it. A working Angular application is not a reason to rewrite, and modern Angular is a perfectly good place for a large front end to live.
For a new project we would reach for Vue, or Nuxt when server rendering and SEO matter — that is where our team is deepest, and you should be staffed by people working in their strongest framework. We will say that plainly rather than take work in the framework that happens to be trendier.
