I agree about the subscription annoyance. It tells me I have “Free updates until Oct 23 2021” but still bombarded me with “subscribe” on launch! I find this predatory.
For an app that wants to save photos for the user, how do you do this permissions gating without irritating the cursory view by skeptical user?
For an app that wants to make sure you don't lose any metadata/exif (including location) how can you do that without raising eyebrows for location permissions.
How can you communicate the value prop to convert a subscription? I think the app does a great job for existing users in providing a 1yr automatic subscription (would have thought parent comment would get this) but I also am confused, and will be confused, when that time is up I think.
--
Halide is a incredible application. One of my favorites. I don't use it as much as I could benefit from it because of the problem of it not having the same immediate access as the native camera app does, but also it does not include Live Photo capture which for me and moments with friends and family is essential. That said, it's the best built app I have on my phone, the best design, provides path to incredible photography results, and I will continue to pay for it.
Look, it's 2020 and tech is getting so human-hostile in so many different ways. I think it behooves us to make sure there's always a way our software can be used no matter how restrictive our users are with permissions.
Thanks for your response.
Now I re-download Halide (the version I paid for a year or two ago) to see what this new version is all about and I'm presented with a bewildering splash screen, prompting me to subscribe (for what now?) and I do everything I can to not subscribe, and then I'm taken to the permissions screen, and it's asking for camera permissions (totally reasonable), photo library access (ok, but let's hold on for a sec), and location access (no thank you), and I can't get anywhere in the app that I paid for, without granting all three permissions.
Having location access a hard requirement for a photo app is just ridiculous. What product owner made this decision? IMO it's completely out of touch and user hostile.
Edit: turns out the hard constraint was access to the photo library. Which, how was I to know that? The UI seemed to indicate that I couldn't proceed until all the boxes were checked.
Look, I get that this is a specialized app and I understand the complexity and nuance related to app permissions. Which means the app developer has to be super clear about what the requirements are from the start.