Re: [w3c/manifest] Ability to dynamically change app icon (#663)

@marcoscaceres well, in earlier internet gifs were allowed, and we've seen such a similar thing you've shared, on the internet, where gifs were abused. But it's all about how people will use instruments, and about the community, not about limitations. Look, here, on github, gifs are allowed. And it's quite beatufil, - I may see this good feedback you've shared. I, personally, use gif recordings to better indicate some bugs while developing my apps, and make issues with these recordings.

So I think it should not be a limitation, for PWA, to dynamically change app icon. The topic isn't about a constant circular animations like it's (mostly) in your gif. It's more about some logic.

Look at your image again. Notice a little humble calendar app?

<p align="center"><img width="105" alt="image" src="https://user-images.githubusercontent.com/13215662/66946111-b32fd700-f069-11e9-97cb-eeb08a5dc514.png"></p>

It does change icon dynamically, every day. But still, - it's pretty much static.

For some sort of apps, like calendar, it may be quite useful, to be able to change their icon, to place some very limited but useful data. For calendar, - it's the number of the day. For some other apps it may be just some binary output, which depends on something complex. So it's not about animation but it's about very limited data output.

"some binary output, which depends on something" - that's exactly my case. That's how I've gotten here. I was thinking about some similar logic to the calendar app. And was wondering if PWA may let me do this. I don't really want getting into native development just for this little thing. But it could be quite nice to have such an ability for PWA, then I would probably turn my little pet web app into PWA.

In order to prevent obusing it should be probably being able to setting up. Like notifications for app. Same with dynamic icon change (which will be mostly useless because I believe people won't abuse it now, it's not 2005).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/663#issuecomment-542832641