Thank you for the feedback! 🙌🏻 It depends in your case. Do you provide services at root level / module level / component level? In most of the cases you would want to provide the services at root level. This way you will be able to use the service in the component just by declaring it in the constructor. I recommend the following articles for a better decision: Dependency injection and injectors hierarchy chapter of this article https://angular.io/guide/standalone-components and https://angular.io/guide/providers Based on the last one you can make a great assessment where would you need to inject the provide the services. I hope it helps you!

This is interesting. I'll give it a shot 👍🏻

Template-driven was the first method to build forms that I tried in Angular. After I discovered Reactive-forms, that's the only way that I'm building forms especially that you can build form dynamically. I've seen that it covers a lot of complex scenarios, as you mentioned Here's an example from Angular docs (of course you can expand a lot on this): https://github.com/angular/angular/tree/3a60063a54d850c50ce962a8a39ce01cfee71398/aio/content/examples/dynamic-form/src/app

Angular is a tough cookie for everyone at first. For me it was the same. It 'forces' you to learn some of the concepts like dependency injection or design patterns (factories, observables etc.) that probably you'll encounter in other libraries or frameworks as well but in a later stage. Probably that's why is hard. It gets you out of confort zone.