Open ako256 opened 1 month ago
Only foreground applications are allowed to be used.
This should answer your question. I've been experiencing a few issues with this limitation for my own app. Glyphs keep staying on when the app is closed to run in the background. When the app is then closed from the background state the glyphs wont turn off anymore. Users either have to fully restart their phone or restart the app to properly close it directly afterwards.
So for your app: Users must always keep their phone unlocked and your app running in the foreground. Otherwise you wont be able to trigger the glyph interface.
So for your app: Users must always keep their phone unlocked and your app running in the foreground. Otherwise you wont be able to trigger the glyph interface.
Wow, how did this get released as an actual api like what use case would someone even implement this for. They should make it so that apps can get permission to control glyphs from background processes as well.
I was trying to make an app that would 'parse' progress notifications and show it on glyphs. I guess my idea is dead before even starting.
Thanks for the reply btw!
You're welcome.
And yes I am totally on your side.
You can still create your app and hope that Nothing will add support for background calls in the future. I guess this is probably the main reason why we don't see so many published apps using the glyph interface.
Eh I think I'll pass for now, I need a working project for my resume and such a limited project would probably be laughed at by recruiters lol
Hopefully nothing opens up this api completely. Users are not dumb, they can decide which apps they'd like on the glyphs.
This api key system is only hurting them in the long run as glyphs current don't have a good ecosystem.
Hello, I am planning to make a music player app that will show the song progress on the charging glyph (! one) and I want to know if a background (or foreground) process can show glyphs. Thanks in advance!