Status-react: Update list of public chats

[jinhojang6]

_Acceptance criteria added 31/10/19. Issue ready for pick-up._ [RH]

Background

Status suggests a list of featured(selected) public chats as below. It will be the first screen for newcomers who want to hang out with existing Status communities.

Problem

1. Some languages with a number of speakers (e.g. French, German, Portuguese) don't have their own community channels on the suggested list.

2. The list of featured public chats are not categorized and localized.

3. Some popular topics such as sports, business, politics, or travel could be easier for the general public to engage in the communities but the featured topics don't include them.

Acceptance Criteria

For v1, update the hardcoded chat list:

• #introductions
• #chitchat
• #status
• #status-[device language if applicable]
• #crypto
• #tech
• #music
• #movies
• #support

Display an alternate #status-language channel only if the user has a device language set to Chinese, Japanese, Korean, Russian, Spanish, or Farsi.

Future Suggestions

The list of featured public chats could be categorized and include more general topics such as

General

• Introductions
• Politics
• Economy
• Business
• Travel
• Entertainment
• Sports
• World News
• Music
• Water cooler
• more general topics..

Languages

• English
• Spanish
• Portuguese
• German
• French
  
  
  
  • Italian
  
  
• Dutch
• Russian
• Chinese
• Korean
• Japanese
• Farsi
• other major languages..

Developers

• blockchain
• ethereum
• Web
• AI
• VR/AR
• frontend
• backend
• devops
• dapps
• cryptolife
• etc..

Status

• status
• status-core
• status-core-ui
• status-embark
• status-keycard
• status-nimbus
• status-marketing
• other Status public chats...

Design explorations

Considering the mass adoption after V1 and better user experience, Status has to provide users with more public chats in a more organized and comprehensive manner.

[rachelhamlin]

People often ask what other channels are active within #status. I think it's a great idea to set up and encourage use of additional spaces that are _not_ about crypto or our own product. After all, we want people to use Status day-to-day and to talk about things that matter to them.

The community's favorite subreddits might be a good input for this list.

@errorists what do you think about adding category headers to the selected dapps list? Yea or nay? Are there any future ideas for this screen that I'm unaware of?

[errorists]

@rachelhamlin Don’t you guys think it’s too early for that? Those will be dead chats with no activity, without the kind of UX in place yet necessary to facilitate meaningful interaction, especially compared to all of the other places available on the web to discuss things. There’s nothing more sad than scrolling an endless list of channels, decide on the one that interests you only to find it empty. But then again it's a bit chicken and egg problem, right? We can try and do that and see how's the activity like in those channels?

What I’d suggest instead is to surface 10-15 most active chats, since those will be the ones our audience is most interested in. Ideally these should be picked and updated dynamically rather than a hardcoded list. This list shouldn’t include Status channels other than general imo.

As for the design, I’m working on a format that’s more welcoming and easier to understand you’re not really creating chats but rather choosing to listen to a particular hashtag others broadcast on. It's WIP since I actually wanted to base it on some feedback coming from V1

[rachelhamlin]

@hesterbruikman @errorists I'm just reading the conversation in #core about this that I missed yesterday. I'm under the impression that we can measure activity in a certain Whisper topic/chat, and thus there is some room for imagination here. See Andrea's comment here: https://github.com/status-im/infra-misc/issues/26#issuecomment-540490325

Another means to make chat more active would be to load the latest N number of messages, rather than last 24 hours.

Here's a spreadsheet where we can capture ideas related to our make chat more enjoyable to use objective. And one also for fixing significant blockers, and polishing UI.

[errorists]

Here's what I'm thinking for the design

Ideally, I'd like to have a shorter list for now, if we can make propagate it with channels based on recent activity that's great. Otherwise hardcode it with a list of channels we think would have the most activity.

I'd park the full list of every channel we can think of for later, when there's actual activity going on, traffic numbers are up and we can reasonably say these won't sit empty.

[jinhojang6]

@errorists I do like the design, personally

[rasom]

@rachelhamlin @errorists did we make our choice on design and the way how this task should be implemented? It is marked as p0 task on board but it's a bit unclear from the conversation how to proceed.

[errorists]

☝️ good point. @rachelhamlin maybe let's park this for after v1 and then implement the list ordered by activity with suggestions from @yenda on how to that. I can't speak on effort required. We're in the process of adding the much improved chat empty state with recommended channels to join so this imo is less critical for v1?
As for design, I have no intention of changing it from what's shown above, as far as I can tell it's ready to be picked up.

[rachelhamlin]

Yeah, sorry @rasom, I wasn't expecting someone to tackle this yet - it's not ready to be picked up.

For v1, we don't need to implement any new designs. I was more curious for @errorists' opinion on how we could improve.

I'll get back on this today. As I recall - people have typically been a bit confused about the prompt to create/join a new public channel. We have the chance to steer activity as we launch, so I think we should populate the hardcoded list with a more diverse mix of options.

[errorists]

As I recall - people have typically been a bit confused about the prompt to create/join a new public channel.

Almost everyone, me included, thinks that the input to enter your public chat name is actually a search box :) It's a combination of its placement, styling and the list below. That's where this new design comes in

[rachelhamlin]

So for a quick improvement here, what if we:

Reduce the number of #Status-[language] channels. We could show only the alt Status channel that matches the language of the user's device.

Additionally make the list a little more interesting, and match the new welcome screen:

• #introductions
• #chitchat
• #status
• #status-[device language if applicable]
• #crypto
• #tech
• #music
• #movies

Goal is simply to encourage conversation + community in topics other than crypto :)

@j-zerah are you happy to use #status as the catch-all channel for new user questions? If I recall correctly, that's the idea. We'll be in there, too.

Curious for your opinions @errorists @rasom @jinhojang6 @rbnpercy

[j-zerah]

This looks ok to me.

status - seems a bit vague and I wouldn't necessarily know what is expected in that channel as a newcomer. It does imply that the Status team should be there which is good so im cool with it. The only other thing we could call it is #support

Also - often times we get questions from developers asking where they can get in touch with our dev team for questions and support. Does this #status channel make sense for them as well? Maybe #status-devs.

IMO we need to account for three journeys:

• Someone who wants to introduce themselves and exploring fun channels (#introductions, #chitchat, #music, etc)
• Someone who needs help getting set up and has questions about the product (#status? #status-device language)
• A developer who has technical questions and needs to contact someone from our team (?)

[rachelhamlin]

#status - seems a bit vague and I wouldn't necessarily know what is expected in that channel as a newcomer.

Agreed. I like the idea of a #support channel, as that's much more clearcut.

The purpose of #status is even more vague in that case. Today it's effectively our small talk or chitchat channel. I like giving people a dedicated space to talk about the project though.

I would actually suggest we allow developers to ask technical questions in #support or #status as well. One less channel for our team to monitor, and developer questions are on-topic for the project...

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

__This issue now has a funding of 60.0 DAI (60.0 USD @ $1.0/DAI) attached to it.__

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
  
  
  
  • Want to chip in? Add your own contribution here.
  
  
  • Questions? Checkout Gitcoin Help or the Gitcoin Slack
  
  
  • $125,006.24 more funded OSS Work available on the Gitcoin Issue Explorer
  
  

[flexsurfer]

@rachelhamlin @errorists any final decision how we want to implement this for v1?

[errorists]

@flexsurfer Yes, please follow this design for now Figma

to recap, it's a hardcoded list, no dedicated categories subview just yet

[flexsurfer]

thanks, @rachelhamlin do we have a list we want for v1 ?

[rachelhamlin]

@flexsurfer definitely want the list of public chats updated, so if you want to implement this new screen as well, be my guest. :) Please make sure to remove all the alternate languages and display only the one relevant to user's device (if not in English).

[flexsurfer]

| English | Russian | Deutsch |
| ------------- | ------------- | ------------- |
| | | |

[errorists]

nice, I like that contextual language chat!

[gitcoinbot]

Issue Status: 1. Open 2. Cancelled

---

__Workers have applied to start work__.

These users each claimed they can complete the work by 6 months, 1 week ago.
Please review their action plans below:

1) ihabhamed has applied to start work _(Funders only: approve worker | reject worker)_.

hello,
Arabic is not included in the list but if you want to add it I'm available here
2) akanimorex has applied to start work _(Funders only: approve worker | reject worker)_.

i can use reactJs to do this.It will update the list on each load
3) guardiangreenie has applied to start work _(Funders only: approve worker | reject worker)_.

Provide critical feedback along with any bugs.
4) wubswurld has applied to start work _(Funders only: approve worker | reject worker)_.

I can complete your task and other tasks you have posted in a timely manner

Learn more on the Gitcoin Issue Details page.

[gitcoinbot]

Issue Status: 1. Open 2. Cancelled

---

__The funding of 60.0 SAI (60.0 USD @ $1.0/SAI) attached to this issue has been cancelled by the bounty submitter__

• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $136,120.14 more funded OSS Work available on the Gitcoin Issue Explorer