challenges
challenges
challenges
There were a lot of open-ended questions
There were a lot of open-ended questions
There were a lot of open-ended questions
I owned the end-to-end user flows and UI design guide creation process. When we started off, there were a lot of What Ifs with very little clarity.
I owned the end-to-end user flows and UI design guide creation process. When we started off, there were a lot of What Ifs with very little clarity.
I owned the end-to-end user flows and UI design guide creation process. When we started off, there were a lot of What Ifs with very little clarity.
design decisions
design decisions
design decisions
product pain point
product pain point
product pain point
Ambiguity? Use placeholders
Ambiguity? Use placeholders
Ambiguity? Use placeholders
Is the onboarding native flow or web-based?
Do we have authentication through OTP, biometric, or some other means?
Will we auto-fetch the phone number based on the SIM card/SMS permissions?
Since we did not have complete clarity about the nature of the data we would have access to, I created flows using placeholders so as to not be a blocker for the release.
Is the onboarding native flow or web-based?
Do we have authentication through OTP, biometric, or some other means?
Will we auto-fetch the phone number based on the SIM card/SMS permissions?
Since we did not have complete clarity about the nature of the data we would have access to, I created flows using placeholders so as to not be a blocker for the release.
Is the onboarding native flow or web-based?
Do we have authentication through OTP, biometric, or some other means?
Will we auto-fetch the phone number based on the SIM card/SMS permissions?
Since we did not have complete clarity about the nature of the data we would have access to, I created flows using placeholders so as to not be a blocker for the release.
dev pain point
dev pain point
dev pain point
User-driven updates? Inform them upfront
User-driven updates? Inform them upfront
User-driven updates? Inform them upfront
Automatic updates were not possible due to technical constraints. Users had to manually refresh the vaccine certificate to check for updates like International Travel Certificate, or Booster Dose details.
The catch?
If the session had timed out, users had to re-login to update. Since this was a multi-step process requiring user input and OTP authentication, we chose to inform users using an icon on title bar followed by a popup to prime them about the steps ahead.
Automatic updates were not possible due to technical constraints. Users had to manually refresh the vaccine certificate to check for updates like International Travel Certificate, or Booster Dose details.
The catch?
If the session had timed out, users had to re-login to update. Since this was a multi-step process requiring user input and OTP authentication, we chose to inform users using an icon on title bar followed by a popup to prime them about the steps ahead.
Automatic updates were not possible due to technical constraints. Users had to manually refresh the vaccine certificate to check for updates like International Travel Certificate, or Booster Dose details.
The catch?
If the session had timed out, users had to re-login to update. Since this was a multi-step process requiring user input and OTP authentication, we chose to inform users using an icon on title bar followed by a popup to prime them about the steps ahead.
legal pain point
legal pain point
legal pain point
Too many edge cases? Keep it simple
Too many edge cases? Keep it simple
Too many edge cases? Keep it simple
There were various scenarios and edge cases to account for with respect to the availability of vaccine certificates.
It was critical from legal point of view to inform users clearly about what data is being fetched and what they can access.
We decided to convey this through subtext and only fetching those beneficiaries with vaccine certificates available to avoid confusion to users and minimise development logic.
There were various scenarios and edge cases to account for with respect to the availability of vaccine certificates.
It was critical from legal point of view to inform users clearly about what data is being fetched and what they can access.
We decided to convey this through subtext and only fetching those beneficiaries with vaccine certificates available to avoid confusion to users and minimise development logic.
There were various scenarios and edge cases to account for with respect to the availability of vaccine certificates.
It was critical from legal point of view to inform users clearly about what data is being fetched and what they can access.
We decided to convey this through subtext and only fetching those beneficiaries with vaccine certificates available to avoid confusion to users and minimise development logic.
HQ + UI pain point
HQ + UI pain point
HQ + UI pain point
OneUI brand standards? Copywriting done write
OneUI brand standards? Copywriting done write
OneUI brand standards? Copywriting done write
Each aspect of the copy across the flows — whether it was the title bar or the tiny subtext below the header — went through many rounds of iterations to strike a balance between familiar terminologies, official terminology and OneUI character limitations.
We picked the text that was consistent with the official Covid-19 PDF from the CoWIN portal.
Each aspect of the copy across the flows — whether it was the title bar or the tiny subtext below the header — went through many rounds of iterations to strike a balance between familiar terminologies, official terminology and OneUI character limitations.
We picked the text that was consistent with the official Covid-19 PDF from the CoWIN portal.
Each aspect of the copy across the flows — whether it was the title bar or the tiny subtext below the header — went through many rounds of iterations to strike a balance between familiar terminologies, official terminology and OneUI character limitations.
We picked the text that was consistent with the official Covid-19 PDF from the CoWIN portal.
UX pain point
UX pain point
UX pain point
Too many actions? Establish hierarchy
Too many actions? Establish hierarchy
Too many actions? Establish hierarchy
There were numerous actions that the user could do with the certificate like view, share, download and so on.
I classified the actions based on factors like criticality, frequency and ease of access before finally choosing the ones that were aligned with OneUI guidelines.
There were numerous actions that the user could do with the certificate like view, share, download and so on.
I classified the actions based on factors like criticality, frequency and ease of access before finally choosing the ones that were aligned with OneUI guidelines.
There were numerous actions that the user could do with the certificate like view, share, download and so on.
I classified the actions based on factors like criticality, frequency and ease of access before finally choosing the ones that were aligned with OneUI guidelines.
Fun fact: I won the Spot Award!
Fun fact: I won the Spot Award!
Fun fact: I won the Spot Award!
