Challenge Overview
Describe what you want to accomplish.
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 animations support.
Requirements:
React Native has support for animations of only a few types, but they can cover a large mix of possible combinations:
https://facebook.github.io/react-native/docs/animations.html
The XRE specification is also robust with regards to different possible animations and how they are supported.
This challenge will implement the animation support in React Native, mapping that to XRE. Note that there may be mismatches or things that can't be implemented in a 1-1 way. If there is an issue with any of the mapping, please mention it in the forum ASAP so we can discuss how we'll handle that within the scope of the original challenge.
The XRE specification will be provided in the forum.
Sample app
You must provide a relatively robust sample app that demos the various animations and how they are supported in React and XRE. This should be more than a simple demo and should cover a good number of different combinations of the animation options.
Note that any sample must be navigable by the keyboard. Right now we have support for these keys:
* left
* right
* up
* down
* enter
* escape
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.
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 animations support.
Requirements:
React Native has support for animations of only a few types, but they can cover a large mix of possible combinations:
https://facebook.github.io/react-native/docs/animations.html
The XRE specification is also robust with regards to different possible animations and how they are supported.
This challenge will implement the animation support in React Native, mapping that to XRE. Note that there may be mismatches or things that can't be implemented in a 1-1 way. If there is an issue with any of the mapping, please mention it in the forum ASAP so we can discuss how we'll handle that within the scope of the original challenge.
The XRE specification will be provided in the forum.
Sample app
You must provide a relatively robust sample app that demos the various animations and how they are supported in React and XRE. This should be more than a simple demo and should cover a good number of different combinations of the animation options.
Note that any sample must be navigable by the keyboard. Right now we have support for these keys:
* left
* right
* up
* down
* enter
* escape
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.
Submission
Your submission should be a patch file in Git against commit hash 20e77248f4e576d02ea9e75456b568d3a089adde
NOTE: You are free to change, reorganize, and refactor the code as you see fit. You are not required to stick to any past decisions on architecture.
Please make sure your updated README covers:
1. How to deploy the server-side to Heroku
2. How to configure the client XRE receiver to connect to the server and work with the different apps available
3. What the React Native app looks like and how the animations work
A video is required, but it only needs to cover the validation (XRE and native), not the setup. Having the setup details only in the README is fine.
Links:
https://facebook.github.io/react-native/���
https://www.youtube.com/watch?v=hDviGU-57lU
Your submission should be a patch file in Git against commit hash 20e77248f4e576d02ea9e75456b568d3a089adde
NOTE: You are free to change, reorganize, and refactor the code as you see fit. You are not required to stick to any past decisions on architecture.
Please make sure your updated README covers:
1. How to deploy the server-side to Heroku
2. How to configure the client XRE receiver to connect to the server and work with the different apps available
3. What the React Native app looks like and how the animations work
A video is required, but it only needs to cover the validation (XRE and native), not the setup. Having the setup details only in the README is fine.
Links:
https://facebook.github.io/react-native/���
https://www.youtube.com/watch?v=hDviGU-57lU