RePic is the couples’ peace treaty for bad photos: when “like the reference” turns into a debate, put the reference over your live iPhone camera, align the shot, and save a clean photo. Same composition, fewer retakes, fewer “that’s not what I meant” moments.
What became possible in your product with Astra that was not practical before?
Maker
With GPT-6 Astra, a product request—or unfinished idea—can become a coordinated process: discuss the problem, delegate bounded work, and set acceptance checks. I no longer act as the human API between tasks. I still provide ideas, make decisions, and verify results hands-on.
Before Astra, I started with Sol. With no engineering background, I carried context between tasks myself. RePic 1.0 shipped before we formalized HQ + worker: Astra now organizes scope and checks in HQ, while Luna executes.
The difference became clear in the RePic website and Product Hunt preparation. One request moved through planning, copy, implementation, launch materials, checks, and review as one workflow. The website was deployed and verified, and the Product Hunt draft was prepared. I made the final calls throughout.
Report
Maker
📌
Hey Product Hunt. I made RePic after repeatedly missing the photo my girlfriend had in mind.
She would show me a reference with the pose and framing she wanted. Once I opened the camera, I had to switch back to the reference or hold a second phone. The moment passed before I got the shot.
RePic keeps the reference over the live iPhone camera. I can crop it, adjust its opacity, move or flip it, align the person and background, and shoot. The guide stays out of the saved photo, and I can compare the result with the reference afterward.
Photos stay on the iPhone: no account and no image upload. The app includes three free clean saves; a one-time Apple purchase unlocks unlimited saving.
Before GPT-6 Astra, I started with Sol and carried context between tasks like a human API. After RePic 1.0 shipped, Astra helped us organize an HQ + worker workflow: I bring a complete request or an early idea for discussion and planning; Astra coordinates the work and review, Luna executes, and I make the product decisions and confirm the result.
I recently used that workflow for the RePic website and Product Hunt preparation, taking the work from an idea to a deployed, checked website and a prepared draft.
If you take photos for someone else, what usually goes wrong first: pose, framing, angle, or background?
Hey Product Hunt. I made RePic after repeatedly missing the photo my girlfriend had in mind.
She would show me a reference with the pose and framing she wanted. Once I opened the camera, I had to switch back to the reference or hold a second phone. The moment passed before I got the shot.
RePic keeps the reference over the live iPhone camera. I can crop it, adjust its opacity, move or flip it, align the person and background, and shoot. The guide stays out of the saved photo, and I can compare the result with the reference afterward.
Photos stay on the iPhone: no account and no image upload. The app includes three free clean saves; a one-time Apple purchase unlocks unlimited saving.
Before GPT-6 Astra, I started with Sol and carried context between tasks like a human API. After RePic 1.0 shipped, Astra helped us organize an HQ + worker workflow: I bring a complete request or an early idea for discussion and planning; Astra coordinates the work and review, Luna executes, and I make the product decisions and confirm the result.
I recently used that workflow for the RePic website and Product Hunt preparation, taking the work from an idea to a deployed, checked website and a prepared draft.
If you take photos for someone else, what usually goes wrong first: pose, framing, angle, or background?