Add Nimbledroid endpoint #39

armenzg · 2018-07-04T15:31:57Z

This is to support this issue on the frontend.

I've considered not implementing this API on the backend since we could have just used the frontend and cache it, however, there are some reasons I want to document as to why I believe it should be done on the backend.

Fetching directly from Nimbledroid (public sample gist) takes a long time which would have meant a very slow first load for the client
The compressed transfer is less than 200KB and 2MB on disk. I will be dropping the console_message from each entry to reduce the data size. If we need it we can add it later.
We can add a Heroku scheduler to warn up the cache in advance. This will improve the client's first load time

* Add documentation to enable Nimbledroid fetching * Heroku review app configuration changes to copy Nimbledroid env variables * Add /api/android/nimbledroid endpoint * Add central configuration file * Switch from 'node-fetch' to 'isomorphic-fetch' to support tests with 'fetch-mock' * Add Nimbledroid tests

* Add documentation to enable Nimbledroid fetching * Heroku review app configuration changes to copy Nimbledroid env variables * Add /api/android/nimbledroid endpoint * Add central configuration file * Add Nimbledroid tests

armenzg · 2018-07-15T11:30:10Z

This landed few days ago.

armenzg added the enhancement New feature or request label Jul 4, 2018

armenzg self-assigned this Jul 4, 2018

armenzg closed this as completed Jul 15, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add Nimbledroid endpoint #39

Add Nimbledroid endpoint #39

armenzg commented Jul 4, 2018

armenzg commented Jul 15, 2018

Add Nimbledroid endpoint #39

Add Nimbledroid endpoint #39

Comments

armenzg commented Jul 4, 2018

armenzg commented Jul 15, 2018