Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Angular JS at NOW TV

An overview of why AngularJS is our Javascript MVC of choice

Andrew Merrell

on 6 December 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Angular JS at NOW TV

AngularJS at NOW TV
Requirements for our
Javascript framework

Andrew Merrell & Caroline Bourdeu d'Aguerre
Why we selected AngularJS
We reviewed a few Javascript MVC frameworks and here's the reasons we choose AngularJS:
A few more reasons
Angular was
built with testing in mind
, there are helpers and mocks to use for core Angular functionality. Including E2E & unit test runners.
We can write
services to fetch and transform data
The view drives the controllers and models.
Angular is great for single page applications.
Routing is built in
, you can depend on services to resolve before rendering views.
Uses the HTML 5 History API and has fallbacks.
Steep learning curve when it comes to complex problems.
Documentation is not great but is rapidly improving.
Testing directives and promises is not easy.
Directives can have controllers & compiles, pre linking, linking and post linking.
Which one is the best to use?
Choosing when to use a factory, service or provider.
AngularJS website
Choosing an MVC with TODO MV*
Egghead.io - short video tutorials
More detail on some of the reasons we like AngularJS
E2E testing Angular with WebDriver
Understanding how Angular DOM binding works.
Brian Ford - AngularJS Developer
2 way data binding
is easy.
Dependency injection
, less boilerplate needs to be written to connect models, views, controllers and services together.
way of building the app, by adding attributes to existing tags.
, extending the HTML language.
It's modular
, you need only include the core, but google have written some helpful modules.
Not required to use models, we can use
plain Javascript objects
, we just update the object.
Where next?
Where we want to go with our web application.
Single page app.
How do we ensure SEO?
How do we ensure browser performance?
Allow us to cache pages easily by moving work to the client side.
We tried to build our Javascript in a structured way, we wanted a framework that would give us structure.
A framework that would be easy to test.
Reduce UI flickering as much as possible.
What we liked
Proper MVC on the front end, with a good structure.
Easy to create a single page experience.
We can create components (Directives) which can be easily reused (Modular).
Easy to add 3rd party modules and directives.
Full transcript