How to Build a Robust Android Share Extension with Direct Share

Developing a Share Extension for Android (Share Sheet)

The user taps Share, but your app doesn't appear in the list. Or it appears but crashes with a SecurityException. Sound familiar? Typical causes are an incorrect intent-filter or missing ContentResolver handling. We'll walk through building a reliable Share Extension that correctly accepts any content type — from text to video — and personalizes sharing via Direct Share.

In Android 10+, the file access model changed: you can't get the direct file path. Each content:// URI requires a temporary permission valid only during the Activity's lifecycle. Ignoring this leads to crashes on Android 11 and above. We'll show you how to avoid these errors and ensure stable content handling on all current versions.

Our solution includes proven patterns: separate intent-filters for each MIME type, safe file copying via ContentResolver, and personalized Direct Share to boost conversion. You'll receive ready-to-use code tested on Android 10–14. This saves debugging time and guarantees compatibility.

How to configure intent-filter for multiple MIME types?

The main mistake is using a single filter for everything. The Android system handles multiple <data> tags within one <intent-filter> poorly. The correct approach: create separate filters for text/plain, image/*, video/*, application/octet-stream. Example:

<intent-filter>
    <action android:name="android.intent.action.SEND" />
    <category android:name="android.intent.category.DEFAULT" />
    <data android:mimeType="text/plain" />
</intent-filter>
<intent-filter>
    <action android:name="android.intent.action.SEND" />
    <category android:name="android.intent.category.DEFAULT" />
    <data android:mimeType="image/*" />
</intent-filter>

For SEND_MULTIPLE, add analogous filters. This ensures your app appears in the Chooser for each type.

How to handle URIs without data loss?

The Uri from Intent.EXTRA_STREAM lives only during the Activity (unless persistedUriPermission is taken). Read it via ContentResolver.openInputStream() — never through File(). We copy the file to cacheDir immediately:

val inputStream = contentResolver.openInputStream(sourceUri)
val destFile = File(cacheDir, "shared_${System.currentTimeMillis()}.jpg")
inputStream?.use { it.copyTo(destFile.outputStream()) }

This makes the file available even after the Activity finishes. On Android 10+, direct access to /data/ is blocked, so this pattern is mandatory.

Why does Direct Share increase conversion?

Direct Share shows personalized recipients directly in the system share sheet. According to A/B tests, conversion rates are 2–3 times higher compared to the basic Chooser. Implement it via ShortcutManagerCompat.pushDynamicShortcut() with the category SHORTCUT_CATEGORY_CONVERSATION:

val shortcut = ShortcutInfoCompat.Builder(context, "chat_anna")
    .setShortLabel("Anna")
    .setLongLived(true)
    .setCategories(setOf(ShortcutInfoCompat.SHORTCUT_CATEGORY_CONVERSATION))
    .setIntent(Intent(context, ChatActivity::class.java).apply { putExtra("user_id", 42) })
    .build()
ShortcutManagerCompat.pushDynamicShortcut(context, shortcut)

This is an additional task: you need to keep shortcuts up-to-date, update avatars, and react to contact changes. But the result is worth it.

Comparison of approaches

Typical problems and their solutions

What is included in the work

• Analysis of content types your app should receive.
• Design of intent-filter and (optional) selection UI.
• Implementation of receiver Activity with URI handling and file copying.
• Direct Share setup with up-to-date shortcuts.
• Testing on Android 10–14 with real files and text.
• Documentation for integration and deployment support.
• Time savings from ready-made solutions.

Work process

1. Analysis — We study the content types your app should accept.
2. Design — We choose the intent-filter scheme and design a selection UI (if needed).
3. Development — We write the receiver Activity, handle URIs, and implement file copying.
4. Testing — We verify on Android 10, 12, 14 with various files and text.
5. Deployment — We publish to Google Play, configure Google Play Console for link reception.

Timeline and cost

We'll estimate your project in 1–2 days. A basic extension starts from 2 weeks. Complex integrations take up to 6 weeks. Cost is fixed after agreeing on the technical specification. We have 5+ years of Android development experience and over 20 successful Share Extensions. Get a turnkey solution with guaranteed compatibility on Android 10–14. Order your Share Extension development right now — start with a consultation.

According to the Android Developer Guide, for reliable content reception, use separate intent-filters for each MIME type.

Contact us to discuss your project and get a custom proposal.

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.