I'm designing an iOS app to order groceries online. I have a doubt about when ask for registration. To proceed at payment you must be a registered user. One can use an app like this several times and I'm unsure if I should ask users to login or register on the first page after opening the app with the option to skip this step, or ask to login or register only when they come to pay.
Having to spend time registering when all they want to do is actually shop distracts the user from their main task and makes them more likely to not want to use it.
Also think about what information the user needs to provide when registering and to be honest they will need to provide the same information if they want to get things delivered and paid for anyway.
So registering at the end would be a natural stage of the users journey within the system, they will need to pay for it, (registering card and name), provide an address for delivery (registering home address) and an email address for the receipt of their shopping (registering email address), so by actually using your app for its purpose they are consequentially registering as well!
Just read this (rather brief) article: http://www.uie.com/articles/three_hund_million_button/
It's about an e-commerce site that was dropping customers due to the registration thing.
In brief, passing the customers through a registration track as part of the checkout ... well, you see the article's title.
Some users mumbled that they didn't were there to build a long-term relationship.
I encourage all of you to read this usability jewel.
I'd ask later.
Some users might be turned-off by requiring to create an account without seeing if the app is something they would be interested in. Especially if the brand is not very well known. By asking later you have a chance to show them what you have to offer so they will see the value of registering.
Agreed with both of the above. If you look at traditional shopping sites, it is good practice to allow a guest checkout, and then prompt the user to register when they are done. This also allows the user to gain an overall impression of your site/service (hopefully positive!) so when they are asked to register they will be more willing to.
Why do users have to be registered to use your app? This may be something you want to reconsider being mandatory (again, going back to the example of guest checkouts). If you decide it is necessary, @MeeMMeeM's point about making checkout and registration simultaneous is a great idea-- as long as users know they are in effect registering!!
I'm unsure of Google's or any other platform's policy, but here is a recent (May 2017) response from Apple's App Store Review for an app. The app sign-up required only a username (which can be fictional), an email address, and a password. No user-declaration of sex, age, or credit card information, for example, was required:
As we discussed, your app has been rejected for the App Store Review Guideline detailed below.
Guideline 5.1.1 - Legal
We noticed that your app requires users to register with personal information to access non account-based features. Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user.
User registration that requires the sharing of personal information must be optional or tied to account-specific functionality.
This app is tabbed, and only two of the currently four tabs require account-specific information. I've reconfigured the app so the new user is not first met with a sign-up screen, and expect to soon re-submit it for App Store Review. To me this policy has its plusses and minuses: One plus is that the new user can poke around a bit, though I've provided plenty of screenshots and a preview video of these behind-the-wall parts of the app to the App Store; one minus is that the app now opens to a tab in the app that is not the one I prefer.