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
custom icon #9
Comments
See also: bromite/bromite#120 (comment) Contains a link to https://opensourcedesign.net/jobs |
I ended up using an icon recolor for the time being: https://github.com/GrapheneOS/chromium_patches/blob/pie/0020-Vanadium-branding-for-GrapheneOS.patch I auto-converted the existing branding to a dark grayscale variant as I did previously. I still do want a custom icon, but I see some benefit in having it based on the Chromium logo to some extent since most people are familiar with that and can tell it's a browser from the icon, consciously or subconsciously. It's probably not ever going to be a standalone project from GrapheneOS, so it doesn't really need distinctive branding itself. It may make sense to make it more different from Chromium than just a recolor though. I do have some progress on branding for GrapheneOS itself. I uploaded 3 PNGs generated from the initial set of vector graphics below (there are other assorted options to choose from too). I haven't entirely decided on the highlight color and I'll be making the theme in the OS and Chromium match this too once that's decided. I'd like to have the site match too. Currently planning on mostly sticking to matching the Material Light theme, but there are some colors that need to be chosen, likely from the Material color palette to match other things in the OS and apps. Also currently using the Roboto font for branding and the site for consistency, and a nice thing about that is it's very tied to AOSP. Google uses it for AOSP documentation, blog posts, etc. but mostly not for anything else tied to Google. They even replaced it in their own apps and on Pixels for titles, headers, etc. with Google Sans. |
No description provided.
The text was updated successfully, but these errors were encountered: