iMessage Extension Development: Stickers, Cards, and Games

Users communicate in iMessage, and your service works right inside the chat. No need to leave the Messages app to send a sticker, vote, or make a move in a game. An iMessage extension is a separate Extension target inside an iOS app, embedded in iMessage. Since the technology’s inception, we have developed over 20 projects for the App Store, guaranteeing pass of App Store review and avoiding rejections under sections 4.2 and 5.1. On one social app project, we built an interactive poll-sharing extension, reducing message delivery latency from 5 seconds to under 1 second by switching to URL-encoded data and implementing NSCache.

Sticker Pack vs MSMessagesAppViewController

Sticker Pack — the simplest option without code: add an Extension target of type "Sticker Pack Application", upload PNG/APNG/GIF to Stickers.xcassets. Apple generates the UI automatically. Sizes: Small (100×100 pt), Regular (136×136 pt), Large (206×206 pt). APNG — up to 500 KB, GIF — up to 25 MB (not recommended due to quality loss).

MSMessagesAppExtension — a full extension with UIKit or SwiftUI. Entry point is MSMessagesAppViewController. Two modes: Compact (~225 pt) and Expanded (nearly full screen). Switch via requestPresentationStyle(.expanded). Messages are represented by MSMessage objects with URL and MSMessageTemplateLayout (image, caption, subcaption). On tap, the recipient opens the extension if installed.

Why Choose MSMessagesAppViewController?

MSMessagesAppExtension is 10 times more flexible than Sticker Pack: it allows interactive cards, multiplayer games, polls, and integration with purchases via StoreKit 2. Sticker Pack is only suitable for static or animated stickers. If your project requires any interactive scenario—choose MSMessagesAppViewController.

Limits and Constraints of iMessage Extension

The main constraint is RAM: Apple allocates about 100 MB. Exceeding it causes an EXC_RESOURCE crash. Use NSCache with countLimit and totalCostLimit, avoid heavy images in cache, load data asynchronously. Second constraint is the URL size for data transfer: encode data into query parameters or base64, avoid large payloads.

How to Pass Data Between Participants?

Data is encoded into the URL of the MSMessage object: MSMessage.url = URL(string: "yourapp://state?data=\(encodedState)"). The recipient parses the URL in willBecomeActive(with:). You cannot directly use UserDefaults—each participant has their own device. For shared data between the main app and extension, set up an App Group: use the same identifier group.com.yourapp.shared in Capabilities of both targets. Then read/write via UserDefaults(suiteName:) and FileManager.containerURL(forSecurityApplicationGroupIdentifier:).

Comparison of Compact vs Expanded Modes

Comparison of Sticker Pack vs MSMessagesAppExtension

Development Process

1. Scenario analysis — determine how the user interacts in compact and expanded modes.
2. Design — architecture considering memory limits and data transfer.
3. Implementation — write code in Swift/SwiftUI using MSMessagesAppViewController.
4. Integration — set up App Group, StoreKit 2, push notifications.
5. Testing — on real devices (at least 2 iPhones with different iOS versions).
6. Publishing preparation — App Store Connect, TestFlight, metadata.
7. Support — 30 days of free technical support after release.

What’s Included in the Work

You receive: project source code with comments, configured App Groups and StoreKit, prepared metadata for App Store Connect, a publishing guide, and 30 days of technical support after release. Additionally, we provide full documentation covering architecture, data flow, and App Group setup; access to the repository with version history; training for your team on working with extensions; and a guaranteed submission to the App Store with support during the review process. If needed, we assist with fixing any rejection issues within the warranty period.

Timeline and Budget

Sticker Pack (no code): 1–3 days (design + assembly) — from $500. iMessage Extension with interactive cards: 3 to 5 weeks — from $5,000. Multiplayer game or complex data exchange: 6 to 10 weeks — from $12,000. The cost is determined after scenario analysis—we ensure a transparent budget structure. Contact us for a preliminary timeline and cost estimate. Get a consultation—we’ll assess the complexity of your task and propose an optimal solution. Order development today.

Source: Apple Developer Documentation on Messages

Development of Widgets, App Clips, and Live Activities: Entry Points Outside the App

We understand that users see your app not only when they open it. A widget on the home screen, a live score in Dynamic Island, a mini experience without installation — these are separate entry points that we implement within platform constraints. Over 5 years, we have developed more than 50 extensions for mobile apps, from simple informational widgets to App Clips with payment scenarios, saving clients up to 30% of time on repeat visits.

What entry points should you consider for your app?

WidgetKit Widget Development: Why You Can't Just "Add a Widget"

WidgetKit works via a Timeline Provider — the widget doesn't stay in memory continuously; it requests data snapshots in advance. The most common mistake: developers try to show real-time data via URLSession directly from getTimeline(). Apple doesn't prohibit this, but with aggressive updates, the system starts throttling requests, and the widget gets stuck on outdated data.

The correct approach: the main app updates data via WidgetCenter.shared.reloadTimelines(ofKind:) — after receiving a push notification or when the user returns to the foreground. The widget reads data from a shared App Group container using UserDefaults(suiteName:) or file storage. No direct network requests in the provider in production.

In the latest iOS versions, AppIntent-based interactive widgets have emerged — buttons and toggles directly on the widget without opening the app. This is implemented via Button(intent:) in the SwiftUI widget layout. Only works for simple actions; complex logic should transition to the app via widgetURL.

How Live Activities Change User Experience?

Live Activities are a mechanism for displaying live data on the Lock Screen and Dynamic Island (iPhone 14 Pro+). They are launched via ActivityKit, updated via push notifications of type liveactivity with a payload up to 4KB.

Architecturally, it's a separate SwiftUI target with two views: compact (Dynamic Island) and expanded (Lock Screen). Data is passed via ActivityAttributes — a strictly typed structure. The dynamic part is ContentState, while the static part (unchanged during the activity) is directly in ActivityAttributes.

A typical issue: Live Activity doesn't update on the device even though push is sent. The reason is that the app doesn't have permission for background push or apns-push-type is set incorrectly. In production, you need apns-push-type: liveactivity and a token from activity.pushToken. According to Apple documentation, without a correct push token, the Activity won't receive updates.

When to Use App Clips vs Instant Apps?

App Clips (iOS) and Instant Apps (Android) solve a similar problem — provide functionality without installing the full app. But the implementation is fundamentally different.

App Clip is a separate target in Xcode, max 15MB, launched via NFC tag, QR code, Safari Smart App Banner, or a link in Messages. Data access is limited: no Keychain sharing with the main app without explicit setup, no access to HealthKit, no push notifications (only ephemeral). The App Clip Card is configured in App Store Connect, and metadata errors are a common reason for rejection.

Android Instant Apps are built on a modular architecture: the app is divided into feature modules, each of which can be downloaded separately via Play Feature Delivery. An Instant App is a feature module with <dist:module dist:instant="true">. The limitation is no more than 15MB total for instant delivery.

Comparison shows that App Clips win in payment scenarios due to Apple Pay integration — conversion is 20% higher compared to Instant Apps in similar cases. Instant Apps are better suited for game demos and services requiring quick access via Google Search.

What Does Our Work Include?

• Audit of current architecture: determine which entry points your app needs — widget, Live Activity, App Clip, Instant App.
• Prototyping: visual model of the extension following platform guidelines (Apple HIG, Material Design).
• Development: implementation in Swift (iOS) or Kotlin (Android) using WidgetKit, ActivityKit, App Clip API, Play Feature Delivery.
• Integration: setting up App Group, Keychain sharing, push certificates, provisioning profiles.
• Testing: on real devices (iPhone, iPad, Android) and simulators. For Live Activities, test via xcrun simctl push.
• Publication: preparing metadata for App Store Connect (App Clip Card) and Google Play Console (Instant App configuration).
• Documentation and training: architecture description, widget update instructions, push notification troubleshooting.

How Does Our Development Process Work?

1. Analytics: which app features are truly needed outside the app, and which mechanism fits. Widget for forecast — WidgetKit. Real-time delivery tracking — Live Activity. Payment at checkout — App Clip.
2. Design: choosing stack, data update schemes (Timeline, push), UI layouts for compact and expanded views.
3. Implementation: writing code in Swift/Kotlin, configuring App Group, push certificates, test schemes.
4. Testing: each extension is tested in isolation. WidgetKit rendering is verified via Xcode Widget Gallery, Live Activities via simulator with forced push.
5. Deployment: publishing to stores, monitoring metrics (update frequency, App Clip launch count).

Estimated Timeframes

Cost is calculated individually after audit. An estimate is provided within 2 business days.

What Are Typical Mistakes in Extension Development?

• Too frequent widget updates — leads to throttling and empty state. We recommend an interval of at least 15 minutes (see Apple Human Interface Guidelines in WidgetKit documentation).
• Ignoring shared container — the widget doesn't see data because it uses its own UserDefaults instead of App Group.
• Lack of fallback for Live Activities — if push isn't delivered, the user sees outdated data. A periodic polling mechanism via Activity.update with pushType: nil is needed.
• Incorrect App Clip Card metadata — a common reason for rejection in App Store Review. For example, incorrect URL or missing icon.

Contact us to assess which extension fits your app. Order an audit of current entry points — we'll find non-obvious scenarios for widgets and App Clips. Get an engineer consultation on architecture today.