Open MoralCode opened 2 years ago
This should also probably include all the data for every split/interval in one shot.
Current thoughts:
create some kind of central "data feed manager" that centrally manages the different characteristics available and reconciles that with the data the user requests such as to only have the minimum number of notifications possible while maximizing available bandwidth (so using the multiplexed characteristic all the time probably wont be a good idea)
its likely that this feed manager would need to create its own Flutter streams so that it has the ability to swap from one source feed (a dedicated chatacteristic for one or more pieces of data) to the multiplexed feed without the application on the other side being aware (they just keep getting the same objects)
Currently WorkoutSummary data is implemented as an object full of futures, which is a bit hacky and a little messy to look at in the code.
Ideally It would be nice to have a data structure that can:
Specifically for WorkoutSummaries:
Workout
object used to start the workout or be used to construct aWorkout
if one is not presentideally this should also be something thats able to extend to the other types of data (which are also spread across multiple characteristics)