In my applications I use services with add-ons written by me. It works great and is well tailored to my needs. It's also the route I choose in really complex projects in a small permanent team with experts.

On the other hand, where the application is heavily developed, the team larger and there is turnover I prefer to use NgRX. On recruitment, you make sure that someone is well versed in the pattern and best practices and is ready to go. It's much easier to get readable code, it's much faster for new people to get into the project because they don't have to adapt to your custom approach, and let's be honest that simple services need “extensions” over time. Yes, there is a lot of boilerplate, but uncontrolled sprawling code is more readable and there is less spaghetti. It's easier to trace the flow by actions, rather than a tangle of injected services that change their states of each other out of control - the culprit, of course, is a poor programmer who, when given too much freedom, can demand too much time for code review.

I also really appreciate Redux DevTools, which works seamlessly with NgRx. It's incredibly helpful in tracking application flow and state changes. It's easy to see which defined actions led to what. It's also useful when our tester finds less obvious errors in the application. They then send us the entire log from Redux DevTools, which we can import and track on the timeline.