Legacy Mobile App v2.34.4, Unified Mobile App, and What’s Next

Dear Status App Community,

As many of you know, the Status app has historically been developed from two distinct codebases: one built with Qt technology, powering Status Desktop, and another built with Clojure, powering the current Status Mobile (referred to as Status Legacy in this article).

Over the years, the team has made tremendous efforts to maintain and evolve both versions. However, developing and supporting two separate codebases for the same app adds significant coordination costs and complexity across all areas — product, development, design, infrastructure, and testing.

This has limited our ability to ship faster, remain competitive, and grow a broader community of developers and users around the Status ecosystem.

A Unified Path Forward

In May 2025, the Status team made the decision to focus on a single codebase — the Qt codebase powering Status Desktop — and develop it to serve both Desktop and Mobile platforms.

By unifying both Mobile and Desktop apps under one unified codebase, we aim to:

• Simplify and streamline our development and delivery process.

• Address duplicated efforts and costs across product, design, and infrastructure.

• Ship faster to market and respond more effectively to community feedback.

The initial version of the unified Status Mobile App (referred to as Status in this article) for Android (built from the Status Desktop codebase) will be released next week, with iOS support to follow shortly.

More information can be found in the “What’s Next for Unified Mobile App?” section of this post.

Users will be able to install and run it alongside their Status Legacy mobile app and easily migrate their profiles and data.

For detailed instructions on how to do this, read the “Migrating Data from Status Legacy to Status” section below.

What’s Next for Status Legacy?

The team is now releasing the final feature release (v2.34.4) of the legacy Status Mobile App (Status Legacy), which includes:

• Renaming the app to Status Legacy and changing its icon to blue, so users can easily distinguish it from the unified Status mobile app (Status).

• Two new features to make user profile and data migration to the unified Status mobile app (Status) simple, secure, and private:

Optional message syncing across devices using end-to-end encrypted app pairing. Go to Settings → Syncing and Backup → Paired Devices → Tap + to start a new sync → Enable message syncing.

On-device backup to manually back up your Status profile data (including optional backup of your direct, group, and community messages) directly on your device. Go to Settings → Syncing and Backup → Backup.

While the Clojure-based Status Legacy app (Status Legacy) will remain public and open for contributions, the core Status team won’t add new features beyond the current v2.34.4 release. The team will focus on developing the unified Status Mobile App (Status) going forward. We may issue critical fixes, if absolutely needed, during the 2–3-month user migration period.

Update your Status Legacy up to v2.34.4

What’s Next for Unified Mobile App?

Since June 2025, the team has been adapting the Status Desktop codebase for mobile use, bringing over components and UI/UX patterns while ensuring usability on smaller mobile screens.

The Initial version of the unified Status Mobile App (referred to as Status in this article) introduces many features already available on Status Desktop, including community management, translations, payment requests, the sticker store, and more.

There are a few limitations that remain to be addressed in upcoming releases:

UI/UX Adaptation: The current design is an early adaptation of the Desktop UI/UX for mobile. While the team ensures that main user flows are functional, some may still be imperfect or blocked. Please report any issues on GitHub (after checking for duplicates). The team is gradually evolving the app toward a mobile-native look and feel.
Keycard Support: Coming in future releases. This feature requires the development of a new Qt library compatible with both Desktop and Mobile.
Push Notifications: Planned for upcoming releases.
Biometrics for Password Autofill: Currently available for login and will soon be extended to other user flows requiring password authentication in upcoming releases.

The Initial version of Status will be distributed through testing tracks on the Google Play and Apple App Stores.

The team will be iterating quickly and shipping frequent updates, so please expect occasional instability while the app remains on the test track before transitioning to a production release.

Migrating Data from Status Legacy to Status

You can migrate your Status profile from the Status Legacy app to the new, unified Status app in two secure ways:

1️⃣ Migration via Status Syncing

Requirements:

• Update your Status Legacy app to v2.34.4.

• No recovery phrase required.

• For iOS users: update your Status Desktop to v2.36 or greater. Status Desktop v2.36 will come out in two weeks.

Security and privacy of Status syncing:

• End-to-end encrypted using your profile private key.

• Pairing occurs only via your local network.

Migration steps:

Update your Status Legacy to v2.34.4.
Go to Settings → Syncing and Backup → Paired Devices.
Tap + to start a new sync.
Optionally, enable the message syncing toggle if you would like to sync your direct, group, and community messages alongside the other data of your Status profile.
Follow the in-app pairing instructions (the “i” icon in the top-right corner) for syncing:
1. Android: You can sync your Status Legacy app directly with Status on the same device using your pairing code.
2. iOS: You need to first sync your Status Legacy app with Status Desktop (you need to be on Status Desktop v2.36 or greater), then sync Status Desktop with the unified Status mobile app (Status), since iOS doesn’t support syncing the two mobile apps on the same device.
Install and open the unified Status mobile app (Status) from the Google Play Store or Apple App Store.
On “Welcome Back”, select "Log in".
Optionally, choose whether to share usage data.
On “Log in”, select “Log in by syncing”.
Choose QR or Code entry method.
Optionally, choose to enable biometrics to fill in your password.
Repeat for each profile you wish to migrate.

2️⃣ Migration via On-Device Backup

Requirements:

• Update your Status Legacy app to v2.34.4.

• Your Status recovery phrase is required.

Security and privacy of Status backups:

• Encrypted with your profile private key.

• On-device backup files are created and stored only on your device.

Migration steps:

Update your Status Legacy to v2.34.4
Go to Settings → Syncing and Backup → Backup.
Optionally, enable the message backup toggle if you would like to sync your direct, group, and community messages alongside the other data of your current Status profile.
Tap “Back up data locally” to create and save your current Status profile backup file. You can choose any location on your device to save your backup file.
Install and open the unified Status mobile app from:
1. Google Play Store: [the link will be added next week once the app is released]
2. Apple App Store: [the link will be added next week once the app is released].
On “Welcome Back”, select Log in.
Optionally, choose whether to share usage data.
On “Log in”, select Enter Recovery Phrase.
Paste or type your Status recovery phrase and create a password.
On Import Local Backup, either:
1. Select “Import from file…” to import your current Status profile backup file saved on step #4 above, or
2. “Later” to skip for now and later go to Settings → Syncing → Import Local Backup File.
Optionally, choose to enable biometrics.
Repeat for each profile you wish to migrate.

We’re excited to enter this new chapter for Status, bringing a unified app experience across Desktop and Mobile that empowers privacy-preserving communication and crypto self-custody for everyone.

Note

The Status app is still in active development, so you may encounter bugs.

Your feedback helps us build the best app for secure crypto, private messaging, and community-owned spaces. You can report bugs on our GitHub, or share your thoughts directly in the feedback channel within the Status Community.

Don’t miss the latest news from Status – follow us on X or join our Community in the Status app to get the latest news and updates!

Your use of the Status apps is subject to the Status Terms of Use and Privacy Policy.