Getting started

Environment & study setup

Check the participant device and the configuration packaged for your study.

Reviewed
On this page

Runtime requirements

The current app targets Android 11 or later (minSdk 30), with compileSdk and targetSdk set to 36. Use the study-specific app supplied by your research team. A shared public app-store download URL was not established from this repository.

Reading Samsung Health records requires Samsung Health on the phone and records to read. For studies using Health Connect, check both data sharing by the source app and DTRAC's read permissions.

Starting a study

  1. Confirm the app name, version, and participant device match the study configuration.
  2. Complete the enrollment flow used by the study. studyId and participantId identify the owner of data and remote uploads.
  3. Check permissions and background operation.
  4. Submit one survey and verify that the required sensor and health records are stored.
  5. If server storage is enabled, verify that a local record reaches the server.

The current ui/index.json starts at home. Screens and enrollment can vary by study. Screenshots from the presentation are examples, not a universal default interface.

Configuration inputs

ConfigurationAndroid asset locationPurpose
Plugins and collection itemsmanifests/plugins/registry.jsonEnabled state, types, source priority, allowlist
Questions and survey timingSurvey module's survey.jsonQuestions, choices, response window, audio policy
Screensui/index.json, ui/screens/*.jsonEntry screen, screen inventory, UI nodes
Notificationsmanifests/notifications/config.jsonChannels and schedules
Study runtimestudy_config.jsonStudy identity, duration, availability and anchor policies
Backend selectionmanifests/services/backend.jsonFirebase/Supabase and local-only/server storage

Locations refer to assets inside the APK. Some files are injected when a study app is built; the installed configuration may differ from repository defaults.

Baseline collection

The baseline registry allows sensor and samsung_health. Ordinary Samsung Health pulls are limited to exercise, sleep, and heart rate. health_connect is disabled and absent from the allowlist. Read the runtime filtering described in plugin extensions before treating a configuration declaration as an active feature.

Documentation evidence

Working-tree baseline · source paths · HEAD 8213e6b7

  • app/build.gradle.kts
  • app/src/main/assets/manifests/plugins/registry.json
  • app/src/main/assets/ui/index.json
  • app/src/main/java/com/hdil/datacollection/StudyConfig.kt
  • app/src/main/java/com/hdil/datacollection/config/BackendConfigLoader.kt
  • app/src/main/java/com/hdil/datacollection/MainActivity.kt
DTRAC AndroidYonsei University · Bongshin Lee’s research team