
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.
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.
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:


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
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:
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.
You can migrate your Status profile from the Status Legacy app to the new, unified Status app in two secure ways:
Requirements:
• Update your Status Legacy 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:
Requirements:
• Update your Status Legacy 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:
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.
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.



