You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see from the screenshots below, when I received notification for the apps I locked in my device, content is hidden from lockscreen and notification panel. I need to open the app first to see the content. But for Niagara's (homescreen and alphabet app drawer), the content is visible in Notification Preview.
My main concern with this is for scenarios like when I lend my device to someone. I'm at ease that they can't access those locked apps. But NOT when those apps receive notifications while they're using my phone. The notification's content isn't visible in notification panel, but they can still see it from my home screen or alphabet app drawer because Niagara's Notification preview is showing it.
SOLUTION DESCRIPTION
Description: Additional settings in Notification preview where I can select apps to hide the content. Apps selected will still be able to receive notifications and can be accessed in Notification preview (like how it normally functions) — but the content is hidden.
I don't need app locking feature, the device's native security settings will take care of that. What I need is: Hidden content for apps selected in Notification preview settings.
Something like, "Content hidden. Open app to view". Or just leave it blank.
Thanks for reaching out. Could you please elaborate on your systems app locking feature and what it does?
The notification content hidden on the lock screen and the notification shade when the device is locked is an Android feature and makes sense since the user has not authenticated themselves at that point. However, once unlocked the notifications are visible once the device is unlocked.
Is there a way to lock apps so that their notifications do not show their contents in the notification shade when the device is unlocked?
Is there a way to lock apps so that their notifications do not show their contents in the notification shade when the device is unlocked?
Hi! The app locking feature hides the content on lock screen AND notification shade, yes.
It locks specific apps. Even if I unlock the lockscreen, the content still won't show up in notification shade —unless I open the app (which I need to individually unlock first). Meaning there's kind of two layers of security: one for lockscreen, another for individual apps.
That's why my suggestion is a feature for Niagara's Notification Preview if it's possible to select specific apps to hide only their content (not entirely the notification themselves) It's similar to app locking I think but simpler(?).
As you can see from the screenshots below, when I received notification for the apps I locked in my device, content is hidden from lockscreen and notification panel. I need to open the app first to see the content. But for Niagara's (homescreen and alphabet app drawer), the content is visible in Notification Preview.
My main concern with this is for scenarios like when I lend my device to someone. I'm at ease that they can't access those locked apps. But NOT when those apps receive notifications while they're using my phone. The notification's content isn't visible in notification panel, but they can still see it from my home screen or alphabet app drawer because Niagara's Notification preview is showing it.
SOLUTION DESCRIPTION
Description: Additional settings in Notification preview where I can select apps to hide the content. Apps selected will still be able to receive notifications and can be accessed in Notification preview (like how it normally functions) — but the content is hidden.
I don't need app locking feature, the device's native security settings will take care of that.
What I need is: Hidden content for apps selected in Notification preview settings.
Something like, "Content hidden. Open app to view". Or just leave it blank.
Feature Request Procedure
The text was updated successfully, but these errors were encountered: