Can Pic-Time be vibe coded?
Host client galleries with favorites, downloads, and simple proofing
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Pic-Time, host client galleries with favorites, downloads, and simple proofing. The hard boundary is gallery delivery, store automation, print labs, marketing, and support, plus image pipeline quality, models, and workflow polish.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
medium editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Catalog local photos, host client galleries with favorites, downloads, and simple proofing, generate previews, and export selected originals or rendered copies.
- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- gallery delivery, store automation, print labs, marketing, and support
- proprietary raw-processing quality
- cloud sync and sharing
- large AI models
- Reliability at the vendor's scale is an operations problem, not a prompt.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
Why people still pay
People still pay for Pic-Time because photographers pay because image quality, catalog safety, and fast handling of huge libraries matter more than cloning sliders. The recurring cost buys raw codecs, color management, metadata, previews, face models, GPU support, storage, backups, sync, and export fidelity, not just the visible interface.
Reliability at the vendor's scale is an operations problem, not a prompt.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Pic-Time
Context
**Pic-Time** — Host client galleries with favorites, downloads, and simple proofing. It currently costs $10/mo.
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Pic-Time, host client galleries with favorites, downloads, and simple proofing. The hard boundary is gallery delivery, store automation, print labs, marketing, and support, plus image pipeline quality, models, and workflow polish.
This brief describes a focused, single-operator replacement for the part of Pic-Time that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Catalog local photos, host client galleries with favorites, downloads, and simple proofing, generate previews, and export selected originals or rendered copies.
Build a focused single-user workflow with real persistence, search, and export.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Desktop computer.
Local photo library.
Sufficient disk space.
Optional GPU for AI features.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build a personal replacement for Pic-Time in an empty repository.
Use Tauri 2, React, TypeScript, Rust image libraries, SQLite, and local filesystem access; do not offer alternative stacks.
The core loop is: catalog local photos, host client galleries with favorites, downloads, and simple proofing, generate previews, and export selected originals or rendered copies.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Index selected folders without moving or rewriting originals and store only catalog data in SQLite.
Generate thumbnails and previews, read EXIF, detect duplicates by hash, and monitor file changes.
Provide timeline, folders, albums, ratings, flags, tags, search, and side-by-side compare.
Store edits as reversible parameters for crop, rotate, exposure, contrast, white balance, and saturation.
Render exports to a new folder with explicit color space, quality, size, and metadata choices.
Add catalog backup, missing-file repair, integrity scan, and a clear original-safety guarantee.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out a proprietary raw-rendering engine.
Deliberately leave out hosted cross-device photo sync and client galleries.
Deliberately leave out frontier culling, retouching, and generative models.
Finish by running the tests and listing the exact commands used.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
Gallery delivery, store automation, print labs, marketing, and support.
Proprietary raw-processing quality.
Cloud sync and sharing.
Large AI models.
Reliability at the vendor's scale is an operations problem, not a prompt.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
What you still own after launch
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Risk
**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.
Editorial confidence in this assessment: medium. No independent one-shot implementation is linked yet.
Prior art
Working open-source software you can read, fork, or borrow from before starting:
[Immich](https://github.com/immich-app/immich) — Active open-source self-hosted photo and video management platform
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/pic-time
You still own the product
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
Open-source prior art
Before you start
Can Pic-Time be vibe coded?
Partly, if you narrow it. The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Pic-Time, host client galleries with favorites, downloads, and simple proofing. The hard boundary is gallery delivery, store automation, print labs, marketing, and support, plus image pipeline quality, models, and workflow polish.
What can an AI coding agent reproduce from Pic-Time?
Catalog local photos, host client galleries with favorites, downloads, and simple proofing, generate previews, and export selected originals or rendered copies. Build a focused single-user workflow with real persistence, search, and export. A responsive interface with real empty, loading, success, and error states.
What will a DIY Pic-Time replacement still be missing?
gallery delivery, store automation, print labs, marketing, and support; proprietary raw-processing quality; cloud sync and sharing; large AI models; Reliability at the vendor's scale is an operations problem, not a prompt.; The last 20 percent is sync, migration fidelity, speed, and edge cases.
What do I still own after building a Pic-Time alternative?
Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss.