@robono/messaging-react-native 0.6.0 → 0.7.0

package/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 0.7.0 — unreleased
+
+Supply automatic Expo calling, Maps and connected chat extras. Use Messenger attachment menus, grouped media, bounded dialogs and anchored inbox actions. Connect managed call alerts, unanswered-call messages and call-aware media audio. Stop location and pending uploads during account cleanup.
+
 ## 0.6.0 — release candidate
 
 Clear local chat immediately when the complete Expo connection signs out, before waiting for notification cleanup. Supports the account lifecycle templates generated by server 0.20.

package/README.md

@@ -2,6 +2,48 @@
 
 Use a ready-made direct or group conversation screen, replace its sections, or compose the exported components into your own layout. Use `ExpoMessenger` for the complete inbox and conversation flow, or the individual components inside your existing navigation. The complete Expo messenger connects notification registration; nothing requests permission on mount. The shared icon controls require `react-native-svg` (install it with your framework’s native dependency installer).
 
+## Connected features
+
+The complete messenger connects selected calling, chat weather/tracking and Maps
+through the same authenticated server route. Customers do not supply fake demo
+callbacks or create separate call controllers for this setup. Feature selection
+and appearance remain in **Features & preview**. Advanced custom interfaces can
+still use individual components and callbacks.
+
+Synchronize permitted contacts once on your server:
+
+```ts
+await messenger.synchronizeContact({
+  externalUserIds: [firstUserId, secondUserId],
+  allowed: currentPermission,
+  revision: savedPermissionRevision,
+});
+```
+
+This atomically updates texting and calling permission. It does not buy a service,
+start a call or start location tracking. Use a saved, increasing revision from your
+own database; retries with the same values are safe. Keep group membership in the
+messaging group API; eligible groups use that same membership for calls. Supergroups
+never start calls, and voice/video calls remain limited to eight people.
+
+The host's `authorize` function checks `calling.*`, `extras.*` and `location.*` as
+well as messaging operations. Account checks have no conversation ID; call actions
+use the actual conversation from the service, never a caller-supplied claim. Keep
+current membership, suspension and feature restrictions in those checks.
+
+Incoming calls use the same configured notification providers as messages. The
+supplied client registers its call handler automatically. Native apps need their
+own Apple APNs key/bundle ID and Google Firebase service account; upload them only
+to Robono's private notification setup. A website needs its HTTPS origin and chat
+path, not Apple/Google keys. Users still choose whether to allow notifications.
+These are ordinary app/browser alerts: the OS can delay or suppress them, and an
+alert never answers a call or turns on a microphone automatically.
+
+Await the returned `signOut()` before ending your own login session. It stops
+capture and calls, cancels unfinished tracking and unregisters the device. Old
+account credentials and unfinished work must never be reused for another person.
+
+
 ## Recommended installation
 
 Connect `createRobonoMessengerServer` from `@robono/server` at one authenticated
@@ -140,6 +182,8 @@ The bundled adapter uses your private storage endpoint, described below. You can
 
 ## Private media endpoint
 
+The complete `createRobonoMessengerServer` route already supplies managed private uploads, downloads, metadata verification and configured screening. No separate storage implementation is needed. Only follow this section when deliberately using your own storage.
+
 Mount `createMessagingMediaBackendAdapter` from `@robono/server` behind your existing session authentication. Supply the same `RobonoMessagingBackend` as your messaging endpoint, your authorization checks, and a `MessagingPrivateStorage` implementation for your storage provider. The adapter checks current conversation access and policy before asking storage for a transfer. Phone requests never contain Robono API keys or storage credentials.
 
 The storage implementation has four operations:
@@ -151,12 +195,12 @@ The storage implementation has four operations:
 
 The HTTP protocol uses POST with `{operation, ...}`. `prepare` takes `uploadId`, `conversationId`, `kind`, and `file` metadata; it returns `{url, headers?}` or `{media}` for an already verified upload. `complete` takes `uploadId` and `conversationId`, returning `{media}`. `download` takes `conversationId` and `messageId`, returning `{url, headers?, media}`. `discard` takes `uploadId`, returning `{ok:true}`. Errors use `{error:{code,message}}` and an appropriate HTTP status.
 
