This allows us to simulate what the API should return, and how it should display on the front end.

This is important for tests and just general UI testing.

Start off the project!

This might require the help of hiber.

In order to remind users to check for bats monthly (observations) and environment/physical changes yearly, there needs to be a way to push the notification to the user.

Alternatively, we can extend this idea to a list of messages so that the user can also get notifications for when a surveyor is coming by.

Now that we have mcab/hiber running, we need to be able to GET and POST data from the API.

Use hiber's endpoint api/v1/houses to retrieve the houses for that particular user.

Might need to change the representation from the API.

Need to display the x most recent environment / physical features. Probably by serializing on hiber's end the most x recent features from api/v1/houses.

If we click in to more detail, then we can list further features.

This should be all of the information listed under the House model in hiber. The specific questions to ask are underneath the Epicollect 5 document. Ideally, there is a JSON file that is loaded on page load that has all of the questions, selections, and the component to use for that form.

Have to consult the Ionic documents to style the form.

Currently seeking a quick way to polish out UI a little to ready it for demo day. After this we can try to connect the flightplan and Hiber and call it a completed senior design project

Similar to #8, there should be a button that takes you to a form to submit information about an observation. It should default to the current datetime for creation.

We'll probably use CircleCI to build and test the project.

When there is no internet connection, the application should not allow you to send forms, but it should save what forms you have in the pipeline. When internet connectivity is restored, then the forms should be sent.

This is related to #12.

Any tests should be able to rely on this mocked data to see how the UI interacts when certain actions are triggered.

Cypress comes in handy here.

UI is not set on this, but for a listing of houses, there should be a button to add environment / physical features, which will pop up this form. Ideally, it has the same structure as mentioned in #7.

We didn't really need to have the entire app load at the start. We would ideally want to lazy-load paths, but due to the way either:

1. service-worker.js served files
2. Webpack bundled those files

we weren't seeing them appear in the PWA.

My guess is that it's closer to 1; while serving in dev mode, Webpack was easily able to bundle and serve the files normally.

Similarly, if any errors occur client side, we'll want to know. We'll probably use Sentry.

Probably need to serialize the x most recent observations in the main houses endpoint, api/v1/houses.

Need to also have a way to get all the observations for a house.