Roadmap Planning

Core team:

Please use this post to put forward your thoughts on features, bugs, tech debt or chores that we should prioritize post-v1 release.

We’ll discuss items synchronously during our planning meeting next week, on the 15th.

Reminders, for context:

  • An overview of the current v1 backlog is here.
  • As our differentiating feature, chat will receive most emphasis.
  • Our goal is to ramp up user traction after v1. We’ll use unique Peer IDs as a proxy for active users. (TK: public dash, retention curves)
  • Another longer-term goal is to be sharding ready.

Many issues related to chat are already logged and labeled ‘chat’ or ‘group-chat’ in status-react.

Let me know if you have any questions. I’ll determine the agenda for our planning call based on the response this post receives.

cc @andrey @maciej @hester @yenda @vitaliy @cammellos @pedro @adam @Tetiana @sergii

1 Like

Cool beans! Here’s my chat themed list, very roughly prioritised from the top

:framed_picture: Images GithubFigma

Group%2041


:speaking_head: Mentions GitHubFigma

Group%202


:white_check_mark: A proper Mark as read / unread counter. GitHub

Group%2042

:raised_hands: Message reactions /w SNT reactions GitHubFramer prototype

Group%2043


:bell: Introduce a dedicated Notifications view, in-app notifications Figma

Group%2048


:pencil2: Editing messages Figma

Group%2046


:artificial_satellite: Forwarding messages Figma

Group%2044


:tipping_hand_man: Friend-to-friend content discovery Discuss


:memo: Saving messages you compose as ‘Drafts’ GitHub

Group%2050


:nail_care: Revisit the UI for creating a new Private, Public chat


:speech_balloon: Update the message styling Figma

Group%2051


:man_artist: Redesign the Commands CLI to a GUI Figma

Group%2054


:lipstick: Update the group chat system messages, maybe personalise their copy similar to Discuss for added sass. Figma

Group%2053


:family_man_girl_boy: Update the Group Chat profiles Figma


:see_no_evil: Update unread badge counters to increase the cap from one digit to three


:horse_racing: Animate sending messages GitHub


:musical_note: Add more sounds to chat?


:right_anger_bubble: Improvements to code formatting, inline quotes?


:boom: Self destructing private messages, are these possible at all with the current protocol?


also

Tribute to Talk?:skull_and_crossbones:

11 Likes

Some additions to these awesome features by @maciej, especially regarding onboarding users.

  • Improve on the profile sharing experience and inviting friends. The current web2 accessible page is ok, not great and can be expanded. As a non-Status user, having the first intro be the Whisper ID can be intimidating. Would also be great to have a ‘find me on Status’ signifier aka twitter handle or WeChat ID.
  • Next to that I’m hopeful there’s a way to pass on more invite information post-download to easily connect to the person who sent you the invite.

Related to this:

  • Contact requests that could also trigger a push notification. It’s too easy to miss new people starting a chat as notifications rely on being in one’s trusted contact list. Afaik.
  • Account ‘gifting’ something like sending a contact request with a key, locking a gift in an escrow and only an account that has access to the key sent in the contact request can release the funds.
  • Any investigation into managing multiple chains and identities. Basically what would a window in window based navigation could connect to and if there are opportunities for a gradual transition in the current navigation.

Ideally we also include a ‘buffer feature’ to manage strong requests emerging from user feedback post V1 release.

4 Likes

Heya, great stuff @maciej. Looking forward to SNT message reactions in particular :zap:
Here are some of my thoughts on what should be added and improved.

Better send transaction flow

Video: https://www.dropbox.com/s/xkvzosem08u085w/address.mov?dl=0

1

WIP in Figma https://www.figma.com/file/XUehMnhyD1FGcWzvGz6SXqvh/Mobile-wallet?node-id=3158%3A32526

Better transaction overview

2

Figma https://www.figma.com/file/XUehMnhyD1FGcWzvGz6SXqvh/Mobile-wallet?node-id=3869%3A36442

Better settings

3

Figma https://www.figma.com/file/bPS9GrvMr7LnH7vnkmuveQfd/Settings?node-id=576%3A0

Simple account switching

3

Better seed phrase backup and confirmation

Video: https://www.dropbox.com/s/tpqc1sihu8xjdny/backup.mov?dl=0

4

Simple transaction signing for smaller amounts of SNT/ETH
To enable great features like SNT message reactions and other powerful SNT utility use-cases we have to make it really easy to send up to ~100SNT.

Fix navigation issues
Sometimes right edge-swipe does not do the same thing as tapping on “<” which leads to bad UX not matter how good the featureas are made. Github: https://github.com/status-im/status-react/issues/8940
Here’s one more nav issue: Tap on “inner” screen icon to go back to the “main” screen or scroll to top Github: https://github.com/status-im/status-react/issues/8885

7 Likes

+1! Configuring account contracts. Thanks for adding that one @andmironov🙏

1 Like

Thanks so much for the thoughtful replies, @maciej @hester and @andmironov.

Here’s what’s on my mind in terms of broad objectives, with a few points to illustrate. I’d like to:

Make chat more friendly and engaging

Onboard new users warmly

  • Consider the user’s first experience of Status: diversify the public chat selection & build community within, funnel users into a welcome chat, etc. (can prob update for v1)
  • Revive chat commands for grassroots SNT distribution (possibly also v1)
  • Pull last N number of messages for public chats, rather than last 24 hours, so that chats are more likely to be populated

Bring chat to life, make it enjoyable :man_dancing:

  • Image sending
  • Notifications overhaul
  • Mentions
  • In a parallel universe with one more UI engineer…more picks from @maciej’s list :purple_heart:

Communicate effectively how Status works and what makes it unique

  • Full copy review
  • More opportunities for education within the app (education or FAQ chat? links to web copy? info tooltips? onboarding video?)

Remove blocks & barriers

Bandaid for bandwidth

  • Research into resource consumption & bandwidth—how violently averse will people be, what’s the source of the problem, how can we fix it for now?

Fix annoying UI

  • Check into syncing UI, esp on low connectivity
  • Control the sequence of pop-ups and warnings, e.g. mobile network syncing, notifications settings, etc., so they don’t feel so assaulting
  • Review fetching messages behavior
  • General UI clean up

Make user feedback collection a habit :raising_hand_woman:

  • Monitor usage via whisper analytics + install data
  • App store reviews
  • Quick & dirty observational studies for UI
  • Revive voting DApp for feature polling?

Improve development process through better test coverage

Set community developers up for success (and ourselves for sanity) with docs

  • Use RFCs
  • Map logic
  • Diagram architecture
  • Continue with code documentation

Prepare for future tech changes: multichain readiness, Nimbus


On a slightly longer timeline, I’d like to…

Help users build community within Status

  • Similar to @hester’s suggestion of gifting accounts…perhaps we create a set of Status-specific NFTs. You can gift one to a friend outside the app, and they redeem it on account creation. We could literally illustrate keys or tokens, something that communicates our uniqueness and says “you’re joining the privacy revolution.” Ricardo has some ideas about how to do this on our terms.

Improve identity

  • Universal login
  • Profile privacy controls

Clean up loose ends, “complete” existing features

  • Fixes to group chat
  • Additional account types for multiaccount - import watch only, import from seed, etc.

Make chat even greater

  • Creator side of sticker marketplace
  • Anti-spam/Tribute to Talk

Review EIP implementations


On an even longer timeline: gas abstraction, privacy enhancements (multi-chat, send via mixer, burner wallet for each DApp, etc.), Keycard POS integration, extensions revival, etc.

There’s so much more that I’m not mentioning, but user feedback will help us to determine what’s important.

Above all, I’d like to select the smallest and most manageable chunks of work from the top of our list, ship quickly, and collect feedback constantly. :slight_smile:

3 Likes

Oh, and another thing I love is SNT reactions—that’s another great way to grassroots spread the distribution of SNT and welcome people in. Would like to better understand the work involved (thank you Andrei for including the simple transaction signing item).

1 Like

Fyi: Enigma is looking for wallets to integrate their mixer ‘Salad’. Could be an option to include it with limited effort. Does anyone have thoughts on whether close to what we’d need?

1 Like

my top 5 list

edited: bonus 0) Redesign the Commands CLI to a GUI Figma and Better send transaction flow WIP in Figma

  1. passwordless accounts, using pincode or biometric for signing transactions
  2. signing small (max amount is set in the settings) transaction without authentication
  3. import/create keycard account into multiaccount
  4. import accounts using seed, json file
  5. separate accounts for dapps tabs
2 Likes

I agree mostly with @maciej, especially because we will be launching v1 soon, I think we should focus on things that matter most for the users, and I have a feel that images, mentions (to a much lesser extent code highlighting, but I am biased), will be fairly important for user acquisition and retention, so I’d like them to see prioritized (likely post v1 I suppose)

2 Likes
  1. Performance:
    Performance=UX. Vital for retention of users.
  1. Basic onboarding
    Get people into public chats with a warm welcome asap
  • can be high touch
  • get people to add contacts as soon as possible (vital for retention, see various IM/social network studies)
  1. Measure active users and retention curves
  • Set as weekly growth goal, feedback into 2 and outside-app experience
    • make it crystal clear and failable, i.e. this week we made usage go up or not
  • then fix bottlenecks based on specific user feedback
  • high touch, talk to users and isolate number 1 or 2 prio
    • bounty everything non-essential, i.e. not prio 1 or 2 from user feedback
    • aim for short feedback cycles
