-
Notifications
You must be signed in to change notification settings - Fork 629
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
App Icon in Store is too small #473
Comments
I used the built-in asset generator that is included with Visual Studio, and this is what it came up with. Since this was generated by VS, I believe this is the correct size. I'm not opposed to having someone update the assets, but it's not a high pri for me. |
@stmoy I also think it looks too small compared to the other fluent icons, especially in the Start Menu. I can create an updated assets folder with larger icons. |
@stmoy do you have a file of the icon on its own (preferably vector) that I could use for this? |
The SVG and PNG are here: https://1drv.ms/u/s!Aj55ujyRgozspBu7H_OiEiA6YHx9?e=gjpBLr |
Assets.zip |
@Spyromaniac31 Would you like to create a PR with the updated images? 😃 |
All done. Sorry about all the commits. I'm new to GitHub and forgot to link the title in the commit message at first. |
* Resized tile assets to match standard icon size * Resized tile assets to match standard icon size (#473) * Resized tile assets to match standard icon size (#473) * Resized tile assets to match standard icon size (#473) * Resized tile assets to match standard icon size (#473) * Resized tile assets to match standard icon size (#473) * Resized tile assets to match standard icon size (#473) Co-authored-by: HenryPontzer <fluenthenry@gmail.com>
The app icon displayed for the app in the Store looks too small. It is a small icon in a large blue tile. It would look better if the icon was a similar size as the tile.
This is true both in the Store app and on the site.
https://www.microsoft.com/en-us/p/xaml-controls-gallery/9msvh128x2zt?activetab=pivot:overviewtab
The text was updated successfully, but these errors were encountered: