@robono/messaging-react-native 0.9.0 → 0.11.0

package/CHANGELOG.md

@@ -1,3 +1,11 @@
+## 0.10.0 — release candidate
+
+## 0.11.0
+
+Connects the supplied Messenger to recording/caption controls, on-device background blur and account device checks, using its existing call integration.
+
+Add supplied business cards, public groups and moderation, appearance controls, app-wide availability and inbox continuity. Own conversation opening and foreground incoming updates inside ExpoMessenger. Expand supplied interface languages.
+
 ## 0.9.0 — release candidate
 
 Supply hosted connections, durable offline actions, interface language, localized Maps/calls, and retryable native upload errors. Use native calling 0.7 and Maps 0.3 with an app rebuild.

package/README.md

@@ -1,5 +1,42 @@
 # Optional Robono messaging screens
 
+## Small interface customizations
+
+Choose fonts, text size, message spacing and bubble shape in **Features & preview →
+Appearance**. Saved `appearance.presentation` settings reach the supplied phone
+UI and web preview. Platform fonts differ; device accessibility scaling is retained.
+See the [customization guide](https://robono.com/guides/messenger-customization.html).
+
+The supplied screen accepts `components.MessageBody`, `components.MessageFooter`
+and `components.HeaderActions` in addition to whole-screen replacements. These
+small regions let you add customer actions without recreating the player,
+composer or message gestures. They use the same contract on web and phones.
+
+```tsx
+import {View, Pressable, Text} from 'react-native';
+import type {MessagingCustomization} from '@robono/messaging-react-native';
+const components: MessagingCustomization = {
+  MessageBody: ({children}) => <View>{children}</View>,
+  HeaderActions: ({contact}) => (
+    <Pressable accessibilityRole="button" accessibilityLabel="Profile"
+      onPress={() => openCustomerProfile(contact)}
+      style={{minWidth:44,minHeight:44,justifyContent:'center'}}>
+      <Text>Profile</Text>
+    </Pressable>
+  ),
+};
+// Pass components to ExpoMessenger/ExpoMessagingScreen.
+// Merge with existing components (such as a supplied TrackingMap), if present.
+```
+
+Define these components outside render. `MessageBody` receives the supplied body
+as `children`; preserve it to retain the standard text, media, poll and translation
+behavior. `MessageFooter` adds an optional region inside the bubble. Both receive
+`message`, `mine`, `appearance` and optional `pendingStatus`, and are omitted for
+deleted messages. Header actions receive `conversationId`, `contact`, `appearance`.
+The status indicator, swipe gestures and permission enforcement remain in place.
+Custom actions still require the customer's own authorization.
+
 ## Recommended hosted installation
 
 Run `npx --package @robono/server robono-messenger-install` in your Expo project. The installer sets up the connection and native plugin. Robono runs the communication services; your server verifies the existing login and issues its short-lived session. See the server package's [hosted guide](https://robono.com/guides/hosted-messenger.html).
@@ -396,3 +433,27 @@ when the person starts sharing. Rebuild both apps after native configuration cha
 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.
+
+## Business messages
+
+Use `createMessageCard` from `@robono/messaging` for supplied appointment/order
+cards. `components.customMessages` supports customer layouts and explicit format
+versions; `components.onCustomMessageAction` connects authorized actions.
+Unknown types use the required text fallback.
+[Card setup and limits](https://robono.com/guides/business-messages.html).
+
+## App-wide activity
+
+The complete Messenger connection supplies foreground activity independently of
+the selected chat. Online now and optional Last seen are chosen in Features &
+preview. `connection.availability` can also supply an authorized contact list.
+[Activity setup, privacy and timing](https://robono.com/guides/user-availability.html).
+
+
+## Recording, captions and local call tools
+
+Robono hosts optional call recording and transcription. Enable recording once in the existing Calling settings; every participant must agree before capture, and anyone can stop it. The supplied controls include the consent notice, active-recording status and captions. No customer recording server is required.
+
+The supplied adapters also offer camera/microphone/speaker checks and camera background blur. Screen sharing is separate. Phone blur requires rebuilding the native app; browser blur downloads its model only when selected and needs the documented content-security policy. Background processing stays on the device.
+
+See the [recording and call tools guide](https://robono.com/guides/call-recording.html) for prices, retention, short-lived downloads, deletion, platform requirements and label customization. Captions arrive in short batches with several seconds of delay and can be inaccurate; incomplete transcripts are marked.