Update UI design as per mockups #42

ekigamba · 2019-05-03T07:56:24Z

rowo · 2019-05-11T01:57:23Z

@ekigamba some more detail on above flow with the caveat I haven't looked at where this is technically recently, so if anything works differently let me know:

Initiate screening step is the same for both the sending (Roger) and receiving (Sam) devices.

For the sending device, once they tap "Send data", a dialog appears to say it's looking for a device to send to.

For the receiving data, a dialog appears to say it's looking for a device to receive from.

Once the devices find other devices looking to send or receive, they switch to new states. The sending device's camera is enabled and the name of the device detected that wants to receive is shown.

The receiving device's screen shows a QR code and the sending device's name is shown.

The next step is showing a dialog when the partnered device choose to skip. This is only optional if the sending device is the one that wants to skip, but seems to me required if the QR (receiving) device chooses to skip.

If the receiving device chooses to skip, the sending device sees this dialog:

If the sending device chooses to skip, the receiving device sees this dialog:

Once both devices agree, they see progress. I'm not sure what information is possible here, but a percent or client number of records count could make sense:

At the end, you get a success screen. Information that could show here are number of records updated perhaps or maybe just the official time of end sync.

ekigamba · 2019-05-13T15:35:23Z

@rowo

I also need a :

Transfer fail screen because we expect the transfer to fail sometimes. It will be the same as the success screen since there might be some records that were transferred before the failure.
Authentication failed UI in case the other device rejects the connection
Authorization failed UI - Authorization can fail if the two devices are not on the same team

COMMENTS ON DESIGN ABOVE

I currently do not have a find-fail step in the app right now
Step 4 currently does not work as detailed in the design. Confirmation of the connection has to happen on both devices since it is a security risk to both. I think this needs discussion. However, I like the way you've described it, seems easier. What do you think?
Designs are good, I can change the remaining screens on the app to look as in the design once they are final

Once both devices agree, they see progress. I'm not sure what information is possible here, but a percent or client number of records count could make sense:

At this point, showing the details progress such as percentage might not be technically possible. I will have to look at it a bit more

I have provided the Wcaro apk so that you can have a bit more context on what will be sent and the information available during the syncing and after.

rowo · 2019-05-14T12:58:46Z

@ekigamba

We should discuss the security risk for the connection confirmation. Not sure who the pm is on this.
I don't think progress detail is completely necessary right now — a spinner is okay in that case. If that is the case, it would be nice to give a rough sense of how long this process would take in a time range format i.e. "This usually takes between 1 and 3 minutes. Please keep the phones together during the data transfer process."

I'll put up screens/assets for the fail screens. I think they'll use the below icon with different labels.

ekigamba · 2019-05-14T13:33:08Z

@rowo

Carolyn is the PM but Matt's taken over while she's away.

For progress details, I do not have a good idea of how long the process would take. It depends on several factors, the most important of which I do not have information about to calculate the time.

Can you provide the options for progress details and then we can see which one is technically feasible, has the least LOE & most appropriate for the user experience & final product?

Brief explanation on the above

Calculating time requires knowing the amount of data that is being transmitted by the receiver and being received on the sender. Data being received on the receiver is what we do not have as of now, I'll look at it to figure out what is possible & accurate since.

ekigamba · 2019-05-14T14:22:03Z

@rowo,

I just looked at the progress details and it is possible to show the percentage progress of the current batch.

The transfer works in batches eg. 250 records are sent for each batch until we have no more untransferred records. In this case, we can tell the progress of a single batch easily without much effort

rowo · 2019-05-14T15:25:17Z

Notes from our brief call:

Include a "start transfer" step in the mockups after the QR scan so each user has to confirm to start the transfer and it doesn't go straight there after QR scan.
If both sender and receiver decide to skip the QR scan, it can go straight to the above start transfer step without entering a code — as long as the OpenSRP username is displayed in that start transfer step.

I will update the above workflow to match. Edit: slacked @ekigamba some error messages for feedback. Edit 2: Below is a new flow with the above changes. I added step 5 and changed labels in step 3 and 4.