-Also supply `resolveMedia` to `createMessagingBackendAdapter`, resolving the authenticated actor, conversation and asset ID to your verified stored metadata. This replaces untrusted phone claims before sending. Keep asset IDs opaque and unique per message. Check blocks/permissions in both endpoints. Restrict signed uploads to the prepared object and size where supported; delete rejected objects. Expire abandoned uploads and private cache files through your storage lifecycle. Your app owns storage and any malware/content checks appropriate to its policy; the SDK does not upload files to public storage or scan private conversations.
+Also supply `resolveMedia` to `createMessagingBackendAdapter`, resolving the authenticated actor, conversation and asset ID to your verified stored metadata. This replaces untrusted phone claims before sending. Keep asset IDs opaque and unique per message. Check blocks/permissions in both endpoints. Restrict signed uploads to the prepared object and size where supported; delete rejected objects. Expire abandoned uploads and private cache files through your storage lifecycle. With custom storage, your app owns storage retention and any malware/content checks; configure these separately from Robono’s managed screening. Files must remain private.
 
 Handle signed `messaging.message_removed` events to revoke and delete assets when history expires. Account deletion must also erase associated storage. A terminated app cannot run cache cleanup; the adapter's temporary files live under the OS cache directory, which can be purged by the OS. Do not treat device cache eviction as a fixed retention guarantee.
 
 
-### Design messaging and calling together
+### Custom composition: messaging and calling
 
 The website Experience builder renders these messaging components and the optional calling components, with a local conversation transport. Saving a draft creates an immutable design version without changing active settings. Review and apply updates messaging and calling atomically, with revision checks against the existing editors. Use your existing settings/appearance fetches to receive the applied design. Service access and per-contact eligibility still apply.
 
