Native Share Plugin for Android & iOS

Native Mobile Integration Without External SDKs

The Native Share Plugin for Android and iOS is designed as a lightweight bridge between the Unity engine and the native sharing capabilities of mobile operating systems. One of the primary advantages of this specific implementation is the removal of external SDK requirements. In a standard mobile development workflow, social sharing often necessitates the integration of platform-specific libraries or heavy social media SDKs that can bloat the final build and introduce versioning conflicts. This tool bypasses those hurdles by utilizing the native share sheets already present in Android and iOS devices.

By operating through a single line of code, the plugin simplifies the process of passing data from the game environment to the user’s installed applications. This approach allows developers to trigger the standard OS interface where users can select their preferred communication method, whether that is messaging apps, social media feeds, or cloud storage.

Supported Media and Social Workflows

The utility is built to handle multiple types of content that are common in modern mobile applications. Specifically, it facilitates the sharing of screenshots and videos directly from the game’s runtime. For production teams, this functionality is essential for social features like “Photo Modes” or sharing high-score moments.

When a share intent is triggered, the plugin can pass media to a variety of third-party platforms. The source material highlights compatibility with major services including WhatsApp, Instagram, and Facebook. Because it relies on the native OS share sheet, it is not limited to these specific apps; it can generally interact with any application on the user’s device that is registered to receive share intents for images, videos, or files. This makes it a versatile tool for both games and utility-based mobile apps that require simple, reliable content distribution.

Technical Environment and Pipeline Support

Version 3.1 of the plugin maintains compatibility across a wide range of Unity versions and rendering setups. It is verified for use in Unity 2022.3.17 and the newer 6000.2.2 release. This ensures that projects transitioning to the latest long-term support (LTS) versions or exploring the features of Unity 6 can maintain consistent sharing functionality.

From a rendering perspective, the plugin is agnostic toward the visual pipeline used in the project. It fully supports:

Built-in Render Pipeline
Universal Render Pipeline (URP)
High Definition Render Pipeline (HDRP)
Custom Scriptable Render Pipelines (SRP)

This broad compatibility is particularly useful for developers working on high-fidelity projects in HDRP or mobile-optimized titles in URP. Since the plugin handles the data transfer after the frame has been rendered or the video file has been encoded, it does not interfere with the specific rendering logic of the scene.

Build Optimization and Android Management

With a total file size of only 748.7 KB and a package consisting of 21 assets, the plugin has a minimal footprint on the overall project size. This is a critical consideration for mobile developers who are often constrained by over-the-air (OTA) download limits on cellular networks. The package is delivered as a standard unitypackage, making it easy to import into existing project structures without complex installation steps.

For Android-specific builds, the plugin has been updated to utilize the latest Gradle libraries. This is a significant detail for developers who must keep their projects compliant with evolving Google Play Store requirements and modern Android build tools. By using current Gradle configurations, the plugin reduces the likelihood of build errors during the compilation phase, specifically regarding manifest merging and library dependencies.

Practical Implementation in the Development Cycle

Integrating the Native Share Plugin typically occurs during the UI and social systems phase of development. Rather than writing custom JNI (Java Native Interface) wrappers for Android or Objective-C code for iOS, the developer can call the sharing function directly within a C# script. This centralization of the codebase allows for easier maintenance and debugging.

In a real-world production scenario, a developer might use this plugin to enable a “Share Your Progress” button. When the user taps the button, the code captures the current screen buffer as a texture, saves it temporarily, and then passes the file path to the native sharing method. The OS then takes over, presenting the user with their familiar list of apps, ensuring a consistent user experience that matches the rest of their mobile environment.