I think the settings could be simplified down to a single toggle.
There are two settings now: keep running after window closes, and run on startup. I'm not convinced having these two separate settings solves any use case.
For instance: what's the use case for keeping the app running in the background, but not launch it again on startup? And what's the use case for not running it in background, but then launching it when the computer restarts?
I think people are only interested in "is the app active or not", meaning both of these can be tied to the same toggle called something like "enabled". Either the app is enabled, meaning it changes the wallpaper based on light/dark mode in the background and across reboots, or it's not enabled, meaning it does nothing and does not run in the background.
Here are some benefits I see with this approach:
- It's simpler to understand.
- The settings popover can be replaced with the toggle, simplifying the interface.
- When this toggle is off the rest of the app can be "greyed out" or similar to indicate that "none of this stuff will actually do anything".
I think the settings could be simplified down to a single toggle.
There are two settings now: keep running after window closes, and run on startup. I'm not convinced having these two separate settings solves any use case.
For instance: what's the use case for keeping the app running in the background, but not launch it again on startup? And what's the use case for not running it in background, but then launching it when the computer restarts?
I think people are only interested in "is the app active or not", meaning both of these can be tied to the same toggle called something like "enabled". Either the app is enabled, meaning it changes the wallpaper based on light/dark mode in the background and across reboots, or it's not enabled, meaning it does nothing and does not run in the background.
Here are some benefits I see with this approach: