The focus of this podcast is about how to use Angular Modules the right way. You'll discover how many modules your application really needs. Also, if you've ever wanted to create a custom Angular module to share and distribute - this podcast provides the information you'll need to create, publish, and use your custom module. Free Guide: http://angularlicio.us/custom-angular-modules The whole notion of modules is to create reusable items to improve efficiency and minimize maintenance of source code. The base element of an Angular application is a Module. Each Angular application contains an app.module that is the entry point of the entire application. Therefore, you are already familiar with using modules. Also, it is very common to create additional modules in an Angular applications. However, what if you want to create Angular modules that can be reused in more than a single Angular application? Or, would you like to create custom modules that can be published to NPM and shared with the world? Think of modules as containers of realted things. Even if you never create a custom module that is distributable, you can still dramatically improve the design of you existing Angular applications by creating modules to encapsulate and organize specific feature sets. Angular modules let you decide what items within the module are publicly available. For example, if you create a module that contains an Angular Service, it can act like an API that provides end-points to the application to perform different actions. You get to use and implement some nice architectural patterns that provide: - A service facade pattern to provide end-points of functionality. - Abstract the implementation details to private members of the module. - Create a highly-testable service using specification tests. Encapsulation of many items used to implement the feature set.