search

theheapdump / kite-webapp

web-app for kite trading-bot platform
0 stars 1 forks source link

User Story 22 : Profile Page UI Development - Linked to User Story - 1 #32

Closed theheapdump closed 4 years ago

theheapdump commented 4 years ago

Requirements:

@kshitijbhardwaj , me, and Amit and agreed upon the UI flow. e.g. LinkedIn customer onboarding is a good example. You can as well. try that with a dummy email. (needs email confirmation).

Advantages - It is UI driven than. user-driven. Please do a quick register on LinkedIn to understand the onboarding.

backend will maintain a STATE machine for each onboarding. States are. ( PROFILE & BROKER )

  1. After Registration completes, the User is to be presented with a card - for Profile details

Fields in this form

First Name, Last Name

Small Photo Upload / Avatar - OPTIONAL

NickName

Gender

Birth Date - OPTIONAL

Save / Continue. - send the async call to the backend to. update STATE. to. profile and save profile data

  1. Next present a broker selection card -> select broker drown down -> ZERODHA / ALICE BLUE / etc

  2. In the same card or a new card. (up to UI developer) show the zerodha form fields

TEXTBOX - Enter ZERODHA CLIENT ID

TEXTBOX - Enter API KEY

TEXTBOX - Enter API SECRET

BUTTON - Generate Kite Connect URLs - ASYNC CALL -backend

TEXTBOX - Non editable - Redirect URL:

TEXTBOX - Non editable - Postback URL:

  1. In the above state, there are 3 flows

FLOW 1 - MAY. BE LATER - state remains PROFILE - no async call - redirect to DASHBOARD - blank screen a RED UI. text somewhere on the. top - Broker Information Missing. -> Clickable. -> ROUTE. to. be. decided later

FLOW 2 - DON'T HAVE AN ACCOUNT ? - CREATE ONE. -> First play a official kite developer account creation video and provide a link (FOCUS) for redirect to Kite Developer. -> Video-assisted Kite developer account creation -> user comes back fills the details -> save -> ASYNC call to backend (update state to BROKER) -> Route to dashboard -> Next to be decided later

FLOW 3-> Have the APP details , fill and save -> then same as FLOW 2 -> ASYNC call to backend -> update STATE to BROKER -> Dashboard.

theheapdump commented 4 years ago

WhatsApp Image 2020-10-30 at 00 03 31 WhatsApp Image 2020-10-30 at 00 04 37 WhatsApp Image 2020-10-30 at 00 05 31

theheapdump commented 4 years ago

WhatsApp Image 2020-10-30 at 00 06 13 WhatsApp Image 2020-10-30 at 00 07 48 WhatsApp Image 2020-10-30 at 00 08 46 WhatsApp Image 2020-10-30 at 00 09 22

bevanamit commented 4 years ago

@kshitijbhardwaj @anmoldeep0123 : please comment if there are changes to the screen as per you guys decided.

theheapdump commented 4 years ago

my thought was @bevanamit , it should be quite similar to LinkedIn as much as possible .

bevanamit commented 4 years ago

Then we take the names in 2 parts first and second name... Let's remove the nickname as I don't see we are using it anywhere.

On Thu, 5 Nov, 2020, 12:49 anmoldeep0123, notifications@github.com wrote:

my thought was @bevanamit https://github.com/bevanamit , it should be quite similar to LinkedIn as much as possible .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/anmoldeep0123/kite-webapp/issues/32#issuecomment-722192783, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIF6MYLPRW3HHBWTGVP6IDSOJGZHANCNFSM4TESAC7Q .

theheapdump commented 4 years ago

name could be long - just in case , we will use nickname for communications -on UI and backed - Informal