Smart SleeveProject file 10 of 10
back to library
10Smart Sleeve

Mobile · telemetry · clinician workflow

Role
Project Lead · five-contributor software effort
Public team projectOpen organization repository

Educational competition prototype

The app did not wait
for the sleeve.

As project lead, I kept a five-contributor software effort moving across BLE, DSP, mobile, offline state, cloud sync, and clinician review.

  1. Abstract
  2. Stream
  3. Process
  4. Persist
  5. Review
  6. Lead
Patient mobile product
Smart Sleeve public patient mobile dashboard
Patient mobile product · synthetic or public-safe evidenceOpen organization repository
Swipe through the evidence01 / 06
  1. A real/mock sleeve connector kept software development independent of scarce physical hardware.

    REALESP32 BLE
    MOCKSeeded generator
    CONTRACTSame consumer API
    Physical validation pending
  2. Eight-channel EMG/IMU packets are parsed and buffered without coupling transport to UI.

    PACKETESP32 bytes
    PARSEChannel samples
    FIFOTyped frame buffer
    Prototype telemetry
  3. Filters, calibration, normalization, and feature extraction turn noisy telemetry into display state.

    RAW8 channels
    FILTERNotch + bandpass
    CALIBRATEWarmup + baseline
    ANALYTICSDisplay state
    No clinical accuracy claim
  4. Redux and SQLite preserve patient sessions locally, then Firebase syncs when connectivity returns.

    UIImmediate state
    SQLITEDurable session
    SYNCRetry boundary
    FIREBASEShared record
    Prototype sync scale
  5. The clinician portal reuses patient and session records in directory, detail, goals, and telemetry views.

    DIRECTORYFind a patient
    DETAILHistory + goals
    SESSIONTelemetry summary
    Educational demo data
  6. Five public contributors converged mobile, DSP, hardware, portal, data, tests, and CI on one demo system.

    MOBILEPatient workflow
    DSP + BLETelemetry system
    WEB + DATAPortal + sync
    MAINIntegrated demo
    Team-delivered prototype
System viewOne connector kept the product moving with or without hardwareThe physical sleeve and programmable mock share the same consumer contract; this proves testability, not physical-device validation.
Replaceable sourcesHardware boundaryHardware-independent productsame contract
real pathESP32 sleeveBLE packet stream
test pathSeeded mockrepeatable telemetry
shared contractISleeveConnectorconnect · stream · disconnect
productPatient apppair · exercise · review
public sourceIntegration testsscripted device states
leverageParallel deliveryUI and telemetry evolve together