@founderhq/journeys-bridge
v0.3.0
Published
Versioned native bridge protocol for FounderHQ Journeys
Readme
@founderhq/journeys-bridge
Versioned message types, serializers, parsers, and safe JavaScript dispatch helpers shared by the FounderHQ Journey renderer and native SDK hosts.
Most app developers should install a platform SDK instead of using this package directly:
@founderhq/journeys-react-nativefor Expo and React NativeFounderHQJourneysfor Swift/iOSfounderhq-journeysorfounderhq-journeys-composefor Android
Hosts must ignore unknown fields and reject unknown protocol versions. Never place a FounderHQ API key in a renderer URL.
The protocol covers bridge readiness, first paint, navigation state, native haptics, typed events, capture, discounts, links, errors, and commands so every platform SDK can expose the same Journey behavior as web.
Version 0.2 adds optional ready.payload.capabilities entries prepare and
visibility without changing wire protocol version 1. A capable host initializes
with presentationMode: "prepared", waits for rendered, then sends
{ name: "set_visibility", visible: true }. Reuse the same renderer. Hosts
without both capabilities retain direct presentation.
initialize also accepts revisionId and a distinct clientSessionId for each
presentation. Capture bodies preserve their own original identifiers; hosts must
forward them unchanged. A failed capture_response may include retryAfterMs
so the renderer retains queued events and respects the server's backoff.
Release notes
0.3.0
- Released with the 0.8.0 Journeys SDKs. Their API and renderer default to
https://app.getfounderhq.com; the analytics ingest host is reserved for Events.
