ItвЂ™s basically a watch task for macOS, with a UI to set up all the stuff you want it to do. I didnвЂ™t go down that road, though, becauseвЂ¦ Enter HazelДЄ number of recommendations from folks turned me onto Hazel. Like putting the command into `~/.bash_profile` or something. I bet there is some trickery to avoid that. This wouldnвЂ™t be much different.Д®xceptвЂ¦ that weвЂ™d need to gulp watch (or whatever) from the command line every time we restarted. A lot of us probably already do this with the web projects we work on. Then if an image file appears there, run an image optimization task. One way to approach this would be to set up a Grunt/Gulp/Webpack/Whatever watch task to watch the Desktop. What if we didnвЂ™t need to optimize images because any image that was on the Desktop was automatically optimized? ThatвЂ™s what weвЂ™re shooting for here. Making any image on the Desktop automatically optimized The Desktop is a convenient place, for me, for all that to happen. Perhaps itвЂ™s a screenshot that needs to get resized, then optimized, then uploaded somewhere, then deleted. Images are one of the most common things that end up there. I do whatever IвЂ™m doing with them, then move them away.

Things IвЂ™m actively using go on the Desktop. Monotonous repetitive tasks are fertile ground for computerization, so letвЂ™s computerize it. If weвЂ™re taught one thing about images and the web, itвЂ™s that they should be optimized.ДЇor me, that means dragging every single image onto ImageOptim before using it. I work with images as part of blog posts, images as part of sites IвЂ™m working on, images headed to social mediaвЂ¦ images everywhere. IвЂ™m forever trying to make my local image workflow easier.

Imageoptim grunt