docs(roadmap): tentative roadmap for Q1 of 2026 #19540
Conversation
jrainville
requested review from
a team,
alaibe,
glitchminer,
osmaczko,
sunleos and
vkjr
and removed request for
a team
Jenkins Builds
|
✔️ status-desktop/e2e/prs-windowsPR19540 🔹 ~24 min 🔹 30089b1 🔹 📦 tests/e2e-windows package |
jrainville
left a comment
jrainville
left a comment
There was a problem hiding this comment.
One thing we talked about in the Release Process meeting is defining Key Features marking the cut of the release.
I think we should mark those with a star (⭐ ) in the roadmap so that it's clear to everyone that once those features are done, we will cut the release and anything not done should be pushed to the next release. Since every new feature should be behind a feature flag, it shouldn't affect anything.
In this case, I would propose the following features as Key Features:
- Mobile feature parity
- Mobile Dapp browser
- Privacy Mode
What do you guys think?
There was a problem hiding this comment.
Thanks a lot @jrainville for this update. I’ve left a few comments and suggestions.
docs/roadmap.md
Outdated
| - [Memory and Performance improvements](https://github.com/status-im/status-desktop/issues/18296) | ||
| - No provided FURPS at the moment as this is mostly about profiling and fixing issues found. | ||
| - In Progress ⏳ 🟩🟩🟩⬜⬜ 64% | ||
| - [Improve Token List and Support custom tokens](https://github.com/status-im/status-desktop/issues/19517) |
There was a problem hiding this comment.
It might be a good idea to run some testing across the following areas, as they could reveal additional tasks for this epic:
- Permissions
- Mint
- Airdrop
- Profile Showcase / Collectibles
- Join Community, Share Addresses and Community Requirements Check flows
- Manage Token Settings
There was a problem hiding this comment.
Yes, the Epic linked is actually the known bugs and things to fix related to the feature. I don't think it's worth listing all of those here, but we should for sure test all of those as part of it before releasing!
|
jrainville
left a comment
jrainville
left a comment
There was a problem hiding this comment.
Thanks for the review @noeliaSD !
Regarding the Mobile Feature Parity section, we currently list five independent features under this epic. Would it make sense to prioritise them individually? Some of these features may be more relevant or impactful than others.
My own opinion is that they are all necessary for the Mobile app to behave at lest as good at the old app, so I'd like to have them all in 2.38.
I'll still list them all in a bullet list under it so it's easier to follow. Let's see what the team and community think, ie can some of them be de-scoped?
docs/roadmap.md
Outdated
| - [Memory and Performance improvements](https://github.com/status-im/status-desktop/issues/18296) | ||
| - No provided FURPS at the moment as this is mostly about profiling and fixing issues found. | ||
| - In Progress ⏳ 🟩🟩🟩⬜⬜ 64% | ||
| - [Improve Token List and Support custom tokens](https://github.com/status-im/status-desktop/issues/19517) |
There was a problem hiding this comment.
Yes, the Epic linked is actually the known bugs and things to fix related to the feature. I don't think it's worth listing all of those here, but we should for sure test all of those as part of it before releasing!
jrainville
force-pushed
the
docs/q1-roadmap
branch
from
95f20b4 to
b98f027
Compare
Jenkins BuildsClick to see older builds (48)
|
I hope you meant 2026 and not a decade later :) |
Oops good catch. Edited. I think I got in the habit of writing |
jrainville
force-pushed
the
docs/q1-roadmap
branch
from
b98f027 to
4fb8e95
Compare
|
I pushed a new commit splitting the roadmap in mutliple files, per half year. I also updated the progress and marked the Key Features |
There was a problem hiding this comment.
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:
- Use Nimble instead of
nimbus-build-system
Annoying long-standing issues
- Banners — there're too many of them, and they're jumping all around
- Make sure biometrics work for all operations - [MilestoneEpic] Re-vamp
KeycardPopup#17404
Small but nice features:
- Logout (without closing the app) — supported by backend, was supported by legacy mobile.
- Delete account — supported by backend, was supported by legacy mobile.
- Integrate Sentry on Nim side to get crash reports
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:
- Communities
- Improve owner experience. Provide ways and docs on running a Control Node.
- Channels Threads (perhaps makes sense to finish Chat SDK integration first)
- Disposable chats — chats that use ephemeral keys and don't preserve history
- Multisigs — create multisig wallets, e.g. within group chats. Use Status/Waku to sign transactions off-chain and then publish all signatures together on-chain.
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 fancier 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.
|
|
||
| ## 2026 H1 | ||
|
|
||
| ### 2.38 |
There was a problem hiding this comment.
I feel like 2.38 is overloaded, I doubt we can do that much 🤔
| - File sending over Codex | ||
| - Dependant on Codex being available in Light mode for mobile and having a C library |
There was a problem hiding this comment.
We will try get Community Archive on Codex in 2.38
docs/roadmap/2026-H1.md
Outdated
| - [UI modularization](https://github.com/status-im/status-app/issues/17872) | ||
| - [FURPS](/docs/FURPS/ui-modularization.md) | ||
| - In Progress ⏳ 🟩⬜⬜⬜⬜ 27% | ||
| - Keycard Shell Integration |
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.
Also, I believe it is important to get this done before IFT All Hands.
There was a problem hiding this comment.
We're focusing on at least having full support for Keycard on Mobile. If we have time, for sure it would be nice to fit Keycard Shell in 2.38 as well 👍
5 participants
Description
Here is the tentative Status App for Q1 of 2026
@sunleos , @alaibe and I met to discuss the features everyone in the team put in the brainstorming document and prioritized them. We only got up to the 2.38 features, but that's enough to give an idea of the start of the year.
The rest of 2.39 will be added later.
This PR is open to comments from everyone, feel free to recommend what to prioritize, if we missed anything, etc.