[Bug]: confusing Notification Switch in conversation datails page

Open Beginner friendly
  • Is something wrong?
#421 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
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
design, mobile

Research direction

Start in the conversation details screen and find the existing notification switch and “Customize notification” row; the issue does not name a file or test. Read how those controls currently enable custom settings and open Android’s conversation notification settings. Done when one “Customize notifications” row uses the switch to enable or disable custom settings and opens Android settings from its label only when enabled.

Written by the indexing model from the issue text.

Description

bug

Thank you for moving notification management to Android itself latest beta! It's much cleaner and less confusing now.
I noticed one small UX inconsistency in the conversation details tab.
There's currently a switch simply labeled "Notification", which is Off by default. However, notifications are still enabled and working normally when it's off. Turning it on actually creates a separate notification category for that conversation in Android's system settings.
I think this could be confusing because users might assume that turning it off disables notifications entirely.

Instead of having a separate "Notification" switch and a "Customize notification" option underneath, why not combine them into a single row labeled "Customize notifications", with a switch?

  • When off: Tapping the switch enables custom notification settings for this conversation. Tapping the label itself does nothing.
  • When on: Tapping the label opens the conversation's notification settings in Android. The switch can still be used to turn off custom notification settings.

This would combine both actions into one clean and intuitive UI element, while keeping the current functionality.

Dominant language
Kotlin
Stars
44
Forks
5
Avg merge
14h 58m
Merged PRs (30d)
65

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 an1ndra/Messages

All issues in an1ndra/Messages

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.