A simple task of user authentication can be quite daunting not in terms of designing and development but in terms of choosing the best way for the product It depends on the stage of the product we are in and also on the type of product Let me try to put my point as a conversation among various stakeholders. Product — — — — - ----product manager Marketing — — — — ---Marketing team Quality — — — — — —Quality assurance team (testing team) Random — — — — — --Random guy Tech — — — — — — — Tech team Product: Guys let's have a short meeting to discuss the new feature we are going to have in our upcoming sprints “user authentication and login”. I am open to suggestions. Marketing: we need to authenticate the user using the conventional method of email and password, we would get the user's email id and I would bug them later if they stop using our product😁 Tech: easy peasy Product: but for that, we have so many steps, I guess we are going to lose users there, dau wou...
This blog is about product, businesses around products, product case studies. I would be expressing my opinion and analysis of contemporary products. This is also an experiment around product related case studies, business case studies, UI UX of B2B and B2C products. I would also talk about upcoming technologies, and how new technologies are going to change the product development testing and deployment. How user navigation is going to change with new and improved capabilities in mobile devices.