Does user need to register?
This depends on how you deliver your PWA app to users and what is a purpose of your app. There are ways to avoid registration step.
The best practice for getting maximum installations is to avoid requiring users to do extra actions by a user, including registration. This can be achieved with the Mobsted mobile app maker. In general you first need to get the app and the communication link with your user and only then ask for any kind of registration credential if whatever received with the com link is not enough.
How to get more users by doing less steps
Use the following techniques to achieve maximum user base installation rates with the Mobsted PWA builder.
Delivering your app with a private SMS link or a QR code may not need any additional confirmation, since you have confidence who is the person accessing the app. Using a link in SMS is essentially a best confirmation that the phone number is correct. Mobsted has built in security measures to ensures that no other person can access this private link. Please refer to the User invitation step for more info.
When using a common (not private) access link in a form of a QR or a common link placed in your online ad you will have two choices. One is to let a user into your app without extra steps and to require registration only at some point, for example, browsing your mobile shop catalog at first and asking to register only upon checkout. Two is to ask for inputing some credential right away in order to access data from a common link, for example, if you use Mobsted m-PWAs for servicing telecom customers, you would want to prove the identity.
Here is how to set it up - SMS invitations Please NOTE that acquiring a user may also be a priority to any kind of registration with the m-PWA system. Since you can initially establish a link between your and user and only then Push notify a user to enter a phone number or anything needed to establish the identity. Please refer to a section Setting up the Widget and Using Social Networks for App Distribution.
When using a common (not private) access link in a form of a QR, or that same "common access link" placed in your online ad, you will have two choices.
- to let a user into your app without extra steps and to require registration only at some point, for example, browsing your mobile shop catalog at first and asking to register only upon checkout.
- to ask for inputing some credential right away in order to access data from a common link, for example, if you use Mobsted m-PWAs for servicing telecom customers, you would want to prove the identity first.
Logged in user, saving the app
Many websites show users a pop up with a link into the app store, making user go through downloads and registrations, sending users through a simple marketing funnel. But funnel is funnel and a great many users are lost at each extra step. This problem is solved perfectly with the Mobsted PWA (read on What is Multichannel PWA). There are two possible scenarios and solutions:
- User is already logged into the website with, say email and password. How smart can it be to send him to the app store for a download and another login? The right PWA solution in this case allows user to save the app right from within the website, with all the ID keys intact, so that next entry through a saved app will allow a user to proceed into his/her account right away.
- User is NOT logged into a website in any way. The right PWA solution will allow saving the communication channel BEFORE the app itself (read on How to Distribute the App). Only then it will ask for credentials and if none are given it could come back to user with a Push message reminding to register, when necessary.
Reminders of extra credentials needed
There is also a powerful option of not asking all the credentials right away. If user saves the app and opens a communication channel, the platform can be set up in a way to request all the needed data in portions, making the process less tedious for users. Just filter for the fields you want filled and set up periodic or action based reminders for users. So see how it is done, please refer to the sections Smart Filters and _Triggers_.