It gets overwhelming quickly when trying to explain Angular from an abstract point of view. By this I mean to explain how it works before showing what it does.
This is a brief introduction to Angular, just enough to give us an idea of what it is. 😉
When to use Angular?
Angular is used for complex client side applications.
Why to use Angular?
The idea of using frameworks in general, and Angular in particular, is to switch the focus from building all the plumming/glue code to your own business logic (things that offer value to your clients).
So, you spend less time worrying about coding all the general features (functionality), and concentrate on implementing the requirements.
Static and Dynamic
The more dynamic your website needs to be, the more time consuming it becomes to implement it.
This dynamic facet is determined by interactivity (modals, pop-outs etc.), forms which can easily be achieved through Angular Features like: Data Binding, Component Model etc.
- Dependency Injection
- Component Model
- Change Detection
- State Management
- HTTP Requests
- Data Binding
How does Angular work?
Angular was build in mind to be modular (to offer modularity – a code is modular if it's split into multiple pieces which can be added together in various ways).
So, the architecture of Angular (how it's built) is made of components. These allow you to reuse components in different parts of your application (for instance: you need a Modal Dialog in multiple pages). This modularity is backed by Dependency Injection.
How to write Angular?
The idea of TypeScript is to offer you an environment which is type-safe in order to reduce bugs, increase productivity and write better code (but not in all cases though).
- Type Annotations