terra-docs

Back to home

Meeting Minutes

Overview of KEY decisions taken:


27th April 2022 - First Internal Meeting

Agenda:

What they do: Terra links data originating from wearables from multiple different companies (including Garmin, Fitbit, Peloton etc.) and makes them accessible to developers on a single API. This sees them act as a middleman between wearables and developers by creating an easy link between the two that can be used to analyse multiple health and wellness parameters.

What they want us to do: The task they have for us is to present graphics that depict interesting data analysis based on historical data. This is left rather open-ended for us to choose what analysis we want to do but will need to be presented on a dashboard with plots and potentially insights/correlations on the given data. The goal of this is to entice less tech savvy customers to observe the potential of what Terra can do with their platform and present this visually to elicit a more immediate and positive response from someone who might not understand the concept fully to start with. Regardless of the level of understanding of their platform it is a logical next step in the evolution of their company.

Factors to consider: The task is left up to us to decide how we use data available to us and what analysis we want to do. It is necessary to consider that a user might not have multiple apps/datasets that encompass some of the things we might want to draw correlations between, e.g., user might only have data for their sleeping patterns, which would mean we cannot analyse how their sports performance is affected by this. As such we discussed a couple approaches to this. The first was potentially to use machine learning on other historical data of similar profiles so that we could provide a dataset for our missing parameter given we obtain a few details from the user (could be height, weight, gender, age etc.). Another idea was to limit our analysis to just using the given data from which we could provide some interesting insights (looking at someone’s sleeping patterns and recommending how they might improve their quality of sleep). We will also have to consider how the user is able to view data as the idea is to create a custom dashboard for users to select what they want to observe depending on what insights are available given their data.

What we actually have to do: The idea is to create a website to view this on with the potential to move this to an app in the future. For the backend Node.js was agreed on while frontend would be implemented using React. We will also need to have a database which we can pull data from to display our analysis on the website. This will also involve authentication via the backend to ensure use of a Terra account. From this we were able to decide on goals for the first week which are as follows:

Minutes:


28th April 2022 - First Meeting with Terra

Preliminary plan:

Data to display:

Ideally have wearables track multiple aspects of health/wellness (e.g. sleep and sports performance), but have to take into account that some users may only track one thing and as a result need to have graphics for just that.

Possible datasets for analysis:

Sleep: How will we quantify quality of sleep?

Can we use a formula to produce a sleep quality index (1-10)?

Sports Performance: Should focus on cardio (running, cycling etc.) as hard to track weightlifting from wearables’ data. Factors/variables we could use:

Could use extra variables like VO2 max if wearables provide data

This would be most straightforward analysis such as just displaying average pace over a couple months.

Nutrition: Very common thing to track, but could be a bit complicated for a project like this due to the numerous variables to track and specialised knowledge needed to inform/analyse on this topic Factors/variables to use:

Simplest analysis here would be to check different food group intake amounts against recommended amounts for adults.

How do we want to analyse multiple datasets:

Sports Performance:

Sleep:

Nutrition:


5th May 2022 - Meeting with Terra

Completed:

To-Do:

Trello: Plan all tasks and setup who does what

Frontend:

Backend:

Additional stuff (Optional):

Things to do (for the following week):


10th May 2022 - Meeting with Terra

Discussion with Terra:

Framework design:

Database:

UI:

Backend:

User Profile:

Plan for next week:


18th May 2022 - Meeting with Terra

Frontend:

Backend:

Database:


23th May 2022 - Internal Meeting

To do:

Command bar:

Others:


27th May 2022 - Meeting with Terra

Things to do:

Habit Dash:

Frontend:

Backend:

Uni stuff:

Notes specific to team:


31th May 2022 - Meeting with Terra

To do:

Deliverables:


7th June 2022 - Meeting with Terra

Backend:

Frontend: