ShuffleDB presents:CapDat
CAPTURE. MIX. HAND OFF.
UNLINKED DEVELOPMENT WORKBOARD · ANDROID MVP

CapDat Sandbox

A living plan for the native capture application that starts the ShuffleDB creator pipeline with better media, audio control, and source lineage.

APPLICATION SURFACENative Android—not web capture

The web route explains CapDat and tracks development. Camera, microphone, phone media, and export remain device-native.

WORKING FOUNDATIONCapture, mix, color, save

The supplied project contains real CameraX, Media3, microphone, media-library, and lineage code.

CURRENT DELIVERY GAPExport the relationship

TrackDat manifests exist privately, but a reliable user-facing media-plus-manifest handoff has not been completed.

CURRENT IMPLEMENTATION

What exists versus what comes next

Status is based on the supplied Android source. “Done” means code exists in the MVP; it does not imply public distribution or broad device validation.

01
done

Native capture foundation

CameraX FHD recording, camera flip, countdown, guide playback, microphone capture, audio routing, color preview/export, and Movies/CapDat saving exist in the supplied Android MVP.

02
done

Debug install target verified

The supplied source package contains an intact 18.27 MB CapDat 0.1.0 debug APK for Android API 31+. It is suitable for development-device installation; signed public distribution remains a separate release gate.

03
done

Local media library

Phone, Recent, and Captures surfaces browse, preview, reuse, remove, and Android-authorized delete media.

04
done

Source lineage model

SoundCloud/source-screen-capture metadata and durable CapDat capture IDs can be linked to a dance recording and written as a TrackDat JSON manifest.

05
active

TrackDat handoff surface

TrackDatTesting can receive the paired video and JSON, preserve CapDat identity/artwork, and protect creator corrections. Android export/share remains pending because manifests currently stay in private app storage.

06
active

Production authentication

The temporary SoundCloud token flow must be replaced by Authorization Code + PKCE before distribution.

07
queued

EditDat and PostDat context

CapDat should preserve enough source, audio, capture, and consent metadata for later EditDat and PostDat use without coupling the Android recorder directly to publishing.

IMPLEMENTATION ROADMAP

Eight coordinated upgrades

CapDat stays focused on trustworthy capture and handoff. Editing and publishing remain downstream responsibilities.

01
Distribution

Safe Android distribution

Highest

Turn the working device-build project into an installable, versioned product without weakening Android permissions or user control.

  • Signed release builds
  • Versioned APK or Play track
  • Release notes
  • Device compatibility matrix
  • Crash reporting policy
NEXT ACTION

Choose the private/public distribution route, establish signing custody, remove generated build state from the source package, and produce a reproducible release build.

02
Identity

Production SoundCloud authorization

Highest

Replace the temporary pasted-token development path before any broader distribution.

  • Authorization Code + PKCE
  • Redirect handling
  • Token refresh
  • Revocation
  • No embedded secrets
NEXT ACTION

Register the SoundCloud client, define the Android redirect URI, and implement PKCE in the isolated session layer.

03
Receiver live · Android share pending

CapDat → TrackDat transfer

Highest

Expose the existing private TrackDat manifest and its paired media through a deliberate, recoverable handoff.

  • ✓ TrackDat accepts a paired CapDat video and JSON handoff
  • ✓ Stable capture ID and protected music metadata map into TrackDat audioIdentity
  • ✓ Manual → CapDat → embedded → recognition precedence is contract-tested
  • Share/export action in Android
  • Transfer confirmation
NEXT ACTION

Add the Android share/export surface for the paired media and manifest, then validate the real writer output against TrackDatTesting on-device.

04
Capture

App-playback source engine

High

Complete the existing PlaybackCaptureEngine extension without pretending Android can bypass user consent or platform restrictions.

  • Supported playback capture
  • Explicit consent
  • Captured source model
  • AudioMixPlanner integration
  • Device fallback
NEXT ACTION

Prototype MediaProjection playback capture on supported devices and keep the existing user-controlled screen-recording workflow as fallback.

05
Reliability

Capture and export recovery

High

Protect long recording sessions from process death, export interruption, storage pressure, and partial media writes.

  • Session journal
  • Interrupted-export recovery
  • Storage preflight
  • Temp-file cleanup
  • Actionable failures
NEXT ACTION

Persist recording/export phase state and build recovery tests around forced termination and low-storage conditions.

06
Media

Audio and sync verification

High

Measure the result of guide-track, mic, offset, routing, and Transformer composition across real devices.

  • Sync test fixture
  • Bluetooth-route matrix
  • Clipping detection
  • Latency evidence
  • Export parity
NEXT ACTION

Create deterministic clap/beat fixtures and measure captured versus exported alignment on the Galaxy S25 Ultra and at least one lower-tier device.

07
Library

Lineage-aware capture library

Medium

Make source relationships visible and repairable instead of leaving them only in internal records.

  • Source badges
  • Linked capture detail
  • Missing-source warning
  • Relink workflow
  • Manifest export status
NEXT ACTION

Show the capture ID, source recording, track title, artist, and TrackDat handoff state in the Captures tab.

08
Privacy

Permission and retention contract

Highest

Explain what stays on the phone, what may be shared, and what downstream products receive.

  • Permission rationale
  • Local retention controls
  • Explicit upload/share
  • Metadata preview
  • Deletion semantics
NEXT ACTION

Document each Android permission in-product and require a review screen before CapDat media or manifests leave the device.

CAPDAT CONTRACT

Capture without losing provenance

  • Recording and screen capture remain explicitly user-controlled.
  • Original phone media is never silently deleted or uploaded.
  • Guide-track and microphone choices remain visible and reversible before recording.
  • Source metadata is protected lineage, not disposable caption text.
  • TrackDat receives a versioned handoff instead of guessing relationships from filenames.
  • EditDat and PostDat remain downstream tools rather than being embedded into capture.