# Preparing IaGenify for Android and iOS starts with one mobile workspace.

Canonical URL: https://www.iagenify.com/news/iagenify-mobile-android-ios-preparation

The mobile work begins from the Beta experience: an Android Trusted Web Activity project is in the repository, while the installable web app provides a shared foundation for iPhone and iPad.

## Key points
- The Android project wraps the Beta workspace in a Trusted Web Activity and targets the existing `/beta/` experience.
- Beta provides a standalone web-app manifest and platform icons as a shared mobile foundation.
- This is preparation, not a claim that Android or iOS store releases are available; native iOS packaging and store submission remain separate work.

A mobile release should feel like IaGenify, not like a separate product with a second account and a reduced set of services. The current preparation starts from the Beta workspace people already use, then checks what is needed to make that experience work as an app on Android and iOS.

## Android has a dedicated application shell

The repository contains an Android Trusted Web Activity project configured to open the Beta workspace at `/beta/`. It carries the application identity, launcher artwork, splash screen, notification delegation and the Android-to-web trust relationship. This shell keeps the product experience on the existing Beta origin instead of introducing a separate mobile backend.

## The Beta web app is the shared mobile foundation

Beta also publishes a standalone web-app manifest, a start path, theme colors and icons for browser installation. That gives mobile browsers the information they need to present the workspace as an installed web app and provides a common interface surface while the platform-specific packaging is prepared.

## Android packaging and store release are different milestones

An Android project and built packages are present in the workspace, but that alone does not mean a public Play Store launch is complete. Release readiness still depends on validating the production association, signing and versioning, device behavior, privacy disclosures and the store submission process.

## iOS needs its own release path

The Beta manifest already includes an Apple touch icon and a standalone display mode that support the installable web experience on Apple devices. The repository does not contain a native iOS project or an App Store package. A TestFlight or App Store release would therefore be a separate milestone, with its own build, device checks, signing and review.

Keeping those steps separate avoids promising availability before both platforms have been verified. The shared Beta experience is the starting point; platform packaging, account flows, mobile navigation, permissions, notifications and store requirements each need their own validation.

> One IaGenify workspace across devices; a distinct, verified release path for each mobile platform.

The mobile direction is now concrete: continue from the existing Beta workspace, prepare the Android shell, and shape the iOS path around the installable web app before committing to a native distribution approach. Android and iOS store availability will be announced only after those release checks are complete.

## FAQ
### Can I download IaGenify from Google Play today?
This preparation article does not announce a Play Store release. The Android project and packages are present, but public store availability requires a completed and verified release.

### Is there a native iOS app already?
No native iOS project or App Store package is present in the repository. The Beta installable web app is the current iOS-capable foundation.

### Will Android and iOS use separate accounts?
The direction is to keep the existing Beta workspace and account as the shared product experience.

### Does a built Android package mean the release is ready?
No. Device behavior, production association, signing, disclosures and store review must still be completed and verified.