Screenshot Database during the "Devolutions Era"

[SiriosDev (SiriosDev)]

What is the new way to contribute to the screenshot database?

[Marc-André Moreau (mamoreau-devolutions)]

For the short term, make a pull request to add the app icons and screenshots directly to the json file: https://github.com/Devolutions/UniGetUI/blob/main/WebBasedData/screenshot-database-v2.json

The original Excel file from Google docs has been imported, and the json file has been cleaned up. I do have a couple of ideas on how to significantly increase coverage for the app icons, but it's going to take some time.

[SiriosDev (SiriosDev)]

Thanks, if I may suggest, a system similar to home-assistant/brands is very easy to use, community collaboration side

[Marc-André Moreau (mamoreau-devolutions)]

That's a good reference for structure, I want to build something similar, with a Devolutions CDN to host the images instead of relying on hundreds of links to files of inconsistent sizes.

I noticed that winget now has an option to extract app icons locally to display in the terminal: https://www.edtittel.com/blog/icons-make-their-winterm-debut.html

I looked at the winget-cli code and already have a few app icon extraction scripts in place, now I'm working on trying to automate extraction at scale with GitHub Actions workflows that would install packages, extract the icons and collect as many as possible automatically to populate a large database.

I was originally thinking that I could build an app icon service that UniGetUI would call with optional app icon extraction to feed the database, but if I can fetch a large portion of them in GitHub Actions, I think I can have something decent faster that would be much easier to deploy with a static site instead.

The part that I don't think is easily automatable are the application screenshots, and I don't know how much users want them as opposed to app icons.

My ideal solution would automate icon extraction to the maximum possible, such that there would be a lot less manual entries to add and maintain in the database.