Do you actually run Angular in production?

Yes. The SunEasy operator console and back-office front-ends are Angular applications we build and maintain ourselves, alongside our React and Next.js work. That means Angular engineers here are reviewed internally against a real long-running codebase, not just interviewed about one.

Angular or React — which should we choose?

Angular when one big front-end is shared across teams and you want the framework to settle DI, routing, forms and HTTP for everyone. React when the interface is the product and you want maximum freedom in composing it. We build both, so we have no incentive to steer you — we recommend the honest fit.

Can you take over an existing Angular app, including version upgrades?

Yes, and staged major-version upgrades are a normal part of that work: we move a system forward version by version while it keeps shipping features. One caveat we will always raise early — if you are still on AngularJS 1.x, that is a migration project with a different shape and cost, and we scope it as one rather than calling it maintenance.

Do you build the backend as well, or only the Angular front-end?

Both. A common shape is an ASP.NET Core, Node or Python API with an Angular front-end, delivered by one Square team — so the API contract and the client stay in sync and there is a single point of accountability.

Angular Development Services

Square builds and maintains Angular applications from our Tirana studio — and we run Angular in production ourselves: the SunEasy operator console and back-office front-ends are Angular apps we own end to end. Angular is our choice when a large front-end has to be shared by several people over several years: dependency injection, routing, forms and HTTP come from the framework rather than from a pile of library decisions, and strict TypeScript keeps the codebase navigable long after the original authors have moved on. We work in Nx monorepos, keep RxJS readable instead of clever, and treat the six-month major-version cadence as routine maintenance. Full CET overlap, fluent English and Italian, EUR 35-55/hour.

AngularTypeScriptRxJSNgRxAngular MaterialNxJestAngular Universal (SSR)

Talk to us Staff augmentation

What we build

Back-office and operator consoles: role-based access, dense data tables, audit trails and export flows
Shared component libraries and Angular Material / CDK design systems inside an Nx monorepo
Reactive data flows in RxJS — live dashboards, polling and WebSocket streams that stay cancellable
Application state in NgRx or signals, kept debuggable rather than clever, with typed selectors and effects
Staged Angular major-version upgrades on systems that have to keep shipping features meanwhile

Why this stack

Choose Angular when one large front-end is shared by several teams: DI, routing, forms and HTTP come from the framework, not from a pile of library choices everyone must agree on
Strict TypeScript and a prescribed project structure keep a five-year codebase navigable — the reason enterprise back-offices routinely outlive their original authors
RxJS is a real advantage for streams, cancellation and coordinated async — and a real cost when the team does not know it well; we staff engineers who do
Angular ships a major version roughly every six months; treating upgrades as routine maintenance is what keeps a codebase off a stranded version
Full CET overlap and EUR 35-55/hour senior engineers, typically 30-60% below comparable Western-European Angular rates

Frequently asked questions

Do you actually run Angular in production?
Yes. The SunEasy operator console and back-office front-ends are Angular applications we build and maintain ourselves, alongside our React and Next.js work. That means Angular engineers here are reviewed internally against a real long-running codebase, not just interviewed about one.
Angular or React — which should we choose?
Angular when one big front-end is shared across teams and you want the framework to settle DI, routing, forms and HTTP for everyone. React when the interface is the product and you want maximum freedom in composing it. We build both, so we have no incentive to steer you — we recommend the honest fit.
Can you take over an existing Angular app, including version upgrades?
Yes, and staged major-version upgrades are a normal part of that work: we move a system forward version by version while it keeps shipping features. One caveat we will always raise early — if you are still on AngularJS 1.x, that is a migration project with a different shape and cost, and we scope it as one rather than calling it maintenance.
Do you build the backend as well, or only the Angular front-end?
Both. A common shape is an ASP.NET Core, Node or Python API with an Angular front-end, delivered by one Square team — so the API contract and the client stay in sync and there is a single point of accountability.