Your experience.
Their Robono conversations.

This example shows the flow. Supply your platform's secure storage, cryptography, app-opening and lifecycle handlers. The integration guide includes React Native adapter examples for iOS and Android.

import { RobonoLinkedApps } from '@robono/linked-apps';

const robono = new RobonoLinkedApps({
  app: {
    name: 'Your App',
    developerName: 'Your Company',
    websiteUrl: 'https://example.com',
    privacyUrl: 'https://example.com/privacy',
  },
  tokenStore, // Keychain / Keystore adapter
  crypto,    // Secure platform crypto adapter
});

// Requires @robono/linked-apps 0.1.0-preview.4 or newer.
const pairing = await robono.beginPairing(
  ['account:read', 'messages:read', 'messages:send']
);
// Display pairing.userCode. Keep pairing.pending in secure storage.
// User: Robono → Linked apps → Connect an app → enter code → approve.
const controller = new AbortController();
// Cancel on leaving the screen/backgrounding; resume on return if unexpired.
await robono.waitForPairing(pairing.pending, controller.signal);
// Connected: credentials have been saved through tokenStore.

Keep tokens and the pending verifier in Keychain or Keystore. Codes expire after five minutes. No callback URL or extra SMS verification is needed for code pairing. Use one SDK instance per connected account and coordinate refreshes across processes.

const conversations = await robono.conversations();
const history = await robono.messages(conversationId, { limit: 50 });

// Generate and persist a UUID once; reuse it on retries.
await robono.send({
  conversationId,
  clientMessageId: savedOutgoingId,
  messageKind: 'text',
  textBody: 'Hello from our app',
});

Use conversation capabilities to decide which tools to display. A successful send response acknowledges acceptance; it does not prove that the recipient has received or heard a message.

For voice or files, call createUpload, upload the bytes with uploadBytes, then call send with the returned media ID. Preserve a recording's measured duration. The API reference lists media fields and supported message kinds.

Use download for an expiring playback or download URL. Keep URLs private. Mark a voice message heard only after actual listening.

Use watch to open an authenticated persistent connection. The SDK reconnects and recovers missed changes from a saved cursor. No delivery endpoint needs registration. Save the cursor after processing succeeds, deduplicate message IDs, and reconcile deleted or unavailable content. Events are retained for seven days; an expired cursor requires a fresh synchronization.

For background notifications, your backend can maintain the same SDK connection and route updates to your users. No webhook is offered. Protect linked credentials and coordinate token refreshes through one owner per grant.

Your backend sends a content-free sync hint using your own app's APNs, FCM, or Expo credentials. Fetch current messages when the app wakes or resumes. Background execution is controlled by the operating system and is not guaranteed. Keep companion hints silent by default to avoid duplicating Robono alerts.

Current preview limits per grant, per minute: 60 send operations, 120 media operations, 120 event polls, and 300 other operations. Authorization starts are limited to 60 per app per minute. Limits may change before production.

Respect HTTP 429 responses and back off. Retry a message with its original saved UUID to avoid duplicates. Do not blindly retry token exchanges: refresh tokens rotate, and reusing a spent refresh token revokes access.

Access tokens last 10 minutes, refresh tokens up to 30 days, and grants up to 90 days. Ask the user to reconnect when needed. Never log credentials, callback codes, or message contents.

Call disconnect() to revoke your connection, then stop watchers and clear cached account data. Also handle revocation from Robono, account deletion, and account switching. Previously received data must be handled according to your disclosed retention and deletion policy.

• Approval and denial; wrong or expired pairing code; account switching.
• Text, voice and supported files; retries without duplicate messages; accurate receipts.
• Blocked contacts, disconnected relationships, history deletion, and network restrictions.
• Offline recovery, interrupted connections, expired cursors, and token expiration.
• Notifications on and off; locked screen, background and relaunch on physical iOS and Android devices when supported.
• User revocation and account deletion stop access and clear local account data.

Keep your test results. Publish your data-use, retention and deletion practices, protect credentials, and provide support and security contacts. Do not sell message content or use access beyond the user's consent.