In general, Angularjs1 works in 2 phases :-
b) Binding / Runtime
During the configuration phases, Angular has concepts like module, controller, services, providers and components (ui components)
Typically we worked with App -> Controller -> Services / Factory etc
Why use Factory and Value recipes?
Long, long time ago, we have factory and we have values recipes. These becomes the cornerstone for laying down other components in angularjs (again we are repeating ourselves - module, controller, services, providers and components (ui components)
Because Angular injects various dependencies.
Factory recipes allows :-
- Lazy initialization
- Leverage on other services from a module or modules
- Service initialization
Value recipes is something like a key value pair that gives key / value definition for data-binding in angularjs.
Example of value recipes are as follows :-
var myApp = angular.module('myApp', );
Provider = $get
Service instance are singleton in Angularjs
What the heck is angular directives. Good exmples would be html element types that you laid down on your html mark up like ngmodel, ngbind.
Also note that the following means the same thing, ng-model
Directive 'restrict' options that is available :-
Only One Ng-App
You cannot have more than on ng-App in your application.
What happens when Angularjs bootstrap?
A simple example of Angularjs directive can be found here.