Skip to main content

The same AI agent in your app as on your website: what Conversation SDK lets you build

November 13, 202610 min readPatryk Gmitrzuk

One setup for your website and your mobile apps.

When the conversation in your mobile app is built separately from the one on your website, the two drift apart. A feature reaches the website first. The app gets it later, once someone builds it again and your team ships an app release.

Zowie Conversation SDK is one product for both: your website and your Android, iOS, React Native and Flutter apps. It is how you give customers the same conversation with your AI agent wherever they meet it. Here is what it lets you build, at a glance.

At a glance

Your brand on every screen

Colors, light or dark mode, corners, logo and texts. You set them once in Zowie, and they apply on your website and in your app.

Illustrative examples with a fictional bank.

One configuration, one look

This is the core of it. Your website and your apps share one configuration in Zowie: texts, design and behavior. You set it up once, and it applies on every platform where you use Conversation SDK. Change the primary color, the color mode or the corners, and the change applies on your website and in your app. There is no second configuration to keep in step.

One configuration, every platform
Configured once in Zowie
  • Texts
  • Design
  • Behavior
  • Widget
  • Embedded
  • Android
  • iOS
  • React Native
  • Flutter
All six connect to the same AI agent.
One change, every screen
Primary color
Color mode
Corners
Close-up
Website
App
Illustrative. Try the settings: both screens read the same configuration.

The result is a conversation that looks and behaves the same on your website and in your app, on Android and iOS. Dark mode, right-to-left languages and rich content work in both. A customer who knows the conversation from your website recognizes it in your app.

What you can build with it

Every platform renders the same conversation. So what your AI agent does on your website, it also does in your app.

Visual aids that look the same everywhere

Your AI agent can show interactive content inside the conversation: product cards, input fields or your own custom views, such as an order summary or a booking confirmation. Visual aids work on the website and in the mobile SDKs.

Your own views are web pages that you host. You build one page, and it appears in the conversation on the website and in the app, in text chat and in Hello.

Take a bank customer whose debit card is cracked. The AI agent finds the card and shows it in the conversation. The first figure shows the answer on the website, the second shows the same answer in the bank's app.

Website · text

My debit card is cracked and the chip no longer works. Can I get a new one?

Of course. Should I send the new card to your home address or to a branch?

Debit card
Illustrative example with a fictional bank.
App · text

My debit card is cracked and the chip no longer works. Can I get a new one?

Of course. Should I send the new card to your home address or to a branch?

Debit card

Type or talk

Hello, Zowie's voice channel, works in your app as it does on your website: a spoken conversation with visuals on the screen. Customers can switch between typing and talking within one conversation.

App · voice

Home address.

Done. Your new card is on its way to your home address. It arrives in 3 to 5 business days.

Replacement card ordered

A conversation that knows the customer

You can pass customer details to the conversation: name, email, language and your own attributes, such as a customer tier or an order number. Your processes can use them, and every platform accepts the same fields.

The same conversation on another device

When your customers are logged in, you can identify them with a token signed by your backend. A customer identified this way returns to the same conversation on any device and platform where they log in.

This comes from authentication in Zowie. Conversation SDK passes the token in the same way on the website and in every mobile SDK.

Connect the conversation to your app

A conversation rarely ends in the chat window. The customer wants a screen opened, a setting changed or a document found. Conversation SDK tells your app what happens in the conversation, and your own code decides what to do next.

Your process triggers an action

Picture a bank customer in the app, talking to the AI agent. She says: “Open my card settings.” She does not look for the right tab or tap through a menu. The app opens the Cards screen for her.

Asked in the conversation, done in the app

Open my card settings.

Opening your card settings.

openCardEVENT
Illustrative example with a fictional bank.

This is a custom event. The process sends it with a name and parameters, and nothing extra is shown to the customer. On the website the event reaches your page. In a mobile app it reaches your app's code, with the same name and parameters.

What happens next is up to you: open a screen, update the cart or show a banner. It works in text chat and in Hello.

The same event, on both sides
In your process
ui.sendEvent("openCard", {
  cardId: "demo-card",
});
In your app (React Native)
<ZowieChat
  baseUrl={baseUrl}
  instanceId={instanceId}
  onGenericEvent={onEvent}
/>

function onEvent(name, params) {
  if (name === "openCard") {
    openCard(params.cardId);
  }
}
Illustrative. The event's name and parameters are yours, and so is what your app does with them.

Your app hears the conversation

The SDK also reports the conversation's own moments to your app: it has loaded, a conversation started or ended, a message was sent or received, the session expired, the number of unread messages changed. An app can use the last one to show an unread badge on its support tab.

Links open where you want them

When a customer taps a link in the conversation, your app can take it over and open the matching screen or an in-app browser. If your app does not handle the link, the device opens it as usual.

Same events, your code

The events are the same on the website and in every mobile SDK. Handling them is your team's code, written for your website and for your app.

Less work for your teams

Improved without an app release

When we improve the conversation experience, most changes reach your app users at the same moment as your website visitors. There is no wait for App Store or Google Play review.

When you improve the conversation
Built separately for the app

App users wait for the next app release.

  1. Improved on the website
  2. Built again for mobile
  3. App release
  4. Store review
  5. App users get it
A bank customer frowning at the app on her phone.
With Conversation SDK

App users get it when your website visitors do.

  1. Improved once. Website visitors and app users get it.
The same customer smiling at her phone, a coffee in her other hand.
This is how most improvements travel. The occasional change needs a new SDK version.

Quick to add

On your website, the conversation is one snippet, added in your code or through Google Tag Manager.

In your app, your team adds one package and two values from Zowie: the Base URL and the Instance ID. The packages are public and have minimal native dependencies, which means fewer conflicts with the rest of your app.

Each platform has its own package: ai.zowie:conversation-sdk for Android, the Swift package ZowieConversationSDK for iOS, @zowieteam/conversation-sdk-react-native on npm and zowie_conversation_sdk on pub.dev.

The SDKs use the same options and methods on every platform. A team that has set up Zowie on your website already knows them.

If Zowie already runs on your website, your configuration is ready. What your app still needs is the SDK.

Add it to your app
  1. Add the package
  2. Paste two values
  3. Open the conversation

Good to know

  1. Returning to the same conversation on another device requires logged-in customers and JWT authentication, set up together with your Zowie team.
  2. The conversation is stored on the device, so your app should end it when a customer logs out.
  3. Hello is activated by your Zowie team.
  4. Some settings, such as the chat button and display conditions, apply to the website widget only.
  5. The occasional change needs a new SDK version, which your team updates like any other library in your app.

Available now

Already using Zowie? Conversation SDK is in your account today. In Zowie, go to Automate, then Channels, and open the Conversation SDK card. The documentation covers setup on every platform.

  • On your website: nothing to do. Your setup is now Conversation SDK for Web and keeps working as it is.
  • In your app, on the previous Zowie SDKs: plan the switch for an app release before March 1, 2027. The previous SDKs are supported until February 28, 2027 and stop working on September 30, 2027. There is no old code to convert: your team adds the new SDK, then removes the previous one.

New to Zowie? We'll show you one AI agent on a website and in a mobile app, set up from one configuration.

Stay ahead of the conversation

Get insights on the future of Customer AI, real-world use cases, and strategies for replacing clicks with seamless conversations - delivered straight to your inbox.

By submitting the form, you acknowledge our Privacy Policy and agree to receive email communications from us.