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

Mobile: after joining by invite, make "Continue to #welcome-everyone" the primary action

Open Beginner friendly
#8,269 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
82/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
dart, flutter, rust
Domain
design, mobile

Research direction

Start with invite_join_sheet.dart:216-238, which contains the warning and both actions. Make “Continue to #welcome-everyone” the primary action, keep backup secondary with a line explaining it needs Buzz on a computer, and soften the warning with guidance for later. Done when the invited channel is the primary action and the updated copy matches the proposal.

Written by the indexing model from the issue text.

Description

Today (tag mobile-v0.20.0-rc.1), after someone joins a community from an invite link:

  • The filled primary button is "Back it up now" (invite_join_sheet.dart:222-232), under the warning "This phone is the only copy of this identity…" (:216).
  • "Continue to #welcome-everyone" is the secondary text button (:235-238).
  • "Back it up now" opens the scan-from-desktop flow.

A guest with no desktop app is pushed toward a step they can't complete, and away from the channel they were invited to.

Proposal

  • Make "Continue to #welcome-everyone" the primary action.
  • Keep backup as a secondary action, with one line saying it needs Buzz on a computer.
  • Keep the warning, but soften it to say what to do later.

Small and copy-level. We're glad to send a PR.

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.