Build a custom photo manager
Herrmann reports a photo manager in production use and more than 250,000 imported files. The report links to source code and development history.
Claude Code
First-hand report- Reported by
- Thomas Herrmann · 42ways GmbH
- Published on
- 42ways.de
- Source reviewed
- Publication date
The documented use case
Thomas Herrmann uses Claude Code to develop a photo manager with search and previews for files across multiple drives, including disconnected drives. The project is now called MAKI.
Workflow from the source
- Requirements and architecture
- Implementation with Claude Code
- Tests and personal use
Editorial summary of the source.
What the source shows
Herrmann reports a photo manager in production use and more than 250,000 imported files. The report links to source code and development history.
What remains open
A personal project report by an experienced developer. Scope and timing are the author’s claims; independent quality verification and transferability of the effort remain open.
OUR ASSESSMENT
Who could this suit?
Photographers and small creative teams with specific archive requirements and technical support.
Prerequisites
Development experience, Claude Code access and a test environment with backed-up sample files.
Your checkpoint
Start with copies; check imports, duplicate detection and recovery. Take responsibility for architecture and maintenance.
Effort and data
Development skills
Check model access, data processing and maintenance needs for your setup. Complete operating costs remain open in the source.
Fictional example for illustrationCreated by us · not a result from the report
Fictional example · our illustration · not a test result
A fictional photo studio wants to browse previews while its archive drive is stored away.
Possible view: preview, capture date and archive drive. A test checks whether search works with the original files disconnected.
Understand the tool
Access, costs and availability in Europe