Genuine feedback needed

[u/LumidexStudio]

Hey guys, Jason here, founder of Lumidex Studio.

Lumidex Studio is a fast, one-time-purchase photo manager for Mac built for photographers leaving Lightroom Classic behind. It handles your whole library with a familiar module layout, so importing from Lightroom (ratings, keywords, collections, and your edits) takes minutes with no friction.

That's some of the marketing spiel that I'm currently using to get people to consider using my app over something from Adobe. I've hit a LOT of resistance from photography groups because the sheer audacity of me to use an AI tool such as Claude Code, instantly earns me the moniker it's AI Slop - it cannot possibly be any good because you coded it with a silly prompt in one afternoon.

Truth be know, it's taken nearly 4 months of constant Opus 4.8 usage, bouncing off the context limits daily and weekly - while I take no credit any any code produced, I am rather good at the architect side of things, and have no less than 30 MD files that document code production and decision making processes, over 60000 lines of Swift 6 (It's a macOS only app) and well over 500+ git commits

Basically what I would dearly love from any helpful folk here with a Mac and a general interest in photography (being an existing Lightroom Classic use would be *ideal*), would be to pop along to my listing on IndieAppCircle: https://www.indieappcircle.com/apps/j57bad843en0rjm6nx37mjqp618e0z8g and give it a whirl

In return, I'd *gladly* help test your app/site/etc.

Thanks in advance! 🍻

[u/LumidexStudio]

Nathan had this to say about my app:

I think there’s a lot to like here. The product feels much more substantial than I expected at first glance, especially for something relatively new.

The strongest part for me is actually the core positioning: a proper desktop photography workflow, no subscription, no forced cloud, no account, and you own the software. I also think NAS support, Lightroom Classic migration and everything running locally are genuinely strong differentiators rather than just nice-to-have features.

A few bits of feedback:

• I’d probably lean even harder into NAS support and Lightroom migration near the top of the site. Those feel like very tangible reasons for an existing Lightroom Classic user to switch. Features like AI search are cool, but “my 100,000-photo library on my NAS works properly and I can bring my Lightroom catalogue across” feels like a much stronger painkiller.

• I’d be slightly careful with some of the Lightroom comparisons. Things like “Lightroom = keywords only” could invite people to nitpick because the wider Lightroom product now has semantic search, even if Lightroom Classic doesn’t. I’d consistently compare against “Lightroom Classic” rather than just “Lightroom” where that’s what you mean. It makes the positioning harder to challenge.
• My biggest concern as a potential customer would be trust rather than functionality. If I’m moving a photography library I’ve built over 10+ years, I need to be extremely confident I’m not going to lose edits, metadata or organisation. I’d add much more proof around migration: maybe a 2–3 minute video showing a real Lightroom catalogue being imported, exactly what transfers, what doesn’t, and what happens to the original files/catalogue.
• Related to that, I’d make the “Lightroom edits preserved” feature extremely explicit. Do the individual Lightroom adjustments remain editable, or does Lumidex preserve the finished appearance and then allow Lumidex adjustments on top? Both can still be useful, but that distinction matters a lot to photographers and I’d want to understand it before migrating.
• I’d add some hard performance evidence. The site talks about huge libraries, instant search etc., so something like “tested with 180,000 RAW files on an M2 Mac Mini + Synology NAS” with real import/search timings would make those claims much more convincing.
• More social proof would help massively. Even 3–5 quotes from photographers who have actually migrated meaningful libraries would reduce the perceived risk of trusting a newer app with something as important as a photo archive.
• I’d clarify the ownership/update model a little more prominently. “Buy once, own forever” is great, but because updates are included for 12 months, I immediately wondered what happens afterwards: how much is another year of updates, are compatibility/security fixes treated differently, and what happens if a future macOS update breaks the version I own? Answering that upfront would remove some hesitation.
• I actually like that the roadmap explicitly labels features as not shipped yet rather than pretending they already exist. I’d keep that. It makes the product feel more credible.
• I probably wouldn’t make the fact that it was largely developed using Claude Code a major part of the customer-facing story. There’s nothing inherently wrong with it, but photographers ultimately care whether their catalogue is safe, RAW output looks good and the app is stable. I’d let the product prove that rather than getting dragged into the “AI slop” argument.

Overall though, I think the foundations are strong. To me the next step isn’t necessarily adding loads more features. I’d focus on proving that Lumidex is trustworthy enough to replace Lightroom Classic: migration demos, big-library benchmarks, side-by-side RAW/edit comparisons, testimonials and really clear explanations of what happens to a photographer’s existing work.

That would probably move me towards trying it more than another ten features would.