@@ -177,7 +221,7 @@ The `/calling` entry additionally needs the optional `@robono/calling-react-nati
 
 The website preview renders the same bubbles, inline voice controls, full-screen photo/file viewer and video transport controls through React Native Web. Phone/tablet and portrait/landscape choices resize the real layout viewport without reloading the conversation. Browser media elements and Expo players drive the shared controls; the browser preview does not substitute native browser player controls or a generic dialog. Camera/library/file selection and OS permission prompts still follow the platform. Preview interactions never contact real users or send billable events.
 
-The standard chat uses compact grouped bubbles, timestamps at the lower right, inline voice controls and an expandable attachment tray below the composer. Attach dismisses the keyboard; tap it again to return to typing. Android Back closes the tray first. The microphone remains available beside the text field, including while text is typed; Send is enabled when there is text or a finished voice recording. Camera remains available when capture is enabled, including with typed text or a reviewed voice recording. Captures join the existing pending attachments. New designs start with a light chat palette; existing saved colors remain unchanged. The builder’s “Use classic chat colors” action applies the default palette to the draft without changing enabled features.
+The standard chat uses compact grouped bubbles, a curved delivery indicator, swipe-to-reveal time, inline voice controls and Messenger’s attachment menu. Attach dismisses the keyboard; tap it again to return to typing. Android Back closes the tray first. The microphone remains available beside the text field, including while text is typed; Send is enabled when there is text or a finished voice recording. Camera remains available when capture is enabled, including with typed text or a reviewed voice recording. Captures join the existing pending attachments. New designs start with a light chat palette; existing saved colors remain unchanged. The builder’s “Use classic chat colors” action applies the default palette to the draft without changing enabled features.
 
 Voice-only conversations use Robono Messenger’s compact composer: the duration-limit placeholder, embedded microphone and adjacent Send control. The Expo adapter records and reviews audio inline, with elapsed time, microphone metering, playback and removal before sending. The builder uses the same controls with a local browser microphone recording; no audio is uploaded from the preview. When texting is enabled, tap the microphone to record in the composer and tap it again to stop. Each completed recording becomes a separate playable attachment in the shared horizontal row, and the microphone is available for another recording. Typed text is preserved; Send puts accompanying text on the last attachment as its caption. Custom media adapters can use `components.VoiceComposer`, `VoiceMessageComposer` and `VoiceDraftPlayback`; `renderTextComposer` restores the text controls alongside the reviewed recording.
 
@@ -196,7 +240,7 @@ Enable reactions and polls in Experience builder. The screen includes the long-p
 
 ## Optional message after no answer
 
-Use `ExpoMessagingCallingScreen` from `@robono/messaging-react-native/expo-calling` for the supplied native media tools together with calling. It accepts the same `storage` and `audioSession` as `ExpoMessagingScreen`. For your own media adapter, use `MessagingCallingScreen` from the `/calling` entry to combine the optional call button and message composer. Connect the calling controller's `onUnansweredCall` callback to your existing conversation navigation, then pass `unansweredCallId` and `onDismissCallMessage`. The callback only runs for an outgoing call made in the current controller session that ended without an answer; opening old missed-call history does not trigger it.
+The complete `createExpoMessenger` flow connects unanswered-call messages automatically. For custom composition, use `ExpoMessagingCallingScreen` from `@robono/messaging-react-native/expo-calling` for the supplied native media tools together with calling. It accepts the same `storage` and `audioSession` as `ExpoMessagingScreen`. For your own media adapter, use `MessagingCallingScreen` from the `/calling` entry to combine the optional call button and message composer. Connect the calling controller's `onUnansweredCall` callback to your existing conversation navigation, then pass `unansweredCallId` and `onDismissCallMessage`. The callback only runs for an outgoing call made in the current controller session that ended without an answer; opening old missed-call history does not trigger it.
 
 `UnansweredCallMessage` is also exported separately for a custom composer. Place it inside `MessagingProvider` and supply your existing `pickAttachment` adapter. The adapter must support recording, review and private upload. Eligibility comes from your authenticated backend, and sending rechecks permissions. Recording is optional and starts only when the caller chooses it. An ordinary message is left in the chat, with normal history, retry and media rules.
 
@@ -206,7 +250,7 @@ The conversation header’s three-dot menu includes Search this chat, plus Block
 
 Blocking retains history and stops direct messages and calls for that pair in your app. Shared group messages remain visible. Reporting is separate: it shares the selected message, or up to five recent incoming messages, and the reason with your app’s moderators. It confirms success only after storage acknowledges the report. The SDK reuses the request ID on retry. Owners and administrators review reports in the Messaging workspace; private media is reviewed through your app’s authorized storage tools.
 
-Enable Reactions to show an emoji ribbon beside the long-pressed bubble, or the hover smile icon on desktop. Selected reactions stay attached below the message. Polls are interactive chat messages created from the attachment menu. Transcript is a separate voice-message action. In the header's three-dot menu, choose translation **Off / Text / Voice** and languages once for the conversation. The saved choice controls Translate or Play Translation on eligible incoming messages; own messages and matching sender/target languages do not show it. The result has Show original / Show translation controls. Expo supplies translated-voice playback and its audio session; an explicit Play Translation action starts playback when ready. `language` supplies the initial target and `contact.language` / `participants[id].language` supply known sender languages, with a saved conversation incoming-language fallback. Defaults to Off. The Expo private outbox retains preferences across restarts on this device. Custom contact menus can call `client.setTranslationPreference({mode:'text',language:'es',sourceLanguage:'en'})`. Connect `MessagingClient.transformRequest` to the authenticated `createMessagingTransformBackendAdapter` on your server.
+Enable Reactions to show an emoji ribbon beside the long-pressed bubble, or the hover smile icon on desktop. Selected reactions stay above the delivery indicator. Polls are interactive chat messages created from the attachment menu. Transcript is a separate voice-message action. In the header's three-dot menu, choose translation **Off / Text / Voice** and languages once for the conversation. The saved choice controls Translate or Play Translation on eligible incoming messages; own messages and matching sender/target languages do not show it. The result has Show original / Show translation controls. Expo supplies translated-voice playback and its audio session; an explicit Play Translation action starts playback when ready. `language` supplies the initial target and `contact.language` / `participants[id].language` supply known sender languages, with a saved conversation incoming-language fallback. Defaults to Off. The Expo private outbox retains preferences across restarts on this device. Custom contact menus can call `client.setTranslationPreference({mode:'text',language:'es',sourceLanguage:'en'})`. Connect `MessagingClient.transformRequest` to the authenticated `createMessagingTransformBackendAdapter` on your server.
 
 ### November 1 behavior update (unpublished)
 
@@ -337,3 +381,15 @@ app does not prevent server delivery afterward. The selected time is approximate
 to the minute. Current access, screening and spending rules still apply at send
 time. In-app voice recording and poll creation retain their existing immediate-send
 flows; custom composers can schedule their finalized content through the same API.
+
+### Screen sharing in the complete messenger
+
+The installer configures `@robono/calling-react-native` with `video:true` and
+`screenSharing:true`. On iPhone, your Apple Developer team must sign both the app
+and generated `RobonoScreenBroadcast` extension with the App Group
+`group.<your bundle ID>.calling` (or your explicit plugin override). Xcode/EAS can
+register these using your Apple account. Android asks for screen-capture permission
+when the person starts sharing. Rebuild both apps after native configuration changes.
+The server's selected feature and current contact permissions still control access.
+An existing explicit `screenSharing:false` is preserved by upgrades; enable it and
+rebuild before offering screen sharing in that app.