-
-
Notifications
You must be signed in to change notification settings - Fork 323
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
Inclusion of "Launcher hidden" entries for Apps with Icon Pack support #1873
Comments
Can you give an example of an app like that? Web apps are allowed if someone makes it, but they're disabled in the request function because of their unique IDs |
Well given that I ignored the reason most of them don't show up in a launcher...I didn't quite think through the 'how to bind' them with at least the default Android Icon. As for why even bother -> consistency and small surprises for current and future users. The consequences of it actually working would obviously be quite a bit of crowd sourcing to cover OEM specific stuff. I might just be dreaming too much though. Edit: Package without activities -> search for 'packagename/custom.icon' instead While it could probably be done without 'custom.icon' by simply linking 0 activities to the default Android icon, plenty of system and user apps actually come with custom/different icons and/or activities. (like de.dlyt.yanndroid.notinotes) Maybe @kaanelloed knows if that's something current/standard implementations would allow by adding a few more lines of code or if there's something else I'm not thinking about. |
I've never really looked at web apps icons, but from what I understand, I don't think any launcher has implemented a way to apply icon packs with web apps. |
As I seem to remember a discussion/removal of Icons linked to WebApps (unless I picked that up somewhere else...) I thought about actually asking before I start something big that won't make it.
What are your thoughts on including entries that won't show up in a Launcher but get picked up by Apps with Icon Pack support ?
The text was updated successfully, but these errors were encountered: