Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Mobile: show the channel description in the channel header and empty state

Open Beginner friendly
#8,268 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
83/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
mobile

Research direction

Start with channel_detail_page.dart around lines 574–575 and 603, then inspect channel_detail_page/message_list.dart around line 688 to see how the header and empty state are built. Check how channel descriptions are currently displayed in channel_details_page.dart and run the relevant mobile tests. Done when a set description appears in both requested places, while the header falls back to member count when no description is set.

Written by the indexing model from the issue text.

Description

We run a Buzz community with non-technical guests, and on the phone they can't tell what a channel is for.

Today (Android 0.20.0, tag mobile-v0.20.0-rc.1):

  • The channel header subtitle is the member count (channel_detail_page.dart:574-575, used at :603).
  • An empty channel says only "No messages yet" (channel_detail_page/message_list.dart:688).
  • The description is shown only after tapping the channel name, on Channel details (channel_details_page.dart:658, maxLines: 3 at :702), and in Browse channels for channels you haven't joined.

So the one field an owner writes to explain a channel is hidden at the moments a guest needs it.

Proposal

  • Use the description as the header subtitle when it is set, and fall back to the member count when it isn't.
  • Show the description on the empty-channel screen, above "No messages yet".

Desktop already uses the description in its channel intro, so this would bring the phone in line with it. Happy to open a PR if this direction works for you.

Dominant language
Rust
Stars
36.2k
Forks
4.8k
Avg merge
1d 13h
Merged PRs (30d)
270

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from block/buzz

All issues in block/buzz

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.