3.2.0 Beta (Tuesday, October 15, 2019)
To enable Mobile Inbox on your account, contact your Iterable CSM.
Version 3.2.0 (beta) of Iterable's Android SDK works with Iterable's Mobile Inbox feature. With Mobile Inbox, users of your mobile apps can save in-app messages and revisit them when it's convenient or when the content is more relevant.
The SDK includes a default implementation of an inbox user interface, which can be customized as necessary to match your brand's styles. Also, it automatically captures inbox-related events to Iterable, where they can be used to segment users, filter and trigger workflows, or send system webhooks.
To get started with Mobile Inbox:
- Contact your CSM to enable the feature on your account.
- Read the Mobile Inbox documentation.
- Install the version 3.2.0 beta of Iterable's Android SDK.
3.1.0 General Availability (June 10, 2019)
Version 3.1.0 of the Iterable Android SDK is now generally available and supported by Iterable.
This version of the SDK automatically downloads new in-app messages, allows apps more control over which in-app messages to display and when to display them, and consolidates the way deep links are handled across push notifications, in-app messages, and emails. For more information, see the beta announcement.
How to upgrade
Upgrading to version 3.1.0 of the Iterable Android SDK requires some code changes in your mobile apps. For more details, take a look at the Migrating from a version prior to 3.1.0 instructions on GitHub.
This release deprecates and sets an end-of-life date for various older versions of Iterable's Android SDK, as described in the Android SDK Deprecation and End-of-Life Schedule. Also see Iterable's Mobile SDK Support Policy.
3.1.0 Beta (Monday, May 13, 2019)
Version 3.1.0 (currently in beta) of Iterable's Android SDK provides various new features:
- Automatic downloading of new in-app messages
- More control for mobile apps to decide when and how to display in-app messages
- Consolidated handling of deep link URLs, so that the same URLs work when sent in emails, in-app messages, or push notifications
Beta versions of Iterable's mobile SDKs are subject to the Beta Mobile SDK Terms of Service.
New and updated features
This version of the SDK provides the following new and updated features:
Automatic downloading of new in-app messages
With this version of the SDK, mobile apps automatically download all available in-app messages and store them on device. This makes it possible to inspect the messages to decide when and how to display them. Automatic in-app message downloads happen:
- When Iterable sends silent push notifications (not visible or audible to the user) indicating that new in-app messages are available.
- At key points in the mobile app's lifecycle, such as when it launches or comes to the foreground.
This feature makes it easier than ever to test in-app message campaigns. Simply send a proof and wait for it to appear in the app (no need to manually force the app to download new messages, as could be the case with previous versions of the SDK).
More control for mobile apps to decide when and how to display in-app messages
Since this version of the SDK automatically downloads all available in-app messages and stores them on device, the mobile app can examine each message to decide when and how to display it. For example, the app might:
- Skip displaying a particular message
- Display multiple messages in sequence (by default, in-app messages display in sequence, with a 30-second delay between messages—but this is customizable)
- Wait to display a particular message until a network connection is available
- Create a native user interface for a particular message, rather than rendering the HTML supplied by Iterable
- Display a particular in-app message when a user completes a specific action in the app
Consolidated handling of deep link URLs
This version of the SDK provides a common way to handle deep link URLs in a mobile app. With this feature, deep link URLs in emails, in-app messages, and push notifications are all handled in the same way, making it easier for marketers to define a set of deep link URLs that work as expected, regardless of message type.
How to upgrade
Upgrading to the 3.1.0 beta of the Iterable Android SDK requires some code changes in your mobile apps. For more details, take a look at the Migrating from a version prior to 3.1.0 instructions on GitHub.
To learn more, take a look at the Iterable Android SDK 3.1.0 beta on GitHub.
Mobile SDK Support Policy
A deprecated mobile SDK version is an iOS or Android SDK version for which Iterable has announced an end-of-life date.
A mobile SDK version's end-of-life date is the date after which Iterable will no longer support it. An SDK's end-of-life date will be 12 months after the release of its successor.
Iterable provides support for a mobile SDK version through its end-of-life date. During this period, Iterable will:
- Investigate bugs and provide fixes in newer SDK versions.
- Answer questions about the SDK version through standard support channels.
After the end-of-life date for a mobile SDK version, Iterable:
- Does not guarantee successful message delivery to apps using that SDK version.
- May turn off message serving for that SDK version if severe bugs are discovered (for example, app-crashing bugs).
- Will not answer questions about that SDK version though standard support channels.
Each time you upgrade your mobile apps, incorporate the newest versions of Iterable's mobile SDKs. Doing so reduces the likelihood that your apps will be using an SDK version that is nearing or reaches its end-of-life date.
Android SDK Deprecation and End-of-Life Schedule
The following schedule lists the deprecation dates, support windows, and end-of-life dates for various versions of Iterable's Android SDK. For details about how Iterable supports mobile SDKs, see the Mobile SDK Support Policy.
|SDK||SDK version(s)||Deprecation announcement date||Support window||End-of-life date|
|iterable-android-sdk||3.0.x (where x >= 9)||6/10/2019||12 months||6/9/2020|
|iterable-android-sdk||3.0.8 and older||6/10/2019||6 months||12/9/2019|