Automattic / Automattic/pocket-casts-android
[Notification Permission Request] - Handle scenarios that don't have screen for users to interact
- Dominant language
- Kotlin
- Stars
- 2.8k
- Forks
- 308
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 197
Description
This issue is to decide how to approach the notification permission request for the cases we don't have a screen for the user to interact. Currently we are requesting notification permission on the first screen, but we are trying to request it when is actual necessary. See for more context: https://github.com/Automattic/pocket-casts-android/issues/2698
For example: Playback errors, Fix Download Complete, etc
For the case of Fix Download Complete we have a place for the user to interact, but I am not sure if it makes to request user's notification permission for fixing downloads just because this button also triggers a notification.
Contributor guide
Research direction
Start by reading the linked issue #2698 and reviewing how notification permission is currently requested on the first screen. Consider the playback-error and Fix Download Complete examples described here, including whether the latter's interactive button justifies permission. Done means the project has a decided approach for cases without an interaction screen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100