On Github yearofmoo / fitc-rtec-angularjs-slides
FITC Toronto, December 2013
By Matias Niemelä
Eight major AngularJS articles.
Great resource to learn about AngularJS.
Talk about Real-time web applications
How to integrate Real-time features
Explain that AngularJS is the right tool for the job
Show how to master the UI of your real-time application
Briefly talk about testing and maintainable code
An amazing framework for building dynamic web interfaces
Runs in the browser not on the server
But your backend can be anything
Does this ring a bell?
Let's do a quick example
Traditional websites -- little or no AJAX here
AJAX web applications -- SPA applications
Fully Real-time applications -- WebSockets
But what about a mixture of all three?
Content renders on screen faster and seamlessly
Easier and easier to make websites dynamic
More control over what changes and what stays
But...
More AJAX === a more instantaneous expectation
The gap between expired and instant becomes smaller and smaller
users will eventually expect applications to be fully real-time
So webapps should not require the user to refresh the page anymore
Does the page update when the user walks away from the screen?
Why do we really need a refresh button?
Hook into the hashbang/pushState URL change
Figure out what page to download
Update the body of the page
Perform a fancy animation
AngularJS FTW!
Use AJAX from the start (standard SPA application)
Then apply real-time effects as you go?
What is the first problem that comes to mind?
Lets try and use pusher.js to update a page
Update collisions between AJAX data and Real-time data
Dependency issues
Disorganized Code
Problematic or absence of testing ... How do we test this?
Standard SPA/Traditional websites primarily
Uses WebSockets (a real-time connection) to enhance the experience
Gracefully degrade for older browsers
Kind of like a mobile first approach to making real-time applications
You don’t need to make the entire website using a real-time backend
Github (PR pages)
Asana (tasks)
Facebook (chat)
Our demo application...
The scoping system allows for an easy way to update data
Directives & Expressions can update the DOM as the data changes
Animations can make it look nice
AngularJS can work with a non-angular application
Bindings, directives and expressions listen on the scope
The scope is your in-memory database
Place AJAX and/or real-time data into the scope
The page updates, renders and animates
Lets try and use pusher.js
With angular.js
To make a Real-time application
Native WebSockets
Socket.io (code wrapper)
Pusher.js (streaming service)
Firebase (full backend service)
Grunt, NPM + Bower
Karma with Jasmine (unit testing)
Protractor (end to end testing)
AngularJS 1.2 (ngRoute + ngAnimate)
Pusher.js
A simple Rails app to manage the admin
JBuilder for the API
RailsAdmin for a pre-made admin
Whenever the model changes, upload to pusher
Simple crud application that uses AngularJS and an API
Routes, pages, views and styles
Users, comments, images and more
Nice, clean JavaScript code
Real-time effects update the page as things change
The user instantly knows when something has changed or been added
Animations enhance the experience...
Use angular-animate.js with 1.2
Include the ngAnimate module
Supports CSS3 Transitions / Keyframe animations
Supports JS callback animations
Let's examine some animations in the app
Brand new feature with 1.2
Lets place a stagger on the home page for the users
Stagger the comments
Jasmine tests the JavaScript code
angular-mocks.js provides mocking support
Karma runs the tests on all browsers
What is Protractor?
How does it work?
What can you test with it?
Let's test it out
Thank you for making this possible
Feel free to contact me via matias@yearofmoo.com