UI: High-fidelity Mockup - Login

[foongminwong]

Description

As a student,
I need to create high-fidelity mockup for Login,
so that I can move forward with on the planning stage.

Mocks

Initial idea (per proposal)
Figure 1.2. Login

Acceptance Criteria

Update [Required]

• must have all the fields for BIT system for user login:
  [x] username or email (in case people forget their username)
  [x] password
• must have Organization and Mentor/Mentee radio buttons under "Login as"
• must have Login (for current users) and Register or Sign Up (for new users) buttons
• must have Forgot Password? hyperlink

Definition of Done

• All of the required items are completed.
• Approval by 1 mentor.

Estimation

1 - 2 days

[foongminwong]

@mtreacy002 feel free to edit/insert your proposal Login mock on this issue

[mtreacy002]

Update:

Login page.

link to file

[mtreacy002]

@anitab-org/bridgeintech-maintainers, I think we don't need the radio button for Organization or Mentor/Mentee anymore because an organization must be represented by a user who doesn't have to be a mentor or mentee but can be if they want to. Plus, we don't have separate registration form for an organization (its user representative is the one who will create organization profile). So, can we change the Acceptance Criteria for this issue to remove this requirement? Thanks

[mtreacy002]

Update:

On second thought, I think it's ok to keep the radio button to check if the user is a representative of an organization (so we don't have to query all users data to check if user is rep to get the relevant users_extension table).
So, the latest mockup login I have is as below:

[foongminwong]

Update:

On second thought, I think it's ok to keep the radio button to check if the user is a representative of an organization (so we don't have to query all users data to check if user is rep to get the relevant users_extension table).
So, the latest mockup login I have is as below:

Hmm if you are planning to keep the radio buttons on the Login, based on your latest mockup, it doesn't have radio buttons. If not, your current mockup looks good

[mtreacy002]

Sorry @foongminwong , posted wrong image... 😂

[mtreacy002]

Although, now that I think of it, we can't rely on user on this.Coz, what if the user is naughty and say yes, but actually they don't represent an organisation? Or what if the other way around, the user is representing an organisation but they say no to the answer (maybe they forgot 😂). If we don't give this option (radio button) then, we just have to look into the user record in the user_extension to see if they are or they are not representing an organisation. This way we have one source of truth.. What do you all think, @anitab-org/bridgeintech-maintainers ?

[mtreacy002]

Update:
as per discussion on BIT weekly meeting, Wednesday, May 27th it is decided that we'll go ahead with mockup below

[mtreacy002]

Hi @anitab-org/bridgeintech-maintainers. I prefer if we keep the forgot password feature as a Nice To Have feature and not Required feature. Should I take it out of the Mockup so that it represents what will really work as an MVP?

[meenakshi-dhanani]

Yup. I think it makes sense to not include it in the MVP.

…

On Sat, May 30, 2020 at 8:45 AM Maya Treacy ***@***.***> wrote: Hi @anitab-org/bridgeintech-maintainers <https://github.com/orgs/anitab-org/teams/bridgeintech-maintainers>. I prefer if we keep the forgot password feature as a Nice To Have feature and not Required feature. Should I take it out of the Mockup so that it represents what will really work as an MVP? — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADM6DFPT7FHO7BAEJ6RYQYLRUB23PANCNFSM4NI434BQ> .

[mtreacy002]

cool 👍. I'll take it off the mockup then 😉. Thanks for the input, @meenakshi-dhanani

[mtreacy002]

Update:
now without forgot password link