Goal

My goal with this article is to provide you with different techniques to put all the stuff together and by stuff, I mean components, services and other features that you work all the time in your Angular projects. So, at the end of this article you will be able to build a very coherent application and easy to maintain. Now, building something like this we of course need a solid blueprint. Imagine that we’re building a house, we wouldn’t want to start from scratch and start putting together all the pieces without a blueprint, right? So, why would we start our application without doing those same types of thing? We’re going to focus on planning our application, how we structure a project and how to organize our folders. It’s a good plan take a look to this article at the same time, because they complement each other. Note that this is my personal opinion and you can have a different opinion than me and be totally valid as well. You can talk with some developers in the same room and probably you will get different answers. There is no one right way and I want to emphasize that up front that this article is not about the perfect or right way to build your Angular application architecture. Instead, I will show you different techniques that I think you should consider because knowledge is power and if you know different approaches, in my opinion, you will be able to apply those where appropriate for your project.