https://www.lux.camera/halide-mark-iii/
As for the subscription, there’s always been a pay-once option for major releases. You just miss out on a free trial, the beta program, and anything we might release with ongoing costs.
When I emailed in, they blamed it on how the App Store mechanism changed.
Halide somehow is the only app that has this issue.
The issue is that, indeed, it actually validates that the App Store account currently logged in purchased the app. I believe this is intended behavior, as it closes a piracy loophole where you could log into the Apple ID of a friend, download all their paid apps, and then log in to a different account while retaining access.
If other apps don't run into this problem, it's possible they haven't moved on to StoreKit 2. Or the app has their own login independent of app subscription; setting aside the time it would take me to build that, I don't think most people are willing to create an account to try a camera app.
I use Analogue for day to day capture, and NoFusion and Moment apps for things I will want to edit later. All with one-time purchase. I don't mind paying for quality apps, but I do have subscription fatigue now.
Might check it out. Thanks for letting me know. But really been enjoying Analogue lately.
Unfortunately it looks like lifetime users don't get access to the beta program for whatever reason. I guess they don't want feedback from those users.
I tried Analogue too, but I stopped using third-party camera apps altogether because they all seem to suffer from an issue where if you lock the phone too quickly after taking a photo, the photo is lost forever. I lost so many photos to this that I knew I took.
Halide shouldn't be afflicted by the lost photo issue you're talking about. Normally, if you close a lock-screen extension before a photo is written, it won't be in your library. This can be a problem when the user quickly smashes the capture button and your photo queue gets backed up.
Luckily, the unlocked app gets a chance later to access the content of lock-screen capture sessions. So our strategy in Halide is to write the intermediate files to disk as soon as you initiate a capture; this should take a split second. When we have uninterruptible time, later, we make sure the photo finished writing to your library, and if not, we try again.
However, Apple's documentation isn't clear if the OS will "wake-up" your main app to process unfinished photos, or if it relies on the user launching the app. I'll just say that I dog-food Halide every day by capturing photos of my toddler, and I can't remember the last time I lost a shot.
These days, I use the regular Camera app because I need my damn photos to save. I loved Halide, but that bug made it too unreliable. I get very distressed by data loss and couldn't continue to risk it while trying to develop a way to work around it.