For Android developers and publishers.
Drion Capsule packages your Android app with the Drion runtime as a standalone application for Linux, including SteamOS. Users install and open your app directly, without setting up Drion separately or navigating an Android launcher.
Drion provides the compatibility layer for running Android apps on Linux. Capsule packages that technology around your product, with its own name, icon, and direct launch.
Instead of asking users to install a runtime, obtain an APK, and configure an Android environment, you deliver a prepared application. They open your product, not a general-purpose Android launcher.
A Capsule can include supporting components, such as an on-screen keyboard, while still appearing as one application to the user.
Lets users install and run Android apps on Linux.
Lets developers ship a specific Android product together with Drion as a standalone application.
Capsule is a distribution edition of Drion: the same runtime, shipped as your app.
Use your existing Android application as the starting point for a Linux release, rather than rebuilding it around another UI framework. Compatible apps can start from an existing APK; input, layout, and third-party integrations are reviewed for the target platform.
Ship under your own name and icon, with a direct entry into your application. Users do not need to choose an APK or go through a separate Android launcher.
Package your app with a selected Drion version and product configuration. Test and release that combination together instead of relying on users to assemble a compatible environment.
Capsule stores application data and settings separately from the files you distribute. New builds can update the application and runtime while retaining user state through supported update paths.
Components such as WebView, an on-screen keyboard, host integrations, and input profiles are selected for the application and target platform.
Preparation starts with your application and the devices you want to support. The work is app-specific: running an APK is the starting point, not a substitute for release testing.
Review the application’s main user journeys on the target platform: launch, sign-in, graphics, audio, input, and any required third-party services. Identify compatibility gaps and platform-specific requirements before preparing a release.
Set the application’s identity, runtime configuration, input profile, and supporting components. Adapt controls, layouts, or integrations where the target device needs a different experience.
Build the distribution package and verify installation, launch, updates, retained data, and clean shutdown. Prepare the artifact for the selected distribution channel.
Prepare a standalone application for compatible Linux desktops. Capsule supports archive packaging and signed Flatpak builds, with the runtime included. Desktop integration and system requirements are checked for the selected target.
Prepare your app or game for SteamOS, with input and presentation configured for the intended device. Tell us whether you are targeting Steam Deck, Steam Machine, or another SteamOS device so we can assess the requirements for your app.
Capsule can generate Linux depot content for Steam distribution.
Compatibility is validated for the application and target devices. Store publication and review are separate from package generation.
Capsule uses the same compatibility core as Drion. Your application runs in sandboxed Linux processes, using the Android Runtime and Android framework components while Drion provides the system-side integration.
There is no separate Android operating system to boot in a virtual machine or system container. Execution is local, not streamed from a cloud-hosted Android device.
Capsule does not require a separate implementation just to target Linux. An existing Android build can be the starting point. Depending on the app and target device, you may still need to adapt controls, layouts, or third-party integrations before release.
No. The Drion runtime is included with your application. The target system must still meet the requirements of the selected Linux package.
Compatibility is assessed per application. Native libraries, proprietary services, device-integrity checks, and DRM can affect whether an app or individual features work. Sign-in, payments, and other store-specific integrations need their own review.
Capsule can generate Linux depot artifacts for Steam. Store onboarding, publication, review, and any device-compatibility rating remain separate steps.
You release new builds through your chosen distribution channel. A build can include an updated application, runtime, and configuration. User data is stored separately, and supported update paths should be tested as part of each release.
Tell us about your application and the devices you want to support. We’ll discuss compatibility, any adaptations, and the right distribution format.
Email capsule@actinis.io