I would like the Snooze/Dismiss screen to fill the screen with multiple, custom snooze times.

[CataCluj]

I would like the Snooze/Dismiss screen to fill the screen with multiple, custom snooze times.

[yuriykulikov]

Hey @CataCluj, I would appreciate if you would fill in the form above :)

Please consider Android guidelines here: https://developer.android.com/develop/ui/views/notifications/time-sensitive#kotlin

And this article is also quite good: https://medium.com/android-news/full-screen-intent-notifications-android-85ea2f5b5dc1#:~:text=Full%2DScreen%20Intents%20are%20Intents,call%20or%20a%20ringing%20alarm.

As far as I understand, the only way to show a full-screen popup when the phone is unlocked is to use https://developer.android.com/reference/android/Manifest.permission#SYSTEM_ALERT_WINDOW

Alternative

Third button in com.better.alarm.background.NotificationsPlugin

This needs an additional Intent (like other two buttons), which triggers code much like in com.better.alarm.alert.AlarmAlertFullScreen#showSnoozePicker

[CataCluj]

Thank you. I had filled the form but between the comments'... delimiters. Shows how much I know.
I will try to go through those links but I may have to do a kotlin/android dev course before I can make sense of them.
I'll try to understand the proposed alternative.
Thanks again.
Are you still working on this?

[CataCluj]

From the first link you sent I see the (or part of the) problem: "The system UI may choose to display a heads-up notification, instead of launching your full-screen intent".
I do hope that a full-screen intent could be launched from some button on this heads-up notification? Is that what you proposed (in other words) above? I'm still learning and, even the "lingo".

[CataCluj]

In the second link it seems there are three different scenarios that may need to be addressed:
-Notify while the app is on the foreground
-Schedule Full-Screen Intent Notification
-Full-Screen Intent on Lock Screen with a Keyguard
What is not quite clear to me is if I have to address all these three scenarios separately (what a pain!) or might one be the grand-daddy that covers them all (and the others may exist because the grand-daddy may be too much if only the "lesser" needs need meeting).

[CataCluj]

About the "SYSTEM_ALERT_WINDOW", I feel like it would be justified for an alarm app and feels much less shifty then permissions to connect to internet, access to files, sensors, and others that many apps ask for even if not needed.
I don't think I would mind, as a user, granting such permission to an alarm app.
Thanks again.

[yuriykulikov]

Thank you. I had filled the form but between the comments'... delimiters. Shows how much I know. I will try to go through those links but I may have to do a kotlin/android dev course before I can make sense of them. I'll try to understand the proposed alternative. Thanks again. Are you still working on this?

Hey, I have missed your comment. Yes, I am working on this on occasion. Not very active, I have to admit.