Requirements

Functional Requirements:

• Log workouts
• View history & basic stats.
• Sync across devices.

Non-Functional Requirements:

• relaiability
• offline data storage
• low latency

API Design

There would be 4 api :

1. to write data to server
2. to read data from server
3. to delete all data from server
4. to add a new client
5. to delete a new client

add_user(userdetails={name:,age:,weight:,height: },email=,deviceid=) etc

delete_user(email=,usertoken=). usertoken would be created when user is added

write_data(usertoken, deviceid,userdata={json for all type of data})

read_data(usertoken,deviceid). -- so that data can be formated based on device type!

delete_all(usertoken)

High-Level Design

we will have a client app, gathering al the data from the customer

we will setup a local datastore at client location -- so that it can save data even if the client is offline

Then we will have a server whoes role is retrieve data and share back to client

This system is both high write and high read together.

Detailed Component Design

cilent datastorage - for keeping offline data, also latter to commit to server

server datastorage -

1. s3 for raw data storage from different sesiosn
2. SQL based for userprofile storage

authentication server -- probably oauth openidc based, with refresh token only when the client is first connected to the server. then using refresh token client can keep updating the server