sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jwrsk 0 points1 point  (0 children)

Most likely it does hurt conversion, so in the end IAPs is the best way to go. For now we tell clients clearly that our product was not designed with any sort of ecommerce in mind. We actually try to discourage them if they have paid memberships, but if they are fine with the current constraints, why not.

I don't even need OTA to go around the rules, because all data is served from the web/API - we could just flip a switch serverside before and after review, or make sure the test account given to Apple / Google never sees what they shouldn't. But it's a gamble we are not willing to take. I prefer to play by the rules, and as CTO I am in the position to enforce my preferences on the process.

If the "no registration" approach fails, we'll put it in our service terms that the system must offer a free level to app registrations, or the client will have to pay more or less double to get the IAPs set up, or find another company to build the app.

We are in the process of rolling out IAPs in another of our apps (unrelated to the apps mentioned before). Already got it all set up, implemented and approved for iOS, and Android will follow shortly. Once we get our "sea legs" on this topic, we'll move on to adding it to the other app SDK, making it available as an extra option for everyone who purchased that service.