Hercules PxScene Showcase App - Animation updates and clean up

The PxScene Showcase app will be an app that runs in pxscene (pxscene.org) that displays a functioning UI for browsing videos.  It will be used by the client to show off the capabilities of pxscene on embedded devices.

This challenge will update the existing app to integrate new animations, clean up keyboard navigation, and fix up a few things in the UI

Target environment

We are targeting pxscene for this challenge.  Note that pxscene applications are implemented in Javascript but use custom APIs for drawing and animations.  You are expected to investigate the documentation for pxscene and implement things according to pxscene best-practices.

http://www.pxscene.org/docs/apis/index.html
https://github.com/pxscene/pxscene

Further examples can be found here:

https://github.com/pxscene/pxscene/tree/gh-pages/examples/px-reference
 

Requirements

These tickets comprise the requirements for this challenge:

* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/7
���* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/8
���* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/9
���* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/10
���* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/11
���* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/12
���* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/13

Performance 

Performance is important for this challenge.  Navigation should be snappy, and pages and images should load quickly.  You shouldn't change anything to hamper performance.

Styling and redundancy

Styling and general Javascript should be as clean as possible, with little to no redundancy (DRY).  For instance, if each screen is a different JS file, don't copy / paste style details or redundant methods to each file.

Code layout

The code should be well encapsulated, documented, and designed.  This will be a reference application, so no hacks or bad code will be acceptable.

Submission

You should submit your code as a patch file against Git commit hash 301b9d50621481d218e6b1788f921772caaf85b8 or later.  Git details can be found in the forum.

Make sure your submission includes:

* An updated, deployable project that includes the required changes, via a git patch
* Deployment documentation, including how to deploy to Heroku
* A video showing a walkthrough of the updated project in pxscene
* Validation documentation for loading the project in pxscene from Heroku