2 Likes

It sounds like we have a good amount of alignment in here.

Warm, friendly welcome via smooth onboarding. Better, more engaging chat experience. Reduction of significant blockers like bandwidth consumption. These are some themes I’m hearing across many of these posts.

Additionally: polish specific UI elements, build on privacy as our main feature with increased settings and control, more robust account management…

And measurement/strong feedback mechanisms are a must in my book. Luckily I can shoulder much of that with relatively little dev time.

I’ll surface these objectives in the call later today. Thanks team! :pray:

1 Like

Hi, maybe I’m off topic, but there is a function that I like very much and very convenient: the setting to automatically delete messages in chat rooms 1: 1, for example, after 1 day, 3 days, 14 days and never delete. If possible, please add this feature.

4 Likes

Welcome @bumerang007!

1 Like

The roadmap planning session is up on YouTube.

On the call, we discussed goals for the application after launch and went over potential objectives for the near future, which I extracted from this Discuss thread.

We spent some time discussing our personal drivers and blockers to using Status. This surfaced several more potential objectives, which we added to the list.

We then dot voted, as a group, on which objectives should receive the most focus after launch. Each core contributor was given 3 votes to allocate. 1 point = 1 vote from a contributor.

We’re now inviting other SNT holders and community members to give us their feedback on the objectives ranked by contributors on the call.

Give us a :+1:or :-1:to let us know how you feel about this order of priorities for v1.

1 - Make chat more enjoyable to use. This is about implementing standard chat features, such as image sending, notifications, or @ mentions. (11 points)

2 - Fix significant blockers to use. This requires us to improve on issues like network consumption, battery drainage, etc., as well aggravating UI issues. (5 points)

2 - Polish the UI. This is about improving UI responsiveness, as well as polishing specific features, e.g. seedphrase recovery. (5 points)

3 - Enable smoother transactions. This is about improving the Tx flow to be more in line with Andrei’s post, and could also apply to Tx history improvements. (4 points)

4 - Offer more robust account management. Completing multiaccount features such as ability to import from seed phrase. (3 points)

5 - Make it easier to build community in Status. Account gifting, easier profile sharing, etc. (3 points)

6 - Enhance user privacy through advanced controls. Ability to switch DApps per browser tab, etc. (2 points)

7 - Better desktop support. (2 points)

8 - Welcome new users warmly with smooth onboarding. (1 point)

9 - Build SNT utility. (1 point—worth mentioning that features laddering up to the above objectives can do this)

10 - Bring in additional functionality via extensions. (1 point)

11 - Make uniquness of Status understood. (0 points)

12 - Faster, more iterative release process. (0 points)

Given our team’s bandwidth, we will focus in on the top 3 objectives for now: make chat enjoyable to use, reduce significant blockers to use, and polish UI.

We’ll follow up with in-depth planning sessions to discuss the features & fixes that will drive these objectives in the next few weeks.

If you have specific features or improvements in mind that you would like to see considered, drop us a line!

6 Likes

:+1:

V1 is an incredible achievement all around. Messages send, transactions are secure, and browsing is simple.

To me, the most important next step, is obtaining basic feature parity with other messaging applications to make a genuine case for people to switch over to Status. Therefore, the top three items listed above seem like the logical order of priorities.

6 Likes

Very much agreed on point one! Though re notifications, which provider would you use? I heard in the Town Hall that you might skip PNs for v1

1 Like

I like this from a privacy point of view. Having your phone searched at airports and having ALL your data be scraped is decidedly sub-optimal. Maybe a nuke all button too?

2 Likes

Welcome to discuss.status.im @alexcg1!

2 Likes

Hello everyone. :wave:t3: The core team’s votes are in for order of priority in what to ship after v1.

The top 5 items to make chat more enjoyable are:

  1. @ mentions
  2. Images in chat
  3. Awesome push notifications for Android
  4. A proper mark as read feature w/ unread message counter
  5. Make Status a share target from other apps, e.g. web browser

For fixing significant blockers to use, our focus is in:

  1. Optimizing battery consumption
  2. Reducing network data consumption
  3. Improving wallet fetching Tx history
  4. UI performance, specifically on older Android devices, which can be laggy

We’re now in the process of working on written specs for each item above and welcome any feedback.

My wish is for the team to define the simplest MVP version of each feature, ship, and then iterate based on user feedback—before branching out to more new features.

I’d like for us to balance our time between these new features, and critical bugs/blockers (which will always take precedent). On Tuesday of next week, @Tetiana @sergii @andre and I will be discussing our post v1 release cadence and how often we’ll intend to ship.

7 Likes