Persistent settings
12/24-hour modes, optional seconds, scale, opacity and theme choices persist through a native Rainmeter settings panel rather than source-file editing.
05 · Focused project · Shipped · Rainmeter + Web
A small desktop utility I wanted for my own Windows setup that became an exercise in finishing a focused tool properly: restrained architecture, persistent settings, measurable performance, validation and release packaging.
The design choice
The desktop version only needs local time, text rendering and a small settings surface. Rainmeter already provides those capabilities, so embedding a browser runtime or desktop framework would add memory use and complexity without improving the core job.
The project therefore ships as a native Rainmeter skin with no plugins or network measures. A separate dependency-free HTML/CSS/JavaScript implementation demonstrates the same visual idea in the browser without making the web runtime a dependency of the desktop clock.
Measured performance
Three 45-second scenarios were sampled on the same Windows development machine: Rainmeter baseline, MinimalClock with seconds hidden, and MinimalClock with seconds visible.
Engineering surface
12/24-hour modes, optional seconds, scale, opacity and theme choices persist through a native Rainmeter settings panel rather than source-file editing.
Repeatable PowerShell tooling measures CPU and memory overhead against a Rainmeter baseline instead of relying on subjective “feels lightweight” claims.
Windows GitHub Actions validates project structure and browser JavaScript, while the native release is packaged through Rainmeter's Skin Packager.
No Electron, Node runtime, embedded WebView, background service or unnecessary network dependency is added to a utility whose job is simply to show time well.
Shipped utility
The point of MinimalClock is not complexity. It shows that even a one-purpose desktop tool can be finished with measurable non-functional requirements and a clean technical boundary.