docs(roadmap): tentative roadmap for Q1 of 2026 #19540
+102
−38
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,80 @@ | ||
| # Status Roadmap | ||
|
|
||
| ## Table of Contents | ||
| - [Status Roadmap](#status-roadmap) | ||
| - [Table of Contents](#table-of-contents) | ||
| - [2026 H1](#2026-h1) | ||
| - [2.38](#238) | ||
| - [Features](#features) | ||
| - [2.39](#239) | ||
| - [Features](#features-1) | ||
|
|
||
| ## 2026 H1 | ||
|
|
||
| ### 2.38 | ||
|
Contributor
There was a problem hiding this comment. I feel like 2.38 is overloaded, I doubt we can do that much 🤔 |
||
|
|
||
| Release Epic: https://github.com/status-im/status-app/issues/19509 | ||
|
|
||
| Estimated release: Early February | ||
|
|
||
| #### Features | ||
|
|
||
| - ⭐ [Mobile feature parity](https://github.com/status-im/status-app/issues/19530) | ||
| - In Progress ⏳ 🟨⬜⬜⬜⬜ 19% | ||
| - Includes: | ||
| - [Keycard support](https://github.com/status-im/status-app/issues/19531): In Progress ⏳ 🟩🟩🟨⬜⬜ 50% | ||
| - [Push Notifications](https://github.com/status-im/status-app/issues/19532): In Progress ⏳ 🟩⬜⬜⬜⬜ 25% | ||
| - [Deep Links Support](https://github.com/status-im/status-app/issues/19533): In Progress ⏳ 🟩⬜⬜⬜⬜ 25% | ||
| - [QR Code scanning](https://github.com/status-im/status-app/issues/19534) | ||
| - [UI Zoom setting](https://github.com/status-im/status-app/issues/18265) | ||
| - ⭐ [Mobile Dapp Browser](https://github.com/status-im/status-app/issues/19535) | ||
| - In Progress ⏳ | ||
| - ⭐ Polish [Desktop Dapp Browser](https://github.com/status-im/status-app/issues/19246) | ||
| - [FURPS](/docs/FURPS/dapp-browser.md) | ||
| - In Progress ⏳ 🟩🟩🟩🟨⬜ 71% | ||
| - ⭐ [Privacy mode](https://github.com/status-im/status-app/issues/17619) | ||
| - [FURPS](/docs/FURPS/privacy-mode.md) | ||
| - In Progress ⏳ 🟩🟩🟩🟩🟨 90% | ||
| - [Improve Token List and Support custom tokens](https://github.com/status-im/status-app/issues/19517) | ||
| - In Progress ⏳ | ||
| - Merged. Testing and fixing is in progress | ||
| - [Chat Input Field UX Improvements](https://github.com/status-im/status-app/issues/19524) | ||
| - [Activity Center revamp](https://github.com/status-im/status-app/issues/18516) | ||
| - In Progress ⏳ 🟩🟨⬜⬜⬜ 33% | ||
| - [Unified Adaptive Navigation System](https://github.com/status-im/status-app/issues/19458) | ||
| - [Standardized approach for Popups / Menus / Dropdowns](https://github.com/status-im/status-app/issues/19493) | ||
| - [Color System Revamp](https://github.com/status-im/status-app/issues/19455) - Improved Dark Mode & Updated Palettes | ||
| - [Nimbus Verification Proxy](https://github.com/status-im/status-app/issues/19538) | ||
| - [Memory and Performance improvements](https://github.com/status-im/status-app/issues/18296) | ||
| - No provided FURPS at the moment as this is mostly about profiling and fixing issues found. | ||
| - In Progress ⏳ 🟩🟩🟩⬜⬜ 64% | ||
| - [Private Transactions POC](https://github.com/status-im/status-app/issues/19539) | ||
| - [Backend refactor](https://github.com/status-im/status-go/issues/6435) | ||
| - Runs parallel to other features and doesn't need to be shipped to any particular milestones | ||
| - No API changes are expected until the Chat SDK is integrated | ||
| - [Roadmap, Documentation and FURPS](https://zealous-polka-dc7.notion.site/Backend-Refactoring-2078f96fb65c80d8954ae8fc651b3a33) | ||
| - In Progress ⏳ 🟩🟩🟨⬜⬜ 54% (estimated progress as not all subtasks are created) | ||
|
|
||
| ### 2.39 | ||
|
|
||
| Release Epic: https://github.com/status-im/status-app/issues/19529 | ||
|
|
||
| Estimated release: Mid March | ||
|
|
||
| #### Features | ||
|
|
||
| - [Full SDS integration](https://github.com/logos-messaging/pm/issues/194) | ||
| - Enabling of the SDS wrapping feature flag | ||
| - Breaking change for people in 2.36 or lower (first supported release is 2.37) | ||
| - News Feed on Waku | ||
| - File sending over Codex | ||
| - Dependant on Codex being available in Light mode for mobile and having a C library | ||
|
Comment on lines
+70
to
+71
Contributor
There was a problem hiding this comment. We will try get Community Archive on Codex in 2.38 |
||
| - [UI modularization](https://github.com/status-im/status-app/issues/17872) | ||
| - [FURPS](/docs/FURPS/ui-modularization.md) | ||
| - In Progress ⏳ 🟩⬜⬜⬜⬜ 27% | ||
| - Keycard Shell Integration | ||
|
Contributor
There was a problem hiding this comment. I would rather prioritize Keycard Shell integration for 2.38. I know it conflicts with my comment, but still — it's our own product, we should be the first in line to fully support it. IMO it is more important than any UI/UX improvements and Private transactions POC. |
||
| - Private Transactions | ||
| - Follow-up of [Private Transactions POC](https://github.com/status-im/status-app/issues/19539) | ||
| - Enabling of the feature flag | ||
| - [Ethereum Follow Protocol](https://github.com/status-im/status-app/issues/18685) | ||
| - In Progress ⏳ 🟨⬜⬜⬜⬜ 10% | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| # Roadmap | ||
|
|
||
| In this folder, you can find the roadmap files for the Status App. | ||
|
|
||
| - [First half of 2026 (H1)](2026-H1.md) | ||
| - [Second half of 2025 (H2)](2025-H2.md) | ||
|
|
||
| Epics marked with a star (⭐) are **Key** Features for the milestone, meaning that the milestone is considered Done when those Epics are Done, initiating the Release Process. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll to leave some of my thoughts/ideas here. They don't have to go to 2.38, and some not even in 2026 H2.
But I'd love to see us doing this kind of stuff.
Sharing in the order smaller -> bigger.
Ideas highlights
Developer experience:
nimbus-build-systemAnnoying long-standing issues
KeycardPopup#17404Small but nice features:
Reincarnate existing features:
Embedded privacy-preserving updates notifications
There is
services/updatesservice in backend. I'm not fully sure how it works, but it usesdesktop.stateofus.ethENS name to retrieve a URL, and then the version is fetched from this URL using an HTTP client.Using HTTP here is not super privacy-preserving, but still good enough. We could use it, or maybe implement a simple smart contract that Status App would read.
ENS — ensure full support.
Getting and releasing, binding existing ENS names, monitoring expire date.
Maybe add more features like syncing gravatar, bio and other profile info.
Big features:
Long-term vision
I believe that Status is not just a messenger or a wallet. But it's a synergy of both.
There will always be many fancy wallets. But none of them have messenger. And the opposite.
Therefore, the focus should be on features utilizing both, like Token-gated communities and Multisigs. These are the features that we should develop. And any tasks to ensure we have a reliable foundation to deliver new features quickly.