-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Direct access to Play Store from favorites? #835
Comments
An alternate option would be showing an option in search to open the Play Store: #145 |
That's an interesting idea although personally, I don't have the search enabled on my Home screen so it wouldn't be a huge benefit in my case. It's not hard (and this is what I do currently) just to add the Play Store into my Favorites list in the same way as any other app, but it feels like Store & Settings warrant their own Niagara-controlled options/entries in Favorites rather than take up a regular app slot. |
I personally would use both of these suggestions (or let users select in settings). |
To better plan ahead and to give users an estimate which features will be added to Niagara, I’ve decided to close all feature requests that that are unlikely to be implemented in the next year (2020). This is one of those, unfortunately. I'm sorry. Feel free to open this ticket again in 2021 or later. |
Is your feature request related to a problem? Please describe.
Having switched to Niagara from Smart Launcher the one thing, the only thing, I miss is having convenient access to the Play Store without having to search out the Play Store app.
Describe the solution you'd like
At the foot of the favorites list we currently have a hardcoded & very useful entry for Settings. In a similar way could we have a Play Store option beneath settings? It could be optional in Niagara Settings to enable / disable Play Store.
Its sole purpose would be to act as a shortcut to the Play Store app. Icon could be a shopping basket perhaps?
Niagara is an excellent product - congratulations and thanks!
The text was updated successfully, but these errors were encountered: