What are the arguments to ask users to signup before they can use your app?

For example in a secret luxury accommodation booking app, once you downloaded the app, you are forced to create an account. It is important to mention that the website only mention what the service is.

I would guess that first show the users a little bit before asking to create and account with code verification.

  • Asking users to sign up before they've seen the site is a poor user experience, so there aren't really arguments to do that. Would you want to hand over your credit card before you've even walked through the door of a mystery shop in town? This question may give you some info: ux.stackexchange.com/questions/55391/… – JonW Jan 17 at 16:24
  • I meant only signup. No credit cards are requested at this point – Milah Jan 17 at 17:37
  • For what purpose? To maintain an aura of exclusivity? It's a nonsense, if your app is publicly available then it's not exclusive and the diminished returns from such a position will cost you. – DarrylGodden Jan 18 at 9:25
  • Doesn't matter if it's credit cards, personal details or anything like that. You're asking someone to hand over information about themselves before they've set foot in the place. You wouldn't do that in the real world, so why do it online? You need a really solid business proposition if you don't want the majority of people to turn away immediately. – JonW Jan 18 at 9:30
  • @DarrylGodden i agree. This was their argument. I disagree with asking to signup unless it’s a SaaS service where you have to access your own private data. JonW what would you say about slack, asana and other services like them? – Milah Jan 19 at 15:09

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.