• beta.9 update
• better prerendering support
• support for many applications on server-side
• polyfill removed now as import 'angular2-universal-preview/polyfills';

see universal-starter for changes
https://github.com/angular/universal-starter/blob/master/src/server.ts

Necessary particularly for Service

Since one goal of this project is to be building Angular CLI add-ons for the best practices in this project (Web Workers, Universal, HTTP/2, ServiceWorker, etc), we should have a script to generate the answers app using Angular CLI (plus some custom macros), which can then be tested with the same E2E tests as the hand-written app.

• Disable authentication requirements on server
  • Set up a Github app token
  • Configure Firebase for Github
  • Create login status widget
  • Auth service to manage state

• Create Github App
• Set app tokens in Firebase authentication

• Integrate with Question routable component
• Build a component where the answer can be entered
• Integrate with questions Firebase-based service

• Set up an HTTP/2 server for local and deploy
• Continuous integration deployment with GH/Travis
• Configure SystemJS for HTTP/2-optimized barrel loading
• Get a certificate
• Get a domain
• Set up Firebase

with the release of 0.50.x universal has been updated to angular2 2.0.0-beta.3 you can also prerender the application so you won't need to keep your index.html shell in sync with your application.

• Establishing declaration format for ServiceWorker to track what files to cache
  • Writing Service Worker script to manager caching of static files
  • Experiment with intelligent upgrades from app version to version
  • Generate manifest for AppCache from declaration format

• Set up Karma + Jasmine
• Set up Travis testing

We want to experiment with a way to take a service written as if it was written to be executed in the UI thread, and have it automatically wrapped and executed in UI and worker. @jteplitz602 and I began experimenting with using a monkey-patching decorator to do this: http://plnkr.co/edit/8ksPT8TxTocBkOHvuPP0?p=preview

It's hacky to have a decorator doing so much monkey patching, but would be a good start to figuring out how to make this problem easier to solve in Angular in general.

Right now unit tests just run in Firefox on Travis. They should be run against more browsers, particularly mobile browsers.

• Set up docker image with h2o
• Generate h2o configuration as part of build pipeline
• Set up container engine (including certificates)
• Integrate automatic deployment into Travis

• Create a routable RecentQuestions component
• Create a dumb QuestionsList component
• Create a typeahead-style component
• Create a dumb QuestionItem component for rows

Follow-up task to #17

atm the worker sends a message to the ui after bootstrap has completed to tell the UI to call preboot.complete. However, even though bootstrap has finished on the Worker it has not necessarily finished on the UI when this message is sent. Generally, this results in a flash since there is a slight delay as the server rendered components are removed slightly before the bootstrap components are rendered. It also means we lose the events that preboot is trying to replay.

To fix this, we need a way to know that bootstrap has finished on the UI as well.

In my PR, there is a try/catch around the new Firebase() line because it was raising an exception when rendering with Universal. This should be fixed to actually create a node-friendly Firebase instance instead of just giving up.

• Set up benchpress infrastructure for local testing
• Measure time to see content
• Measure time to finish preboot

We should start shrinkwrapping dependencies since so many fast-moving projects are used in this project. Right now we lock dependencies in package.json, which gets us some protection, but we should shrinkwrap to protect from dependencies of dependencies.

We should re-use tools from angular/angular, like the script that generates a clean shrinkwrap file.

• New Question routable component
• Dumb component for editing question content with markdown support
• Service to manage questions with persisted cache

App will run in a web worker by default.

• Have app bootstrap from worker
• WebWorker should play nice with Universal
• Make custom element wrapper for Material Design Lite lifecycle management
• Perhaps a wrapper for markdown editor (CC @robwormald)
• Make sure implementation works with popup or redirect authentication flow in #1
• Add preboot library to app

We should be able to performance test different measurements with different variables.

Things to measure:

• Time to first interaction on first page load
• Time to first interaction on subsequent page load
• FPS of interactions with certain components

Variables

• With service-worker caching
• With HTTP/2 server
• With throttling
• With Web Worker
• With bundle or with unbundled library

I could re-use most of the rules from the example app I created: https://github.com/jeffbcross/qa-app-demo/blob/master/security-rules.json