DTRAC ANDROID

About DTRAC

An Android foundation for collecting the everyday data your study needs.

Reviewed

RESEARCH APPLICATIONS

Inside the research apps.

Explore participant experiences configured for each study.

INSPIRE

A survey for recording everyday emotions and behavior.

Explore the study
A slider survey in the INSPIRE research app

ReBloomLens

A home screen for exercise, sleep, and daily routines.

Explore the study
Exercise, sleep, and routines on the ReBloomLens research home screen

Study-specific screens from the MD4BD September 17, 2026 presentation. They may differ from the current default app.

On this page

DTRAC is an Android system for research data collection. It brings together smartphone sensors, health records, and participant responses. Each study can configure its collection items, questions, and schedules, with local storage and server synchronization.

What can you collect?

Participant activitiesSmartphone sensorsHealth records
Surveys and EMA, voice responses, cognitive gamesMotion, location, screen and battery, network and call stateSleep, exercise, heart rate and other records held by a provider

Participant activities and device records can be used together. Available data depends on the study configuration, permissions, device, and records in the source app.

How does data flow?

Participant responses, sensors and health records flow into Room and optionally synchronize with a research server

Plugins connect data sources. The storage and read layers use Room as their local source of truth. Studies with server storage synchronize through the existing Firebase or Supabase data sources. Audio files have a separate storage policy from response metadata.

Reading implementation status

  • Enabled by default: Selected in the baseline configuration. This does not guarantee that every device produces records.
  • Implemented: A read, mapping, or storage path exists, but may not be part of default collection.
  • Planned: Additional implementation or external host-app validation is required.
  • Needs verification: Current evidence does not establish device support or runtime behavior.

Documentation baseline

This documentation reflects the September 17, 2026 working tree and the MD4BD meeting presentation. Research examples and future SDK plans are distinguished from the current Android runtime. Configuration examples use fictional identifiers and contain no real participant data.

Documentation evidence

Working-tree baseline · source paths · HEAD 8213e6b7

  • app/src/main/java/com/hdil/datacollection/M9App.kt
  • app/src/main/assets/manifests/plugins/registry.json
  • core/plugin-api/src/main/java/com/hdil/datacollection/plugin_api/Plugin.kt