Use case for project

and you can use labels as permissions

Then you set the collection to subscriber only

If a user does not have that label then he won't be able to access that collection

It is easier than your initial plan

okay. i get what you're saying. so to rectify my thought process.. instead of restricting user account, use permissions.

And you should not disallow account creation

i guess what i don't see is if a user didn't create an account, and they subscribe they still can't access premium content/services.

What happens if the subscription runs out? Do you want to delete the account?

good point. i didn't think that far

Then that user would lose all settings, progress, etc as well

prob don't want to delete the account

No one wants that

yeah. that would be a hurdle .. more effort should be for them to re-subscribe.. but keep their content.. just restrict what they can access.

Yeah that's the normal procedure

Your intial plan can be realized too but it is way more complex than it needs to be

i was following the lead of another app i saw. but my guess is they had a specific use case, and perhaps used rto allow account creation as a parrallel feature to subscriptions

I have made an app somewhat similiar to what you described too. Where registration is restricted

But only because it is a closed community

That's why I asked whether that is really nessecary

well. that was my idea.. to join the community you needed to be a paying member

i don't have much for a non-paying member aside from creating workouts using the app

trying to not lock that feature down

You have to keep in mind that you should still allow access to your app and certain services to non members

If not apple and google won't allow your app

right