Recipes / Claude Code use cases
Claude CodeFull setupPersonal ops

Claude Code rebuilt Apple Photos for his own Immich server

He moved about 85,000 photos and videos to his own Immich server and switched iCloud Photos off. No Immich app felt like Apple Photos, so Claude Code built HomeRoll: a native iOS 26 app that looks and behaves like Photos but keeps everything on his server. He isn't an iOS developer by trade, so Claude wrote nearly all the code while he decided what to build and tested it on his iPhone.

From u/SilentMode46 (r/ClaudeAI) on Reddit · Nov 2026

Setup timeNot stated. Performance on an 85,000-item library took many rounds of measuring on the real device
CostFree app, no paid tier. Your own Immich server: hardware once, then electricity (the README estimates a small mini PC at about 15 to 20 W, roughly 11 to 15 kWh a month)
RunsWhen you want your photo library on a server you own, in an app that feels like Apple Photos
NeedsClaude Code, plus a Mac with the iOS Simulator for the UI tests, An iPhone on iOS 26 to run the app, SideStore or AltStore, to install the IPA from GitHub releases, Your own Immich server (he tested v3.3.5), rea, the reverse-engineering tool, if you repeat the research step (MIT), You, deciding what to build and telling Claude what feels wrong
Last updated2026-11-15

What the source did

  • He stopped paying Apple for iCloud storage: he moved about 85,000 photos and videos to his own Immich server and switched iCloud Photos off.
  • Every Immich app he tried felt nothing like Apple Photos, so he built HomeRoll: a native iOS 26 app (SwiftUI and UIKit) that looks and behaves like Photos but stores everything on his own server.
  • He isn't an iOS developer by trade. Claude wrote nearly all the code; he decided what to build, tested on his iPhone and said what felt wrong.
  • Reverse engineering: Claude took Apple's Photos frameworks from iOS 26.3 apart with a reverse-engineering MCP server (rea) and listed all 226 actions the app can perform. 147 work; 62 need iCloud or Apple services, 16 are Apple-internal, and 1 isn't possible on iOS.
  • Clean room: one agent only wrote plain behavior descriptions ("what happens when you do X"), and the app was written from those, not from Apple's code.
  • Testing: Claude wrote automated UI tests and ran them in the iOS Simulator, comparing screenshots with the real Photos app. 140 of the 147 working actions are covered.
  • Maintenance: Claude reads GitHub issues, reproduces bugs in the simulator, proposes a fix and drafts the reply. Nothing is released until he says go.
  • Performance was the hard part. The first versions crashed or stuttered with 85,000 items, and it took many rounds of measuring on the real device.
“I got tired of paying Apple every month to keep my own photos”— u/SilentMode46 (r/ClaudeAI), Reddit

Summary written by Agent Cookbook from the original post. See the original for the full context. How we source recipes

Our notes

What it takes
Claude Code, a Mac with the iOS Simulator for the UI tests, an iPhone on iOS 26, SideStore or AltStore to install the IPA from GitHub releases, and your own Immich server (he tested v3.3.5). The research step used the rea reverse-engineering tool.
Where it breaks
Big libraries: the first versions crashed or stuttered with 85,000 items, and it took many rounds of measuring on the real device. A free Apple ID signature needs renewing every 7 days, per the README. The post says MIT; the repo's LICENSE is GPL-3.0. The README warns the backup is only as safe as your server.
Human checkpoint
Nothing is released, and no reply is posted to a GitHub issue, until you say go. iOS asks before Free Up Space removes anything from your iPhone. Sending, buying, posting and deleting always need a human.
Tools involved
Claude Code, plus a Mac with the iOS Simulator for the UI tests, An iPhone on iOS 26 to run the app, SideStore or AltStore, to install the IPA from GitHub releases, Your own Immich server (he tested v3.3.5), rea, the reverse-engineering tool, if you repeat the research step (MIT), You, deciding what to build and telling Claude what feels wrong

✓ Verified Source link checked and still live. Notes by Thomas, editor. How we verify

Get their template

Made and published by u/SilentMode46. Start here; it is their original, not ours.

Our adapted version

Ours Our version, based on u/SilentMode46's post and README. Not his wording. Fill in the [BRACKETS].

CLEAN-ROOM APP BRIEF (our version, based on u/SilentMode46's post and README) App I'm replacing: [name the app, its platform and the library it uses] Server I already run: [for example, Immich, with its version] Step 1: List every action the app can perform, one line per action: [paste the list]. Mark each one as works here, needs iCloud or Apple services, Apple-internal, or not possible on my platform. Step 2: One agent writes behavior descriptions only ("what happens when you do X"). It doesn't read the original app's code. Step 3: A second agent builds the app from those descriptions only, and checks each action off the list as it goes. Step 4: Write automated UI tests and run them in the simulator. Compare screenshots with the original app, and list every gap. Step 5: Maintenance. For each new issue, reproduce it in the simulator, propose a fix and draft the reply. Don't release anything and don't post anything until I say go.

Approval rule

🛡
Nothing is released, and no reply is posted to a GitHub issue, until you say go. Free Up Space deletes from the iPhone only what's verified on the server, and iOS asks first. Sending, buying, posting and deleting always need a human.

Set it up

  1. Pick the app you're replacing and list every action it can perform. He listed 226 for Apple Photos, using rea.
  2. Split the work: one agent writes plain descriptions of what each action does, and never sees the original app's code.
  3. A second agent builds the app from those descriptions only, working through the checklist.
  4. Write automated UI tests, run them in the iOS Simulator, and compare screenshots with the real app.
  5. Install the build on your iPhone with SideStore or AltStore, tap through it, and tell Claude what feels wrong.
  6. Let Claude work through GitHub issues: it reproduces each bug in the simulator, proposes a fix and drafts the reply. You decide what gets released.

Common failures

⚠
  • Asking for "make it like Photos" with no list. He says the concrete 226-action checklist is what worked.
  • Expecting a big library to work on the first build. The first versions crashed or stuttered with 85,000 items.
  • Trusting the post's MIT label. The repo's LICENSE is GPL-3.0.
  • Forgetting the 7-day refresh. A free Apple ID signature needs renewing every 7 days, per the README.

Variations

  • The README links HomeRoll-Desk, a macOS sibling where edits look the same on the iPhone. In comments he also mentions an Apple TV app, HomeRoll-TV.

Related setups: Claude Code rebuilt his treadmill screen → · Five app subscriptions swapped for Claude Code rebuilds → · Claude Code migration agents for paid SaaS tools → · Old Kindle turned into a weather dashboard by Claude Code →

Get the 10 best agent setups. Free.

Plus new recipes every week. One email, no spam.

Unsubscribe anytime. Privacy

Related recipes

Same job: Personal ops

In these guides: More Claude Code use cases → · AI agents that save you money →

Get their template ↗