There is an application with which engineers check equipment. Engineers photograph equipment before and after testing. The application looks something like this:

Two buttons for capturing "before" image, and capturing "after" image

The user would have to:

  1. Click the add photo before button.
  2. Take a picture.
  3. Click the add photo button after.
  4. Take a picture.

In my opinion, this is not very convenient and takes a long time.

Are there any other solutions that will shorten the time it takes to add photos?

  • 3
    What problems do you see with this solution? It seems like that workflow is already quite lean. You mention only two taps to capture each picture (open camera, capture picture). That seems like pretty much the minimum possible to me. Commented May 21, 2021 at 16:55
  • Could you please describe how you achieve with this app that engineer doesn't forget to take picture before checking equipment? This could help to answer your question.
    – Serg
    Commented May 26, 2021 at 6:52
  • Photo, this is a prerequisite for checking equipment. Without a photo, the task will not close Commented May 27, 2021 at 13:41

3 Answers 3


It seems like the user will select a particular task that is open, and provide the photos at different times during the process required to close the task. So the complete flow will probably look something like:

  1. Open task
  2. Take before photo
  3. Submit photo
  4. Check equipment
  5. Take after photo
  6. Submit photo
  7. Close task

This is a linear process but it may not be completed in one single step, depending on if step 3 can be successfully completed. So it is possible to design the flow so that there is only one action button to take the photo, but that means you will have to provide some context for the user so that it is clear that the photo being submitted is a before or after photo (because they may need to resubmit a photo for whatever reason). The simplified flow can look like this:

  1. Open task
  2. Take photo
  3. Assign label
  4. Take photo
  5. Assign label
  6. Close task

Maybe allow the user to enter a mode where they can take multiple photos in succession. The first photo could automatically be tagged as 'before', and subsequent photos as 'after'. This is particularly useful if multiple before-and-after sets need to be captured in one session.

Try scanning a multiple pages document with the note app from iPhone to check the flow I'm talking about.


You write "engineers check equipment" and "before and after testing". As noted before, this will typically be a step-by-step description of what to check, or how to test.

If documentation is needed, just put the photo-taking into the sequence as separate steps.

As there is so little information about the business in your question, I'll speculate a little: Why not -

  • scan the equipment's bar code with the camera to start the process (i.e., pick the task),
  • immediately after, turn on the camera to have the user take a photo,
  • on next screen(s) explain what needs to be done to check/test,
  • after last step, again turn on camera to obtain "after" photo,
  • show the user a "review" page to verify what they are about to submit.

That way, you don't even need the user to explicitly start the "photo-taking" step, but it's integrated into the workflow and triggered by scanning a bar code (or selecting a task from a worklist) and by advancing from the last step.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.