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

Add Android notification permission and system-settings controls

Open
#110 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android
Domain
mobile-dev

Research direction

Start with the Android settings UI and the contract from #107, after checking prerequisites #79 and #81. Exercise the permission flows with a local notification fixture, then verify settings navigation, status refresh on return, English/Korean labels, accessible text, and non-blocking allowed, denied, and dismissed outcomes.

Written by the indexing model from the issue text.

Description

android difficulty: beginner enhancement good first issue help wanted notifications

Roadmap: #76

Goal

Give users a clear way to allow notifications and revisit the system setting.

Acceptance criteria

  • Request notification permission from an explicit user action when required by the supported Android version.
  • Handle allowed, denied, and dismissed outcomes without blocking the app.
  • Link to the app's notification settings and refresh displayed status when returning.
  • Provide English/Korean labels and accessible status text.
  • Test each permission outcome with a local notification fixture; provider access is not required.

Start: The Android settings UI and the contract from #107.

Reference: Android notification permission.

Prerequisites: #79, #81, #107.

Dominant language
Go
Stars
1
Forks
7
Avg merge
1h 45m
Merged PRs (30d)
16

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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 wavefnd/wave-platform

All issues in wavefnd/wave-platform

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.