Apps you see. Systems behind them.

Useful software.
A personal touch.

Independent apps, useful dashboards and thoughtful automation. A closer look at the projects I build and the problems they solve.

03Apps
06Systems
09Total projects
Independent projects by Clucky7
Pi Status / monitoring
A real monitoring interface. Private details are hidden. Actual interface · privacy reviewed
CluckyLensContext behind the headlines
Compression pipelineQueue · encode · validate
Actual interface capturesMade for real use
Desktop & AndroidWeb experiencesObservabilityAutomationResilience

01 / The projects

More than a
good-looking screen.

The problem, the purpose, and the details
that make each project useful.

Open a project to see the purpose, technical detail and more images. Animation controls affect every illustration on this page.

Showing all 9 projects and systems.

02 / Beneath the surface

The quieter systems
doing the heavy lifting.

The things that help the main experience stay safe, recoverable and easy to use.

06 / Supporting systemInfrastructure & engineering

Media Integrity & Recovery

The safety layer that asks whether a completed file is actually safe to keep.

Explore the build Purpose, engineering & screenshots
How it worksAnimated explanation
01Inspect
02Check integrity
03Pass or retain
04Recover

Illustrated sequence · no live connection or performance figures

Project details Purpose · engineering · screenshots · animated walkthrough

Why it exists

An encoder exiting successfully does not establish that a long media file is complete, that its streams survived, or that a copied candidate is the exact file that was checked.

The build

What makes it work.

Validation and recovery tools sit around the compression workflow. They compare identity, duration and stream structure, perform bounded decode checks on the Windows PC, and verify staged content before replacement.

  • Several checks, different failure modes. A readable header, a plausible duration and a clean decode answer different questions. The workflow combines checks rather than treating one success signal as sufficient.
  • Know which file passed. Hashes connect the validated candidate to the staged and installed copies. A mismatched or ambiguous file is held for review.
  • Recover the checkpoint. Retained completed candidates can be reconsidered through validation and guarded replacement. Recovery does not blindly trust an old output or silently overwrite a conflicting stage.
  • Protect the original during change. The replacement path keeps an original available during verification. Its later retention follows the production batch policy; this is not an indefinite backup promise.

What it achieves

Built for the everyday.

A supporting safety system, not a separate consumer app or a guarantee of perceptual losslessness. Historical incident analysis informed its checks; no universal quality score is asserted.

Descriptions reflect documented source and release evidence. Illustrations explain behaviour; they do not show live measurements.
How it worksAnimated explanation
01Inspect
02Check integrity
03Pass or retain
04Recover

Illustrated sequence · no live connection or performance figures

07 / Supporting systemInfrastructure & engineering

Signed Updates & Installers

The part of an app people meet before launch and every time it improves.

Explore the build Purpose, engineering & screenshots
The real Windows installer during a 0.2.19 upgrade test. Actual interface · privacy reviewed
Project details Purpose · engineering · screenshots · animated walkthrough

Why it exists

A download button is only the beginning. People also need to understand what changed, see progress, verify the update and retain a working path when installation fails.

The build

What makes it work.

Branded Windows installers and matching in-app update screens combine grouped release notes, version checks, verified metadata and download integrity checks. Android hands installation to the operating system.

  • Readable release notes. Short New, Improved and Fixed groups explain the user-facing change without exposing implementation details.
  • Verify before running. Signed update metadata and a file hash are checked before installation. CluckyLens binds its product, platform and version into the signed offer.
  • Keep the choice visible. Update now and Later, progress views and clear failure messages make the process understandable without forcing an immediate install.
  • Shared style, separate identity. Apps reuse the same presentation language while keeping their own icon, app identity and signing continuity.

What it achieves

Built for the everyday.

A shared delivery pattern used by the released applications. Signed update metadata is not the same as a Windows publisher certificate, and the draft should not imply the installers have one.

Descriptions reflect documented source and release evidence. Illustrations explain behaviour; they do not show live measurements.
How it worksAnimated explanation
01Read release
02Verify signature
03Check file
04Confirm install

Illustrated sequence · no live connection or performance figures

08 / Supporting systemInfrastructure & engineering

Backup & Recovery Automation

Protecting the small pieces of work that are easy to overlook and difficult to recreate.

Explore the build Purpose, engineering & screenshots
How it worksAnimated explanation
01Inspect
02Check integrity
03Pass or retain
04Recover

Illustrated sequence · no live connection or performance figures

Project details Purpose · engineering · screenshots · animated walkthrough

Why it exists

Source control cannot preserve every local working detail, and a backup is hard to trust if an incomplete archive looks finished or a failed run disappears quietly.

The build

What makes it work.

A focused PC-only backup path streams selected irreplaceable data to an encrypted archive on the server. Verification precedes promotion, while bounded logs and failure reporting make the job observable.

  • Focused rather than indiscriminate. The source script selects local-only working data and undo copies while excluding regenerable caches and large transient directories.
  • Stream instead of staging plaintext. The PC sends the archive stream to the protected destination without writing an intermediate plaintext archive on its own disk.
  • Finish only after checking. The destination writes a partial encrypted archive, checks that it can be decrypted and read, then promotes the completed artifact and records a checksum.
  • Visible failures and bounded history. Connection keepalives, explicit exit checks, retained logs and a retention policy help distinguish a healthy backup from a stalled or failed attempt.

What it achieves

Built for the everyday.

A source-verified backup design with separate monitoring of recent success. This portfolio does not claim an independent/offsite backup, current restore drill, or full disaster-recovery guarantee.

Descriptions reflect documented source and release evidence. Illustrations explain behaviour; they do not show live measurements.
How it worksAnimated explanation
01Inspect
02Check integrity
03Pass or retain
04Recover

Illustrated sequence · no live connection or performance figures

09 / Supporting systemInfrastructure & engineering

Web Delivery & Offline Handling

A web client that considers stale assets, interrupted connections and how an update reaches the reader.

Explore the build Purpose, engineering & screenshots
How it worksAnimated explanation
01Load online
02Cache shell
03Network drops
04Offline fallback

Illustrated sequence · no live connection or performance figures

Project details Purpose · engineering · screenshots · animated walkthrough

Why it exists

An installed-looking web experience can still fail on a weak connection or keep serving old code. Caching needs boundaries as well as a fast path.

The build

What makes it work.

A versioned service worker caches content-hashed static assets, keeps changing application data on the network and provides an offline navigation fallback. An update-ready view gives the user a deliberate reload path.

  • Cache the right things. Hashed static files can be cached; fresh navigation and changing API/configuration responses are treated differently.
  • Make disconnection understandable. A dedicated offline page explains the failed navigation instead of leaving the user with a blank screen.
  • A visible update handover. The app can check for a new release when it returns to the foreground and offer an update-ready reload.
  • Keep rollback practical. Versioned caches and a network-loaded entry page help prevent the frontend from being trapped on an obsolete release.

What it achieves

Built for the everyday.

A delivery component of CluckyMedia, not another standalone app. The earlier in-app Install app prompt was deliberately removed; do not present it as a current feature.

Descriptions reflect documented source and release evidence. Illustrations explain behaviour; they do not show live measurements.
How it worksAnimated explanation
01Load online
02Cache shell
03Network drops
04Offline fallback

Illustrated sequence · no live connection or performance figures

03 / A connected approach

The pieces
work together.

Individual projects solve specific problems. Monitoring, automation and interfaces serve different needs. This map groups the ideas behind the work; each project has its own role.

CluckyWorksUseful software.
A personal touch.
Read & discover
Watch & enjoy
See & understand
Automate & protect
Conceptual relationship map · not infrastructure topology

04 / Also in the workshop

More of what gets built.

Smaller pieces that sit inside the bigger projects. They are listed here because they are real work, not separate products.

Customised Jellyfin web client

A modified web client for a personal Jellyfin server: request and discovery rows in a Seerr-style design, a quality selector, season pills, hideable home rows and TV-remote navigation.

Built on the open-source Jellyfin web client and Seerr. Shipped as numbered versions, each with a documented rollback.

Windows and Android packaging

The same client wrapped as a Windows installer and an Android app, with a signed update check, a branded installer and an offline fallback page.

Installer upgrades are rehearsed in Windows Sandbox before release.

The icon family

Every product shares one C-ring mark on a dark rounded tile; only the symbol inside changes. Icons are generated from geometry and checked at 16, 32 and 48 pixels.

Flat two-dimensional marks, one idea per icon.

Watchdog and alerts

Scheduled checks and a watchdog raise a phone alert when something fails, instead of waiting for it to be noticed. Repeat alerts are rate-limited so a real problem is not buried.

Personal-scale monitoring, not an enterprise service.

05 / How the work gets built

Habits behind every release.

Independent projects, designed, built, released and looked after by one person. These are the working rules that keep them dependable.

  1. Preview before publish

    Anything people will see is built and reviewed locally first. Nothing visible goes out on the strength of a passing test alone.

  2. Every change has an undo

    A change log records what changed, the backup taken first and the exact steps to reverse it.

  3. Test, then verify live

    Services ship with automated tests, and changes are checked again on the running system before they count as done.

  4. Updates wait for a quiet moment

    Web releases check server load and active playback first, and a failed release can be rolled back to the previous version.

  5. Private by default

    No tracking on this site. Screenshots are privacy-reviewed, and source code lives in private repositories unless it is meant to be shared.

Toolbox

  • Python
  • PowerShell
  • JavaScript & TypeScript
  • HTML & CSS
  • SQLite
  • FFmpeg / HEVC
  • Electron
  • Capacitor (Android)
  • Docker on Linux
  • Git
CluckyWorks C-family globe logo

06 / Behind the work

Built around real use.

CluckyWorks brings together the personal software projects of Clucky7. Some are apps you open every day. Others quietly check, organise and protect the work behind them.

Each story here focuses on a real need, documented engineering and honest limits. Clucky is me; CluckyMedia is my media server project. CluckyWorks is the home for the wider collection, with credit to the open-source projects behind it.

Find Clucky7 on GitHub
Interface screenshot