Hanif Bahari
Development

Product case study · In progress

VersionLoom

A local-first macOS workspace that turns creative file history into a visual timeline for comparing, annotating, organizing, and restoring earlier directions.

Year
2026
Role
Creator, product designer, and developer
Technologies
macOS, File system monitoring, Local-first workflow, Visual comparison, GitHub Releases

Local-first · visual history · macOS

Every direction deserves a way back.

Download for macOS Apple silicon · macOS preview · 7.7 MB
Installation & privacy

01

The problem

Creative work changes through many saves, experiments, and client directions, but ordinary file systems make that history difficult to see. VersionLoom needed to preserve the freedom of existing project folders while making earlier visual decisions easy to compare, label, understand, and recover.

02

Context

VersionLoom is a macOS application for designers and artists. It watches the project folders they already use, captures meaningful saves, and keeps the resulting history on the Mac. The first public release supports Apple Silicon and previews common image, SVG, Photoshop, and Affinity files; Intel and Windows support are planned after the initial release is validated.

03

Responsibilities

  • Define a visual version-history workflow for creative projects without requiring a cloud account or a new file-management system
  • Design the comparison, library, annotation, labels, milestones, search, and activity-history surfaces
  • Build local monitoring, project-direction organization, restore, export, and reconstruction workflows
  • Package and document the Apple-silicon release with privacy guidance and first-launch macOS instructions

04

Architecture

VersionLoom keeps the project folders and version history local to the user’s Mac. A folder-monitoring layer captures meaningful saves, while the application organizes those states into visual directions that can be compared, annotated, searched, restored, or exported. Preview support lets common creative formats become visible inside the history without uploading source files or introducing a remote service.

05

Technical decisions

Respect the folders artists already use

VersionLoom watches existing project folders instead of forcing a migration into a proprietary library. The visual history is an additional layer around a familiar creative workflow.

Make comparison the primary action

Side-by-side and overlay views help a person judge visual change directly, while notes, labels, and milestones give that change enough context to remain useful later.

Keep creative files private by default

The application works locally, requires no account, and does not upload creative files. That boundary is part of the product’s value rather than a hidden implementation detail.

Treat directions as first-class history

Experiments and client options can remain separate directions, preserving the branching nature of creative work instead of flattening every save into one linear list.

06

Challenges

A useful creative history must be detailed enough to recover a direction but quiet enough not to interrupt making. It also needs to recognize visual changes across several file formats without turning the application into a cloud archive or a general-purpose asset manager.

07

Solutions

VersionLoom combines folder monitoring with a visual library, direct comparison, lightweight annotations, milestones, search, and restore. Local storage and preview support keep the workflow responsive and private, while separate directions reflect the way real creative projects branch and return.

08

Results

The public 0.1.1 Apple-silicon release provides visual project history, comparison, annotations, labels, milestones, search, restore, export, and local-first privacy. Its portfolio download link resolves the newest published VersionLoom macOS release automatically.