You might get a yearly discount offer that is less than $2/month if you get lucky (A/B test split). But that's less than the cost of running the model for people, so hopefully others will consider paying full price.
You might get a yearly discount offer that is less than $2/month if you get lucky (A/B test split). But that's less than the cost of running the model for people, so hopefully others will consider paying full price.
Now with the current flow I would need to activate the subscription and then immediately go to Play Store settings to deactivate the subscription so that I would not forget it.
It gives some features with a totally free plan. That makes the IaP feel less like a bait and switch.
The proposition of SnapCalorie is compelling. Calory ui is decent and I use a scale so accuracy should be good but I think their database is shitty. Meatloaf will vary from 1.5 kcal/g to 3, steak will show as 1 kcal/g, stuff like that.
That seems like a very dark pattern and is, honestly, pretty scummy.
Which makes it par for the course in the scam that is mobile development
Our FAQ and pricing pages all list that it is a paid only app. All of our ads explain that it's subscription based. Anyone who asks we're very transparent about it. If there's somewhere else where you think we can list it to make it more clear I'm happy to add it, just not sure where that would be.
Edit: The "dark" pattern is in the registration flow. It doesn't mention that the app requires a subscription anywhere until after you've created an account. Surely you could add a disclaimer before creating your account? This has nothing to do with the App Store.
Edit 2: I'm not saying you intended to implement a dark pattern. Just perhaps a UX oversight.
Edit 3: The download page would be another great place to put this info, since that's the primary CTA on the home page (there's 4 prominent download buttons).
We can't hit people with the paywall before they've registered because we need to assign the trial to their user record. We've tried adding more language during onboarding but no one reads any of it, they just click through.
You're mistaking challenges in building a global app for malicious intent. I left a job paying a lot more to do this because I wanted to help people.
We'll add something back to the FAQ on this, thank you all for pointing it out.
Perhaps the grandparent comment of mine did, not me.
> We'll add something back to the FAQ on this, thank you all for pointing it out.
So people don't read onboarding instructions, but you're going to bury the pricing info in an FAQ in the App Store where it's hidden below the fold?
The fix is quite easy. Here's a redesign for your in-app registration screen:
Create account
┌────────────────┐
│Name │
└────────────────┘
┌────────────────┐
│Email │
└────────────────┘
┌────────────────┐
│Password │
└────────────────┘
┌────────────┐
│ Register │
└────────────┘
7-day free trial,
$6.67/mo afterI cannot find a FAQ or pricing page on your website.