Google Developer Expert | Auth0 Ambassador | Media Developer Expert at Cloudinary | Twilio Champ | Technical Coach at SpringBoard | Google Women Techmaker | Postman Supernova | AWS | Microsoft MVP
When I worked at CSX, the rail road company. We used NgRX in the ShipCSX application. We chose to use NgRX not at the beginning(sadly). We started developing the app that is massive, but after the first MLP we noticed the need of using NgRx since they were so many things going on that, it was hard to keep track of the state of our app. We were doing sorta of a state management using services at the beginning, and we were kinda re-inventing the wheel. Then after the MLP, 2 devs had to do the migration of the app to use NgRx (it took a minute or 2). I know NgRx is used in different ways across every organization and even across different projects. The way we used it was to handle the state management of the data, and some of the UI state. For example, we were using PrimeNG component library, and some of the components that they build like the sidebar already come with the toggling effect of opening and closing the sidebar, so we didn't change the "native" behavior of the components from PrimeNg to use NgRx. If we built the components in house, then we did use NgRx. Those are my 2 cents. Now where's my swag Wes. Jk jk ;) hope this was helpful
Director of Architecture, Chief Architect at Briebug. Google GDE for Angular/Web Tech. I’m a huge weather nerd. I’m here if you need help in Angular, ASP.Net Core, or best practices.
Location
USA
Education
School of Hard Knocks
Work
Director of Architecture, Chief Architect at Briebug
When I worked at CSX, the rail road company. We used NgRX in the ShipCSX application. We chose to use NgRX not at the beginning(sadly). We started developing the app that is massive, but after the first MLP we noticed the need of using NgRx since they were so many things going on that, it was hard to keep track of the state of our app. We were doing sorta of a state management using services at the beginning, and we were kinda re-inventing the wheel. Then after the MLP, 2 devs had to do the migration of the app to use NgRx (it took a minute or 2). I know NgRx is used in different ways across every organization and even across different projects. The way we used it was to handle the state management of the data, and some of the UI state. For example, we were using PrimeNG component library, and some of the components that they build like the sidebar already come with the toggling effect of opening and closing the sidebar, so we didn't change the "native" behavior of the components from PrimeNg to use NgRx. If we built the components in house, then we did use NgRx. Those are my 2 cents. Now where's my swag Wes. Jk jk ;) hope this was helpful
Awesome bro! Thanks for sharing. I’m bringing NgRx swag for you when I come up to Angular JAX. Just say the word.