Application development
Modules, routing and state organised against how the business is structured rather than how the first screen was drawn.
Angular
Angular application development
Angular development for applications with a long life ahead of them—typed, structured and conventional enough that the next team can read the code without an introduction from the last one.
What this coversAngular
Long-lived enterprise front ends that survive a change of team.
Component and design system work
A shared component layer so a large application looks and behaves like one product.
Integration with enterprise services
Connecting to the identity providers, gateways and internal APIs already in place.
Version upgrades
Moving an application forward across Angular versions, with the scope of the change assessed before it starts.
How it is judgedBefore you commission it
When it fits
- The organisation standardised on Angular and the work has to fit that decision.
- The application will outlive the team currently building it.
- Several teams are contributing and the conventions have drifted apart.
- An upgrade has been postponed long enough that nobody wants to start it.
How it is built
- Angular conventions followed rather than reinvented, because convention is what makes a handover cheap.
- Typed interfaces between components and services, so a contract change surfaces at compile time.
- State kept where it belongs, rather than lifted globally by default.
- Accessibility and internationalisation treated as build requirements when the organisation needs them.
Not this
- Migrating away from Angular without a reason to
- One-off screens with no place in the application
- Infrastructure administration as a standalone service
Common questionsAngular
Can you assess an application before an upgrade?
Yes, and it is often the sensible first engagement: what is deprecated, what is custom, and what is no longer used at all.
Can you work alongside our internal team?
Yes, including in a supporting role where the team holds the domain knowledge and needs a defined piece of work delivered next to it.
Do you work to our existing conventions?
Yes. On a long-lived application, matching the conventions already there is worth more than any preference of mine.
Platform Build & ExtensionMVP Build SprintArchitecture & PlatformSoftware EngineeringUX/UI Design & ResearchProject & Delivery Management
Take the session when the work still needs scoping. Send the brief when you already know what needs building.
A clear next step
Start with the decision in front of you.
Get preliminary direction first, or book a focused session when the question is ready.