Angular
Angular development for large, form-heavy applications
Angular is a strong fit for large internal and customer applications with many forms, roles, and a team that benefits from a single way of structuring a feature. We use current Angular for new work and we are explicit when an older AngularJS or early Angular app needs a planned move.
- Workflow applications
- Design consistency
- Migration planning
- API-backed clients
What we build
Operations portals, multi-step case handling, and admin applications where consistency across a big surface matters more than a novel interaction. This marketing site is itself an Angular application, prerendered so the pages are real HTML. That is a small example, not the kind of system we mean by an enterprise portal.
When Angular is unnecessary
A content site or a small product UI does not need Angular’s structure. React or Vue may be a lighter fit. We will not introduce Angular into a React company without a reason the team accepts.
Angular for a large signed-in app
Angular when
- A long-lived admin or portal
- A team that wants a full framework
- Forms and roles are the product
Consider a lighter page
- A marketing site
- A one-screen tool
- A team that will not learn it
What we settle for Angular
The version
This site itself is Angular 15. A new product should name the version your team will keep current.
The modules
Lazy areas match the roles, so a clerk does not download the whole company.
The forms
Validation and permission states are designed with the API, not after it.
Before an Angular app
- 01
The life
A long-lived portal, or a short tool that might want less framework.
- 02
The version
The one your team will keep current.
- 03
The roles
Areas that should load only for the people who need them.
- 04
The forms
The validation the API already enforces.
Marks Angular fits this application
- 01
A large signed-in app
The reason is a broad product with modules, forms, and roles.
- 02
Forms match the rules
Validation is the business rule, not only a red border.
- 03
Routes are the product
Navigation follows the jobs people do.
- 04
A module can grow
The team can add a feature beside the existing ones without a rewrite.
What we build
Workflow applications
Long forms, wizards, and role-based navigation with a predictable structure.
Design consistency
Shared form, table, and dialog behaviour so features do not invent their own.
Migration planning
A path off unsupported Angular versions that keeps the business running.
API-backed clients
The UI consumes a real API. It does not become the place rules are silently reimplemented.
Related reading
.NET
ASP.NET systems for organisations that already run on Microsoft.
Java
Spring Boot services for systems that must still be clear in five years.
Web development
Portals, dashboards, and customer web apps built as products.
UI/UX design
Flows and interfaces tied to the system that will actually be built.Questions we hear
Which Angular version do you start from?
A supported current version. This site is Angular 15 because that was the requested platform. New client applications are discussed against the version your team can maintain.
Can Angular serve public SEO pages?
Yes, with prerendering or server rendering, which is how this site is built. A purely client-rendered app is a weak public website.
Do you pair it with .NET or Java?
Often. The server is chosen separately. Angular does not require either.