Call-for-Code-for-Racial-Justice / Incident-Accuracy-Reporting-System

Incident Accuracy Reporting System (IARS) is a Content Management application that addresses the issue of transparency surrounding police incident reporting by allowing witnesses and/or victims to directly submit evidence (images, videos)
Apache License 2.0
65 stars 26 forks source link

Mobile App Feature Request #96

Open nitekon1 opened 2 years ago

nitekon1 commented 2 years ago

A brief description of the feature or enhancement you'd like to see:

A clear and concise description of what the feature or enhancement is, Ex. Using this tool be would be much easier if [...] Creation of mobile application.

How will this feature be used?

A clear description of how, who, and when this feature would be used. Ex. User A wants to create a new Incident [...] To discuss, plan and track creation of a mobile application.

What is the impact of this feature/enhancement?

Describe the impact of this feature or enhancement, how will it help users or adoption of this project. Ex. All users will be less frustrated when [...] Close requirement of major component of project.

Acceptance Criteria

What does it look like if we've implemented this enhancement or new feature correctly? Ex. User A was able to create a new incident 5s faster than previously [...] Mobile application has been created and incident submissions work as expected.

nitekon1 commented 2 years ago

Adding flow diagram for mobile application IARS Mobile App Flowchart - Page 1 .

nitekon1 commented 2 years ago

Referring to Draw.io file from design session. https://ibm.box.com/s/fkd68uyjtdtu2t04e6jrcvykm5fkp1xg

To view: 1) Download file 2) Goto -- https://app.diagrams.net/ 3) Select Device 4) Select Open Existing Diagram 5) Select file

nitekon1 commented 2 years ago

Attaching screenshot of home screen from app design. image

nitekon1 commented 2 years ago

Attaching initial screenshot of home screen from mobile app. image

swith004 commented 2 years ago

Comments after testing mobile app:

  1. After selecting that the reported incident isn't live, user is asked to enter date and time:

    • Date format might be confusing, as it is in DD/MM/YYYY format (as opposed to the more common MM/DD/YYYY format)
    • Date format allows user to enter date in the future, which should be prevented
    • The Time field asks for manual input, and is strict with inputting a space for "am" or "pm" - different input method should be used to avoid this
  2. When selecting media:

    • When selecting camera, there are 3 icons: switching between front and back camera, image, and a reel(?). Selecting the third button (the reel?) did not work for me
    • After successfully attaching media, it was not clear to me that clicking on the media would remove it, which could be quite bad if the user is taking photos or video live. I had suspected that after attaching, I would select media that I wanted to include or exclude (which would be indicated by a checkmark), which I think would be preferable than the media being removed altogether
  3. When describing the incident, the "next" button is disabled until after the user clicks a spot on the screen outside of the text field, which wasn't immediately obvious. Therefore, I was wondering why I couldn't submit, or what if any requirements were necessary to enable the next button. The "Next" button should become enabled after any text is inputted to remove this confusion

  4. On the submission page, there are two tabs: Choice and Details

    • Choice can be a little ambiguous as to what choice the user is making, especially since the details tab is always present, regardless is the "choice" the user selects is "no."
    • To remedy, perhaps something along the lines of "contact" request" is a more appropriate name, and then after selecting "yes", a form should be displayed on the same page. The details tab should therefore be omitted in this scenario.