Work / Desktop application

TIMELIMIT

FEATURED

Offline-first desktop deadline instrument

Source repository
Dark offline TIMELIMIT desktop widget with a tabular countdown display and deduction control.
Committed desktop UI artifact.
01

Context

A long commitment can lose urgency when it has no visible, daily accountability mechanism.

Problem

The deadline tool needs to preserve correct remaining-time behavior across sleep/resume, calendar boundaries and local state changes.

Operational impact

Keeps a long-term deadline visible and derived from the current timestamp, so local users can review remaining time without relying on a drifting counter.

Constraints

  • The project is portfolio code, not a signed or hardened production release.
  • The app is local/offline; it does not demonstrate external SaaS/API integration.
02

System

An Electron/TypeScript desktop widget that makes long-term deadlines visible through timestamp-based time calculation, deduction rules and local persistence.

Inputs

  • start date
  • commitment years
  • deduction events
  • local user settings

Implementation

  • Renderer UI calls clock, deduction and UTC date engines.
  • A narrow contextBridge connects local UI state to Electron main-process capabilities.
  • State persistence follows temporary file, fsync and rename behavior in the app user-data directory.
  • Electron renderer/main/preload layers with a narrow IPC bridge.
  • UTC-aware date math, deduction engine, translations and local window/tray controls.
  • Five committed Vitest files declaring 27 test cases.
03

Decisions

  • Calculate from timestamps rather than decrementing a counterTime remaining stays derived from the current clock after sleep/resume rather than drifting with a running counter.
  • Persist state atomicallyTemporary-file write, fsync and rename reduce partial-write exposure for local state.
04

Artifacts

The artifact above is the committed evidence for this project. More screenshots and files are in the public repository.

05

Evidence

Evidence classes distinguish what can be inspected directly from what is documented, simulated or reconstructed.

06

Limitations

  • No claim of independently verified public CI execution, signing or hardened production security.
  • Electron configuration includes sandbox:false; do not position as a security-hardened release.

Discuss a system like this.

Start a work enquiryAll work