The great thing about the new multi-layer icon format in Golden Gate is that it finally separates an icon's foreground from the background.
So in theory, it opens the door to returning shape-differentiated icons to MacOS if a future display theme (a successor to the poorly-conceived Clear and Tinted themes) allows the background to be minimized while the foreground is emphasized.
What I would love to see, and should now be possible, is a revision of the Clear theme where the squircle is transparent/refractive and the foreground retains its native color.
Hard agree! Not only is it less fun and less visually appealing to me, I think forcing the uniform squircle everywhere makes it harder (than it used to be) to distinguish one app from another by icon alone.
Apple CEOs always seem to want to make a splash via hardware (especially since the guy worked in hardware engineering) but it would be nice if an engineer brings more focus on the software as well.
I agree, but I'm surprised there was no mention of contrast or proposal to restrict colors.
Their first good example bumped up the color contrast. The orange examples in their set of "gorgeous app icons" are just as bad as the slack vs photos example.
I would love if the OS had an option to automatically convert every app icon to greyscale and required a minimum color contrast ratio for the original. Then, the user can pick their own overlay colors (similar to the color tags in finder).
Someone with 5000 hours design experience needs to make a common icon theme for a few 100 GTK and QT libraries and standard-names. It feels like it's 1000s of hours of work. And then you have to make them available in a few formats, HDPI, maybe a build system, etc. there are a number of themes but the ones I try seem to be missing one or more of the icons from the set. Just need the right volunteers to build them, and also get a bunch of app-builders to adopt them, and figure out what colour the bike-shed should be (blue).
Why volunteer? Why not find a way to pay someone for the value of their time at market rate and release the product of their labor under a permissive license?
As a bit of a shameless plug, I did some in the past[0] and am working sporadically on a "fork" of those[1] but it's a whole full-time work. There are hundreds of icons to do for apps alone. Each one needs to be done in 16x16, 22x22, 32x32, 64x64, 128x128 and 256x256 so if say you have 150 icons to do for apps, you actually will need to do 900 icons. And add to that that you'll need to cover categories, places, filetypes, actions...
Granted, you can do a 256x256 and scale it down to 128x128, for example, but if you care for quality some details will be lost anyway. So that's why nowadays you'll see most icon themes are just a bunch of logos plastered over a shaped background.
And what irked me the most was that a few weeks after that I released that first set via deviantart and opendesktop.org there were websites that included them in their sets and made them available for download in their websites, not even a redirect to my deviantart or opendesktop pages or something. And found out after that that some people were using them in commercial projects and stuff so I had to chase them asking to not use them since they were cc-by-nc'ed.
Never got a single cent of any of that. I love making icons, at some point I was even working for the icons that would eventually become the Breeze set for KDE5 with their VDG, but it happens that I also need money to buy the beans.
I think illustration isn't something too much in the mindshare of open source, so overall support for it isn't great. IMO this has contributed to it. The industry standard tools are all closed, with closed formats, so it just sounds like much more of a hassle vs contributing code/text.
I mean this throughout the whole process. The only standard illustration file format I can think of is SVG, but it's largely a format to export to, not one industry-standard software uses as it's main persistence format.
So for starters, contributors tend to need access to speciality software they probably don't have installed to view and edit the source of truth. This also means you're handling at least two files in your VCS, the closed format acting effectively as a blob, no diffs, etc. and an export file (usually more, for different scales) to actually interface with the rest of the ecosystem; this is the file everyone can open, inspect and compare, the one your build consumes, etc.
This already would be a good amount of friction for someone familiar with the tools, but designers are not necessarily familiar with git, the PR process, etc. Add to it that icons are more subjective than code, which overall should follow certain rules and either works or doesn't, and it overall seems not worth it for a casual contributor.
The great thing about the new multi-layer icon format in Golden Gate is that it finally separates an icon's foreground from the background.
So in theory, it opens the door to returning shape-differentiated icons to MacOS if a future display theme (a successor to the poorly-conceived Clear and Tinted themes) allows the background to be minimized while the foreground is emphasized.
What I would love to see, and should now be possible, is a revision of the Clear theme where the squircle is transparent/refractive and the foreground retains its native color.
Hard agree! Not only is it less fun and less visually appealing to me, I think forcing the uniform squircle everywhere makes it harder (than it used to be) to distinguish one app from another by icon alone.
In fact the HIG used to explicitly say so with clear examples proving it.
Tahoe was such a huge mess, but I'm hopeful that the new CEO will turn things around and bring things back to normal.
If they do, I'll consider upgrading both OS and laptop, but right now I'm holding on to Sequoia
They have a new head designer too IIRC, but probably is going to take some time for him to slowly move away from the mess he inherited.
It really was Mac OS X's Vista moment.
Edit: It'll always be Mac OS X to me, not macOS.
Golden Gate is better but it hasn't fixed your icons unfortunately
Apple CEOs always seem to want to make a splash via hardware (especially since the guy worked in hardware engineering) but it would be nice if an engineer brings more focus on the software as well.
I think this is a battle they won't win, though I applaud the effort.
I agree, but I'm surprised there was no mention of contrast or proposal to restrict colors.
Their first good example bumped up the color contrast. The orange examples in their set of "gorgeous app icons" are just as bad as the slack vs photos example.
I would love if the OS had an option to automatically convert every app icon to greyscale and required a minimum color contrast ratio for the original. Then, the user can pick their own overlay colors (similar to the color tags in finder).
It might be better to make Linux have these gorgeous icons now that Apple locked them up.
Make the icons be Free on Free OSes like Linux.
What's been keeping Linux from having gorgeous icons up to this point?
Someone with 5000 hours design experience needs to make a common icon theme for a few 100 GTK and QT libraries and standard-names. It feels like it's 1000s of hours of work. And then you have to make them available in a few formats, HDPI, maybe a build system, etc. there are a number of themes but the ones I try seem to be missing one or more of the icons from the set. Just need the right volunteers to build them, and also get a bunch of app-builders to adopt them, and figure out what colour the bike-shed should be (blue).
Why volunteer? Why not find a way to pay someone for the value of their time at market rate and release the product of their labor under a permissive license?
Yeah what if these open source developers just got jobs and then they paid someone to do what they used to do for free?
Yeah, it’s amazing what you can accomplish when you find a way to pay people a livable wage for the things you want.
As a bit of a shameless plug, I did some in the past[0] and am working sporadically on a "fork" of those[1] but it's a whole full-time work. There are hundreds of icons to do for apps alone. Each one needs to be done in 16x16, 22x22, 32x32, 64x64, 128x128 and 256x256 so if say you have 150 icons to do for apps, you actually will need to do 900 icons. And add to that that you'll need to cover categories, places, filetypes, actions...
Granted, you can do a 256x256 and scale it down to 128x128, for example, but if you care for quality some details will be lost anyway. So that's why nowadays you'll see most icon themes are just a bunch of logos plastered over a shaped background.
And what irked me the most was that a few weeks after that I released that first set via deviantart and opendesktop.org there were websites that included them in their sets and made them available for download in their websites, not even a redirect to my deviantart or opendesktop pages or something. And found out after that that some people were using them in commercial projects and stuff so I had to chase them asking to not use them since they were cc-by-nc'ed.
Never got a single cent of any of that. I love making icons, at some point I was even working for the icons that would eventually become the Breeze set for KDE5 with their VDG, but it happens that I also need money to buy the beans.
[0] https://miler.codeberg.page/?prj=rekt
[1] https://miler.codeberg.page/?prj=betelgeuse
I think illustration isn't something too much in the mindshare of open source, so overall support for it isn't great. IMO this has contributed to it. The industry standard tools are all closed, with closed formats, so it just sounds like much more of a hassle vs contributing code/text.
I mean this throughout the whole process. The only standard illustration file format I can think of is SVG, but it's largely a format to export to, not one industry-standard software uses as it's main persistence format.
So for starters, contributors tend to need access to speciality software they probably don't have installed to view and edit the source of truth. This also means you're handling at least two files in your VCS, the closed format acting effectively as a blob, no diffs, etc. and an export file (usually more, for different scales) to actually interface with the rest of the ecosystem; this is the file everyone can open, inspect and compare, the one your build consumes, etc.
This already would be a good amount of friction for someone familiar with the tools, but designers are not necessarily familiar with git, the PR process, etc. Add to it that icons are more subjective than code, which overall should follow certain rules and either works or doesn't, and it overall seems not worth it for a casual contributor.
It'll take just a few prompts to customize all your icons the way you like.
They have other, arguably more important, yaks to shave.
a question as old as Linux itself