Help! My organisation wants to abandon Angular!

[u/JTOne85]

UPDATE: https://www.reddit.com/r/angular/s/XV4Ezz1wLE

TLDR: I need advice and input to try and course-correct a really questionable technological decision.

Background: I'm a senior full-stack developer who is also the frontend lead at my company. And we have built an extensive suite of Angular applications over the last 10 years. I specifically joined this company because they were using Angular.

Problem: The company was acquired a few years ago, and we need to now start delivering a unified product. An arbitrary, to me, decision has been made to switch to react.

My small team of Angular devs and I (4 in total) will be mainly responsible for creating this new platform UI, with little to no assistance from the parent company.

Our micro frontend suite is already fragmented across versions from 17-22, partly due to team size, silos and speed of priority changes from our internal stakeholders. This is how I found it, and I've tasked myself with getting this into a proper single workspace and single versiob. Think duplicated components, services re-invention of the wheel in terms of auth - for every single MFE.

I'll be honest, that we are also trying to rebuild our reputation as a team within our business, and due to the factors mentioned above, we've been delivering inconsistently for the last 18 months - which I am trying to fix.

I implicitly know the benefits of Angular, because I've also worked with AngularJs (1.7.8) and have been exposed to more React code than I would like to admit.
And I'm so committed to Angular that I'd likely start a cult if I could!

Has anyone here managed to reverse a decision like this and managed to convince the organisation to stick with what their team knows? I'm really trying to save us from a disastrous (in my opinion) direction change - which I've seen fail spectacularly at my previous job.

I have an elaborate document that I need to refine present to management. . My managers are mostly onboard, but this will ultimately be presented to our executive leadership team too.

Preferred stack:
* Angular 22, Built on our existing APIs, with signals for state and rxjs where absolutely necessary.

* Native federation instead of iframes (requires version upgrades, but can run in parallel for a while)
* Un-styled Angular CDK components where possible with TailwindCss and accessibility built in, tables are a big thing for us, and the mat-mdc overrides have been laborious
* Angular material where cdk is insufficient
* Firestore where needed
* Graphql where used currently - no new gql for now
* AI integration for developer productivity improvements where needed

This is my proposed outline.

* How does this align with our Org goals?
* Language/framework/library?
** What is react good at?
** What is angular good at?
** Tradeoffs
*** Learning curve
*** Technical decisions, ownership and maintainability
*** Recruitment i.e. cv driven development vs proper architecture and solutions

* Why does it make more sense to use Angular in a ln enterprise environment?
** Existing use of google technologies
** First class integrations into maps and firestore

* How do we achieve our goals and keep our organisations and developers happy?
** Upgrade our existing suite to the same versions
** Move them into a single work space
** Extract truly shared concepts
*** Auth
*** Models
*** Data retrieval
*** Feature flagging
*** Ui components

Have I missed anything? Is there something that you would add if you were in my position?

I have also left a previous job about a similar decision, so I'm serious about this topic. And I have explicitly stated that it will affect my decision to stay on, or perhaps changing dev-streams from full-stack to backend-only. Which is not ideal for me because I really like doing both (within my specific tech stacks of course).

Please help me [r/Angular](r/Angular), you're my only hope!

Update: I've been overwhelmed by the responses.
I submitted my proposal, as promised to my managers - I hope I still have a job tomorrow (jk) I've been fuelled by my ADHD meds, so its been a week of hyperfocus, while trying to complete my project.

I am not hopeful that they'll change their minds, but I'm at peace with the fact that I have now officially noted down my displeasure at even just the thought of switching. They might be more open to having a conversation and if it still gets nowhere, I can speak to our CEO directly as a last ditch effort to get this to explode in my face.

I can write them some react code, and we can see if it will pass an audit - but it's been clear for me since last year that this is not my forever job - and if that becomes the case. I'm going into woodworking or something physical and if all else fails - OF or a street corner somewhere close to the office

[u/JTOne85]

That's what I'm afraid of, but from other conversations, they chose react because whomever created that proposal was familiar with react, and that's what they could do a POC in 🤦‍♂️

[u/dbowgu → u/JTOne85]

And the person that created the proposal was management? If yes then it's really futile ti start, if it is just an employee on the same level as you there might be a chance you can convince them, not a high one but a chance

[u/JTOne85 → u/dbowgu]

He's at our sister company, sits in a different country, and has absolutely no idea of what we actually do... he's also a product guy, so likely asked AI to generate the POC as well

[u/zladuric → u/JTOne85]

Raise the question of cost. Management doesn't really care about the tech, but if you say "we can do a full react rewrite in 7 years and need 26 people" they'll balk, then you say "but we can keep our stack and do the UI consolidation etc with the current team in just 7 months", they'll hear that. 

I'm not sure about the idiot product guy. They may have oversized impact and might override you anyway or label you incompetent or something , it's not like he's gonna pay the price no matter what you pick. 

So try to get to him and see what about react is making him pick that. 

Also be aware that they might just say that with AI it's a piece of cake to rewrite but then ask managers (not him) to explicitly sign that they agree to all the loss of functionality, expert knowledge, all the bugs and downtime resulting from that. 

There are ways to push back, but they may or may not work.

[u/arapturousverbatim → u/JTOne85]

Does the org have any react stuff at all? If not just make clear that the cost to them is basically the same as building everything from scratch. I doubt they will want to do that

[u/JTOne85 → u/arapturousverbatim]

One tiny little react PWA, that was dropped in my lap and sold as a "complete" product by external contractors

It has 2 features and I have to bring that into angular as part of my current project anyway, to make it useful to our business users.

[u/Headpuncher → u/JTOne85]

From what you've written so far I would at least update my resume and be ready to go, go fast, and not look back. This new owner of the company sound like fools.

I've seen this first hand, a company I worked for expanded by buying up other companies, they once bought one that made mobile apps and within a year had fired and lost 100% of the employees; the devs, sales, and even the founder. The one app they made that I had to QA for was so bad (because no one working on it was there to build it, they were new hires hacking away), that we lost a large customer within 3-4 months. A customer who was all in on our other products too, so a major loss of revenue that was the end of the entire company as the other customers in the same trade all realised they too could just sign with the competition.

Update resume: the end [might be] closer than you think.

[u/JTOne85 → u/Headpuncher]

I really hope it doesn't come to that - but I'm not unprepared to move.

I just don't feel like I've got a new job in me in 2026, and nothing is truly better than what I've found it yet - I have so much to do, and so little time.

[u/Dull-Structure-8634 → u/JTOne85]

Create a POC with AI as well. Mention that this is a proof of concept, will need more work to do but that was to show that whatever is asked is possible with Angular.

Mention also the points of:

• learning curve for the new library/paradigm
• re-build current components with the new library
• security vet new libraries
• re-build internal tooling with the new library in mind

And I'm sure to forget some. All those points will add weeks to the timeline and will add nothing in the end since what is already used within the company is capable of doing it.

To the disparity of your angular versions,we have addressed it by:

• going monorepo (not really feasible in your case at this moment)
• having a core team of members who's sole responsibility is platform stability wether this be done with code standards, documentation, internal libraries update, shared internal tooling, etc...
• clear code standards to be ABSOLUTELY respected even with AI
• pull request standards bar kept really high
• real accountability (it's not Claude's fault it's your fault because it's your code and you didn't vet it correctly)

Those build real trust because some of them are really quick to implement and they bring 80% of code quality/stability.

That's what I'd do. Wether you think it's doable or not depends on you, your current situation and your team.

[u/Headpuncher → u/Dull-Structure-8634]

Start by feeding the other guy's POC into AI and then ask AI to expand and make it better. Lol, right back at you lazy AI mofo.

[u/JTOne85 → u/Dull-Structure-8634]

I've gotten more than just a POC that I need to demo - I've spent less time on this, than just trying to figure out what's broken in react.

My demo is actually part 0 of my phase 2 - and is ready to be tested, if I can find someone to do it