Signal App

Last edited 465 days ago by Akinloluwa Adeleye

The error messages on the sign-up page ("Expected hmo to be of type object null, instead found type string") and the reset password page ("Request failed with status code 404") employ ambiguous language that does not effectively communicate the issue to users.

During the password creation process, there is a lack of guidance or suggestions regarding the required parameters for a "strong" password.

In the "What is your emergency" page, the selection element for indicating if the person can talk feels misleading, resembling an actual initiate-call button rather than a selection. A radio button would be more appropriate, providing the necessary visual feedback in a high-stress scenario.

While searching in the "Select emergency type" list, it would be beneficial to include suggested emergency categories based on popular searches or frequently encountered issues.

Within the "Select emergency type" list, a clearer indication of how to exit the list is needed. Consider implementing a horizontal line at the top, resembling a draggable handle, as a more intuitive method to exit the modal.

Incorporating real-time suggestions as the user types in the search field would greatly enhance the search experience, providing relevant options related to the user's input.

The "Location" page would benefit from an option to edit the pickup location, especially in cases where an emergency is being reported on behalf of someone else. Additionally, replacing the "x" icon with a "back" button would be more appropriate on the "Location" page.

In the "Location" page, when typing in the "where are you going to" box, it would be valuable to suggest nearby hospitals or medical facilities based on proximity.

Implementing a progress tracker or stepper instead of an "x" or "back" button would enhance the user experience, allowing users to easily navigate through the flow and providing a clear indication of their progress.

The "Emergency request details" page should include an option to edit the details directly on that screen.

Consider incorporating infographics or suggestions for DIY first-aid ideas relevant to the user's request in the "Processing Request" page. This can help alleviate unnecessary panic and provide helpful information.

On the "Processing Request" page, replacing the "x" icon with a "go to homepage/dashboard" option would be more appropriate, preventing users from mistakenly assuming that clicking the "x" will cancel or stop the process.

Implementing a Google API integration for alternative signup/sign-in methods would greatly enhance user convenience, particularly in emergency situations where time is critical.

Add a new card and detail your task, then drag the card to update its status. Kanban (or card) views can help balance demands and bandwidth to improve workflows.

Clear sample data

⁠

Tasks

Tasks

Pending

In progress

Completed

Include suggestions during password creation process

Update Error messages on the sign-up page and forgot password pages

Update “Can you talk” buttons to radio buttons

Include suggestions when selecting an emergency type

⁠

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.