Apps & libs
This page lists official libraries, as well as example code for you to develop your own Pryv.io apps.
Web & Node.js
Section titled “Web & Node.js”JavaScript library
Section titled “JavaScript library”➔ npm, GitHub (monorepo including add-ons)
Optional add-ons:
- JS lib Socket.IO add-on ➔ npm
- JS lib Monitor add-on ➔ npm
- JS lib CMC (Cross-account Messaging & Consent) add-on ➔ npm — client-side helpers (slug builders, lifecycle wrappers, errorIds catalogue) for the CMC plugin shipped in Open Pryv.io v2. See the CMC guide.
Example web apps
Section titled “Example web apps”➔ GitHub
Implementing use cases such as:
- Collecting form data
- Viewing collected data and sharing it
- Collecting and consuming high-frequency data
Auth web app
Section titled “Auth web app”➔ GitHub
Handling registration, auth requests, password reset and email change
Multi-Factor Authentication app
Section titled “Multi-Factor Authentication app”➔ GitHub
Handles the MFA flow.
Swift library
Section titled “Swift library”➔ GitHub
Swift example app
Section titled “Swift example app”➔ GitHub
HealthKit integration (PoC)
Section titled “HealthKit integration (PoC)”➔ GitHub
Library
Section titled “Library”➔ GitHub
Java app examples
Section titled “Java app examples”➔ GitHub
Android app example
Section titled “Android app example”➔ GitHub
React-native example app
Section titled “React-native example app”➔ GitHub
Based on the JavaScript library.
Subject account backup — CLI + library + sample web app
Section titled “Subject account backup — CLI + library + sample web app”➔ CLI + library: pryv-account-backup ➔ Sample web app: pryv-account-backup-webapp
A subject-facing tool for downloading every read-side resource of a Pryv account (account / streams / accesses + history / profile / audit log / events / attachments / HFS series / webhooks) as a portable JSON + binary disclosure bundle. Two flavors share the same library code:
- The CLI (
npm start) is the canonical flavor; produces a folder of JSON + binary files plus a per-file sha256 integrity manifest for third-party auditors. - The sample web app is operator-hosted so non-technical subjects can self-serve via a “Start backup” button; produces the same coverage as the CLI minus the auditor-facing manifest, emitted as a series of subject-portable ZIP files.
Subjects also get a portable sync-state.json they keep alongside the backup; re-supplying it on the next visit drives cross-session incremental, so subsequent runs only fetch what’s changed.
The previous-generation pryv/example-service-bluebutton is archived; new deployments use the pair above.