Onboarding Flow | Identity Service | Join Section

[lakshayman]

The onboarding flow commences when the user signs up on the RealDevSquad website. The onboarding flow consists of the following:

• Getting the details of users like introduction, why they want to join our RealDevSquad, and their location details.
• Asking the user to make their Profile Service.
• If they made the Profile Service, they should get the link to our Discord Server.

So, we have done some work listed below in Identity Service and Join Section until now. We are using these two to achieve above mentioned.

IDENTITY SERVICE

What is done

• Identity Service is in the working stage, user can link their profile service with identity service and can push their updated data to the approval flow.

What needs to be done

• Eventually, when there will be a large number of users, the identity service can go down because of the lambda timeout. As it's profile call takes too long, we are trying to make them parallel. (Parallel profile service calls identity-service#124)
• We have to write tests for the identity service. We have a testing setup ready looking into setting up mock data. (Fix API mocking in verify function tests identity-service#125)
• Updating the data field that the user calls its profile data. (To be discussed with Ankush)

JOIN SECTION

What is done

• Users can add details to the join section and share the link with Ankush.

What needs to be done

• The last page tells the user to share the link with Ankush and he will send the invite. But instead of that, that page should tell users to make their profile service and the page itself or page link shared with Ankush should check if the profile service of the user is linked so that Ankush can check from there only. (Should be decided by Ritik) (I think we can work on this Parallelly without waiting for the UI changes that are currently in progress on website-my identity page which helps in linking profile service and identity service).

More details can be provided by Ritik.

Questions

• We are asking for the name of the user in the signup flow, in the join section, and in the profile service. Don't you folks think it's redundant?