Chapter-2 Sign Up

This page describes the Sign Up Flow of the Bolbhav Android Application.

Splash screen

Currently, it is a image that is not responsive and dimensions are messed up. We are working on a GIF.

App Narrative Posters

After the splash screen in the sign up journey, a user is shown two posters that explains the crux of the app.

Sign up

After one has installed the application, a user can login using an Indian phone number. They will receive a code in the message that the user has to submit to prove that they own the mobile number. Currently, this is the only way to sign-up. Sending message to international numbers is not integrated. Any phone number entered is automatically assumed to be an Indian phone number with default country code of +91.

Phone number verification code

The phone number verification code is sent via Msg 91 platform. Current template id is: 6650bcb1d6fc050a493cfad2

Code message that user receives

16988 कोड का इस्तेमाल करके बोलभाव में रजिस्टर करें। धन्यवाद, बोलभाव! ["jDkpQ9vqnhq"]

1. The first number is the code.

2. The alphanumeric code in the end is the user's device id that is used to auto-fetch the code.

Triggering and verifying code API

For this, the login API is called to request a code on SMS. In the backend a request is sent to Msg91 to send the message on the user's phone number. We currently do not store the code sent via Msg91 in our database.

Submit Phone Number

{
    "mobile_number": "918340541175",
    "action": "send_otp"
}

Submit verification code

{
    "mobile_number": "918340541175",
    "action": "submit_otp",
    "otp": "08582",
    "referrer": {
        "~channel": "whatsApp",
        "~referring_link": "https://0vx58.app.link/P0dFJoVA9Gb",
        "+is_first_session": false,
        "+clicked_branch_link": true,
        "$canonical_url": "https://app.bolbhav.com",
        "$canonical_identifier": "329",
        "$desktop_url": "https://app.bolbhav.com",
        "~id": "1285899126730720773",
        "+click_timestamp": 1711865035,
        "+match_guaranteed": false,
        "~feature": "referral",
        "~campaign": "Bolbhav referrals",
        "custom": "data",
        "$og_title": "Bolbhav",
        "$android_passive_deepview": "branch_passive_default",
        "+rn_cached_initial_event": true,
        "referrer_id": "69"
    }
}

New User

1. When code is verified, it is checked that the phone exists in the person_table. If not, then a new entry is made.

2. Parallely, a new entry is made for the user in the user_meta table, where the field bolbhav_plus_last_login_at is updated with the current timestamp.

3. Upon login each users is provided an fcm_token (registeration token) that expires after 6 months. Upon expiry, the user is auto-logged out and the user has to login again.

Exisiting User

1. Upon login a new fcm_token (registeration token) is allocated to the existing user.

2. The user_meta table was added on 20th Jan 2024, whereas the person table exists since Feb 2022. So it is possible that users are already present in the person table but do not have an entry in the user_meta table. Hence, when a new user sign up, it is checked whether, an entry exists in the user_meta table. If yes, the field bolbhav_plus_last_login_at is updated with the current timestamp. If no, a new entry is made for the user in the user_meta table, where the field bolbhav_plus_last_login_at is updated with the current timestamp.

Posthog events

On the sign up journey, following posthog_events have been added.

1. splash_screen

2. signUp_phone_number_screen_open

3. 

signUp_phone_number_submit

4. otp_resend_request

5. 

otp_screen_open

6. 

otp_submit



7. signUp_change_mobile_number

Important data to track

Sign up drop off rate

How many people drop off in the sign up journey? Below graph show the data for the May 2024 and 30% drop off at the phone number screen. We need to think about removing the sign up journey.