Best approach to "pre-launch" app

Seeking your knowledge on what will be acceptable to Apple for our roll out. Our end goal is a subscription service for $x a month you get y items of your choice shipped to you.


Before being able to take payment/have paid members/ship items/purchase inventory, we want to drive traffic through social to our app, and also be able to throttle the amount of paid members and shipments we get to control growth.


Ideally we would like our app to 'onboard' potential customers with our offering, have them sign up for a free account via FB/IG/PI and fill out a profile. Then they receive their spot in our 'queue' for an invitation later, to access the full app (this part has not been built yet).


Is there any aspect of doing an 'onboarding and invitation queue only' that Apple will disallow?


If so, what if you are onboarded, create a profile, receive invitation queue spot AND are able to rate items in our inventory, which you can receive as part of your subscription later when you sign up as a paid member. In otherwords, a 'Tinder style app waiting to become a paid dating app'.


Would this be acceptable and also be able to get listed in the proper category, say 'apparel subscriptions' or similar?


Lastly, when we do launch (offer subscription and shipping) we need to restrict paid members to a certain major US only (or our US state only). What is the proper handling of this as I know it is often done with startups, but heard it can be problematic?


We are not planning on having the entire app experience on our website, as we want to be app-centric (but if need be, we will adjust). Any thoughts/wisdom are very appreciated. Thanks

Replies

>Would this be acceptable


There are no pre-reviews, and app review isn't here, if that's what you're asking - all you can hope for here are the opinions of other devs.


About your 'subscription' service....that word has a specific meaning here, in the context of In App Purchase, which usually means digital goods consumed inside the app...certainly not clothes. I assume you meant your own $ervice $cheme, outside of the app.


>and also be able to get listed in the proper category


You can pick a primary and secondary category, but Apple has the final say.


>or similar?


My guess is your app would end up in 'shopping'.


>to a certain major US only (or our US state only).


Can you explain that better, thanks.


If you mean 'major US city', not sure that's entirely feasible using the store, which only lets the dev choose which territories/countries the app is on sale in, not cities/states.


You could put the app on sale in the entire US, and then DIY restrict on your end, but App Review would have to decide if they're ok w/that.


About the launch...don't hard-plan against a fixed date the app might be in the store - don't assume the app will be approved at all, and/or be approved on your timeline. Get it in the store first, then pull the launch trigger.

What KMT said, plus I don't think there is a mechanism for invitation-only apps. Generally, all apps on the App Store are available for anyone to download if they want to.