Camo: Photo Editing Coach

Problem & Learner Context

Amateur photographers face a persistent skills gap between the blunt simplicity of single-swipe filters and the overwhelming complexity of professional editing suites like Photoshop. Users who want greater creative control are too often intimidated by Photoshop's vast interface to ever develop genuine fluency — leaving them stranded between tools that are either too simple or too complex.

User research surfaced a recurring persona: the "DIY Perfectionist" — someone who feels a strong sense of creative ownership over their photos and insists on being in control of the editing process, but whose intimidation by complex tools actively stifles mastery. This tension drove several core design questions:

• How might we make photo-editing welcoming to use and to learn from?
• How might we give the DIY Perfectionist the confidence and mastery to produce "flawless" photos?
• How might we get photo-editing software to anticipate the DIY Perfectionist's vision for "flawlessness"?
• How might we remove the sense of intimidation from the tool in one's pursuit of mastery?

User interviews also revealed how personal and varied photography is as a practice. One user explained that she takes only 1–3 photos per day, each one intentional:

"I don't want a photo of me in a museum, but me in the museum with a cup of coffee. Or an afternoon in Paris. Or a book. I look forward to showing my pictures to my family, but I'm only uploading my pictures to capture a bigger experience — then the raw process needs to be self-explanatory." — Anabel

Another user took up to hundreds of photos a day, dedicating blocks of time to curate and sequence them into a visual narrative. Despite these differences in style, both users shared the same frustration: the tools available to them did not match their creative ambitions.

My Design Decisions & Rationale

The defining design principle for Camo was to keep the intelligent coach in a supporting role — not as an instructor dictating a prescribed sequence of steps and exact adjustment values, which would strip the user of the very sense of control they most needed. Conventional interactive tutorials tend to guarantee a successful output at the cost of the user's creative agency. Camo's approach inverts this: the system offers multiple guided pathways and adjustment ranges, not targets, so the user retains creative judgment at every step.

This distinction between process-driven and product-driven design was central to format selection. The app format — an interactive tool the user actively controls — was the only viable vehicle for this philosophy. A static PDF, a video walkthrough, or a one-way tutorial would have replicated the same prescriptive dynamic Camo was designed to break.

Interface design choices were also deliberate: since Camo is intended as an intermediate tool before users graduate to Photoshop, many UI elements — workspace layout, visual indicators, panel organization — were designed to parallel those of professional-grade software. This reduces the cognitive re-learning cost when users eventually make the transition.

Project Walkthrough & Highlights

Camo's core feature is an AI analysis engine that compares the user's raw image against a professionally edited reference photo and generates multiple guided editing pathways from which the user can choose. Rather than prescribing exact adjustment values, the system offers recommended ranges — preserving the user's creative latitude while ensuring the outcome stays within professional standards.

Comparative visual feedback reinforces the learning loop: tools like histograms and light-distribution graphs display both the raw and reference images side by side, allowing the user to see their edits concretely and with interpretive depth. This encourages thoughtful emulation rather than copy-cat replication, sustaining the user's engagement as a growing editor rather than a passive follower of instructions.

Results & Evidence of Value

[Camo was developed as an academic research prototype at Stanford. Describe any usability testing outcomes, formative evaluation findings, or the evaluation criteria designed into the project blueprint for future measurement.]

Reflection & Lessons Learned

[Identify one aspect of the design or process that didn't go as planned, how you would iterate on it given more time or resources, and the broader insight you carry forward into your current design practice.]