Hercules React Native to XRE - Cleanup and animation updates

This challenge is part of a new project involving React Native.  The eventual goal is to have a way to build React Native apps for Hercule's embedded devices that communicate with the device over websockets, using the proprietary XRE messaging protocol.  They would like to see if we can build a React Native translator that sits on a server and communicates with clients, sending them XRE messages to draw the React Native components.

Basically, we are going to stream apps to a client and update the client based on actions that raise events from the client to the server.

This challenge will implement fixes for some recent deficiencies, will reorganize the documentation, and will add some new animation classes.

Requirements:

These tickets comprise the requirements for this challenge:

* https://gitlab.com/hercules-react-xre/react-xre-poc/issues/20
* https://gitlab.com/hercules-react-xre/react-xre-poc/issues/21
���* https://gitlab.com/hercules-react-xre/react-xre-poc/issues/22
���* https://gitlab.com/hercules-react-xre/react-xre-poc/issues/23
���* https://gitlab.com/hercules-react-xre/react-xre-poc/issues/24
���* https://gitlab.com/hercules-react-xre/react-xre-poc/issues/25
���

Navigation

Note that any samples and demos must be navigable by the keyboard.  Right now we have support for these keys:

* left
* right
* up 
* down
* enter
* backspace


Native validation

To prove out the solution, we need to ensure that a native mobile build of an app matches what is displayed in XRE.  Please provide documentation on how to compile each example and run it in Android or iOS, and please also provide this information as part of your submission video.

Background

The server side "screens" will be implemented in React Native, using React classes. 
The goal is to make sure the React Native definition is generic, not custom to XRE.  The normal React Native development process will apply on the server.
 

Final Submission Guidelines

Please see above