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
Hi, new Pro user here, and I love the simplicity of Niagra, and my top reason for using it is the speed of access to everything like search, widgets, calendar, weather and so much more.
One thing i enabled right away was the quick-lock. I noticed how Niagra actually scrolls down in the Apps List when i lock the screen using quick-lock. This makes logical sense, but when I unlock my screen the next time, I would prefer so much more to see my Favourites again, instead of ending up in a random point in my Apps List.
Describe the solution you'd like
I see 2 possible solutions, both of which resolve my issue:
When the screen is locked using the quick-lock, the next time I unlock my phone, Niagra should return to the default Favourites view, by default.
An option to set my preference to not "Remember position in Apps List after locking screen"
Hi @DetourToNirvana, Thanks for reaching out! If you lock your phone via double tapping the alphabet scroller and unlock the phone immediately (< 3 seconds), Niagara Launcher returns you to the last position (app list) instead of the main home screen. This is intentional and saves you time if you accidentally locked the phone.
Is your feature request related to a problem?
Hi, new Pro user here, and I love the simplicity of Niagra, and my top reason for using it is the speed of access to everything like search, widgets, calendar, weather and so much more.
One thing i enabled right away was the quick-lock. I noticed how Niagra actually scrolls down in the Apps List when i lock the screen using quick-lock. This makes logical sense, but when I unlock my screen the next time, I would prefer so much more to see my Favourites again, instead of ending up in a random point in my Apps List.
Describe the solution you'd like
I see 2 possible solutions, both of which resolve my issue:
Feature Request Procedure
The text was updated successfully, but these errors were encountered: