Recommended Decision Order
- If you are evaluating the SDK or starting a new app, use
create-elata-demofirst. - If you already have an app and know which capability you need, add the published package for that capability.
- Only drop to repo-internal workflows if you are actively modifying the SDK inside the monorepo.
New Project Or Evaluation
create-elata-demo
The best starting point when you want a working app quickly.
EEG In A Browser App
Use@elata-biosciences/eeg-web when you need:
- browser-side EEG WASM APIs
- signal processing and model functions
- shared types used by browser integrations
EEG Web SDK
Signal processing, band powers, and analysis models
Browser BLE For Muse-Compatible Devices
Use@elata-biosciences/eeg-web-ble when you need:
- browser BLE discovery and streaming
- normalized headband frames
- a transport layer for Muse-compatible EEG devices
@elata-biosciences/eeg-web alongside it.
EEG BLE Web SDK
Connect to headband devices over Web Bluetooth
Camera-Based rPPG
Use@elata-biosciences/rppg-web when you need:
- browser-side rPPG processing
- packaged WASM backend loading
- demo helpers for camera-driven prototypes
Camera Web SDK
Heart rate from camera via face detection
Local Repo Development
Use./run.sh sync-to only if you are modifying packages/eeg-web inside the monorepo and want to link the local package into another app.
Do not use sync-to as the normal onboarding path for new SDK consumers.
Paths To Avoid
- Avoid starting from
./run.sh sync-tofor new apps. It is a localeeg-webdevelopment helper, not a general setup flow. - Avoid treating in-repo dev demos as the normal install path. They are useful references, but
create-elata-demois the cleaner consumer starting point. - Avoid assuming a scaffolded app is broken if
pnpm installbehaves strangely inside another workspace. Check thepnpm --ignore-workspaceworkflow first.
Next
Quickstart
Scaffold your first app
Example Apps
Full reference implementations
Compatibility
Browser, device, and tooling support