mbernasocchi
commented
10 years ago From Tapio Mattila: Calendar view supports understanding when user has been moving. Answers quite well to questions when and how often. Tabular format (table view) supports understanding better the data part of each training. User could see with one glimpse a bunch of training specific data. So both views could be valuable. In table I would personally like the possibility to select (filter) what columns are visible. This of course means that there should be quite many columns (data items) to select from. One move contains more general header part and data a list of data points. From these it would be nice to have for example following kind of list:
- date, time, training type,
- training effect, recovery time, burned calories (motivating for elderly people :-) )
- duration, length
- avg_speed, avg_hr, avg_xxx
- has this event been downloaded to any service (movescount, endomondo, ...) One, perhaps far fetched, idea to this 'logbook' concept would be a possibility to import designed trainings. Use case is that a coach could define training programs that trainees then import to their personal calendar and tries to do those. Undone trainings marked somehow differently of course to done items. If this would be reality then we are not far from synching some club's own training calendar...
jonathanbell
Ideas are welcome! Should we use a calendar? A list with more information (like duration, distance, etc)?