Skip to Content
FeaturesActivity Metrics

Activity Metrics

Status: Current implemented behavior. Audience: Users and contributors. Implementation: features/activity, data/repository/ActivityRepository.kt. Navigation: Screen.Metric; widgets STEPS, DISTANCE, CALORIES_OUT, ACTIVE_CALORIES, FLOORS, ELEVATION, WHEELCHAIR_PUSHES. Related: Feature map, Statistics, Recording of activity.

The activity feature owns period-based detail screens for movement metrics and workout sessions. It is separate from activity recording: recording and manual activity entry create records, while these screens read and explain existing Health Connect data.

Implemented Metrics

Activity metric detail screens currently cover:

  • Steps.
  • Distance.
  • Calories burned.
  • Active calories.
  • Floors.
  • Elevation.
  • Wheelchair pushes.

The workout/session area also covers activity lists, activity detail, route preview/export, heart-rate charts for workouts, activity summaries, and cardio-load context.

Detail Pattern

Activity metric screens follow the shared period-detail model:

  • Day, week, month, and year ranges.
  • Selected anchor date.
  • Previous/next period navigation.
  • Calendar selection.
  • Pull to refresh.
  • Period charts and selected-day entry views where available.
  • Statistics, comparisons, baselines, confidence, and source context.
  • Reorderable metric detail sections.

The movement metrics share one metric screen configured per metric, which carries each metric’s title, accent, required Health Connect permission, and value extraction. Calories, active calories and BMR render the calories aggregate instead.

Screen state lives in an activity ViewModel loading through ActivityRepository. Period selection is not owned by the view model — the shared metric-detail scaffold owns it and hands a selection down. New activity metric work should keep metric-specific charts and rows in features/activity and use the shared scaffold instead of adding a new screen shell.