How to deliver an App on a subscription model?

Looking into App Store or Self Fulfilled but we don't know how to get the app service to stop working once they have it on their devices. It's a subscription model that we will charge $47 per month for the service, but if they cancel, we need to cancel their usage of it. Need to know how to launch this thing ASAP. Any help?


Without understanding what the App does, it's difficult to help. But one suggestion is to have the app, itself, require authentication on your server when used. The authentication could be as simple as them logging into the app for service. When they cancel their subscription, you suspend or delete their login information.
Another autentication method could be associated with their payment method. Keep a simple database or profile of this user (i.e. login and payment history as trial/active/inactive/suspended). I am assuming you already have their payment profile on file in your subscription model. On start-up, your app checks your database to see if this person's profile is in the active state, before it continues.
There are any number of ways to validate the user. One suggestion is to also offer a trial membership for 14 days. As part of the authentication process, you can check the date/time remaining in the trial period, send them reminders that their credit card will be charged at the end of the trial, etc.
When they have cancelled their subscription or their credit-card fails to process successfully - you update the authentication database appropriately. When they bring up the app service again and their status is inactive, the app outputs the appropriate instructions on how to refill or restart their subscription.

This is just a few ideas. I am confident that others will have better ideas.

Answered 6 years ago

Geez, if you are asking this because the person or people building this don't know the answer, you don't have a technical team capable of launching your "thing" ASAP.

This is such a basic technical question that you need to stop what you're doing and find a competent technical co-founder before pursuing this idea any further.

Answered 6 years ago

Your app should include a login that would validate with your servers who is/isn't an active member.

Let's hop on a quick call and we can discuss specifics.

Answered 6 years ago

Just so you know, Apple rarely approves apps for subscription billing so you will likely have to build your own billing backend.

Answered 6 years ago

If you are in the mid of app development then I assume you had already shared this with your tech team. If they were unable to answer that then you are surely in trouble. Fire them right now! because you don't even know what they will end up building.You might end up getting a rejection from Apple store if the app is not "wired" properly.

On the other note Apple doesn't have any problem with subscription based apps, they have problem with the nature of the app. With recent updates they have provided support with there SDK but have gone very strict with the privacy policy in respect to the end user. Otherwise the billing is through the same old app store billing system (70% dev/ 30% store).

Hope it helps.

Answered 6 years ago

Unlock Startups Unlimited

Access 20,000+ Startup Experts, 650+ masterclass videos, 1,000+ in-depth guides, and all the software tools you need to launch and grow quickly.

Already a member? Sign in

Copyright © 2019 LLC. All rights reserved.