User Feedback

[finger563]

(original document: EVAL APP REVIEW.docx )

Brandon and I reviewed the Smart Drive Evalulation app today. We evaluated the app for about 2 hours at Barton Creek mall on a carpeted surface. We reviewed the turtorials/videos and then Brandon and I both took turns doing trials with and without the Smart Drive. For each trial we did the same track, approximately.

RESULTS/COMMENTS:

---

• The videos/tutorials are helpful resources and should also be included into the PushTracker app

• The “Connectivity” title may be better titled “How to Connect” or “Connectivity Overview”. This would help differentiate whether the app is actually connected vs how does one connect to the various devices ( aab88c7 )

• On the topic of connectivity, there is no indication that the Eval app has to be paired to the pushtracker except for when you try to start a trial and it asks for you to pair. This can be confusing also for the reason that there are 2 apps and one might think (as we did) that you pair to PushTracker app and that talks to SmartDrive Eval app (Add First-Run Instructions #251)

  • Can add a button for tips/directions (Add First-Run Instructions #251 )

• When referring to the “app” it may be better to include what “app” is being referred to (e.g. pushtracker, eval, both?) (396ef51)

• Add somewhere to have only one app open at a time (5b9cc37)

• There is the goal of getting rid of the PushTracker App

• The tracking feature is great. It could be improved if the GPS was more descriptive or included a map with pins or both? ( Map View for Demo Location #185 )

• The sliders for speed and accuracy are difficult to move because you have to hold it down and then slide. It makes sense because if you swipe quickly it changes the page, but is there a more intuitive option or ability to decrease the sensitivity? (look into slider sensitivity / controls on carousel pages #284)

• If you don’t complete a trial completely you lose the information you did complete. Is there a way for this to save in the app as you work through it so you don’t have to start over if a trial fails or is completed for some reason (Add ability to resume evaluation #190 )

• Is there a maximum distance the evaluator can be away from the user without losing the connection? (307513a)

• The push counting is very inaccurate. We pushed and didn’t push the PushTracker counts weren’t close. For example, with the SmartDrive on and performing no pushes it recorded 4-5 pushes (maybe these were the taps?) and without the SmartDrive when we pushed 25-30 times it only recorded 14-17 pushes (handled by PushSettings PushTracker Settings Control Page #186 and version 1.6 of the PushTracker Firmware)

• The coast time metric is a little confusing and also will be inaccurate if the push tracking is inaccurate. The coast time is defined as the amount of time the push drive is engaged divided by the amount of pushes performed during the time the push drive is engaged. Should anyone really be pushing while the Smart Drive is engaged? (Change to reporting average speed instead of coast time in the trials #241 )

• The app measures distance in meters. Should we change this to feet since this is the US market?

• Is there any way to save the trials locally within the app (aside from sending the email) ( Add view for evaluations #191 )

• Is there a way to identify each trial without using user identifiers. For example, can the email have a time and date stamp? Are we concerned at all about clinicians using identifiers or is that their concern?

• It would be helpful to have a “next” button or some cue to move to the next screen during the trial (18454ad)

• Out of 8 attempted total trials we had an issue starting 2-3 times when connected (timeout!) and 1 time stopping (resulting in us having to exit the trial completely and losing the rest of the data, see bullet 7)

• Starting and stopping the trial takes about 10 s. For a user this may seem like its taking too long or not working. Can this be improved? If not can we use a timer to let the user know its moving towards completion or some other way to notify them (963ac53)

Feedback Update 2018-11-01

• The push tracker settings adjustments don't seem to be working well at all. Don't match Push tracker even if you click OK. You can make changes and hit save . Exit and go back in and nothing has changed. (Make Settings service that the Settings / Trial pages can use #280 )
• Also email opens but quickly crashes after completing Eval but works fine after you go back to saved evaluations. Then it emails out fine. (email service crashing when used from eval but not when using eval-list button #282)
• The summary when you rate ramp and incline difficulty needs to have an unable to complete ramp or incline when the slider hits 10. (Add unable to complete buttons to trial and summary #281)
• Ramps/ inclines I believe should be one . (on trial / summary pages consolidate ramps & inclines into single item #283)

[finger563]

We will need to go through this and determine what issues / changes need to be addressed (that aren't already issues)

[finger563]

More feedback from Brandon:

First chance to play this week. This pops up all the time even during trial. The push tracker settings adjustments don't seem to be working well at all. Don't match Push tracker even if you click OK. You can make changes and hit save . Exit and go back in and nothing has changed.
Also email opens but quickly crashes after completing Eval but works fine after you go back to saved evaluations. Then it emails out fine.

Changing PT settings in the Trial part worked though and the advice of 3/15 for me was SPOT ON in counting my pushes !! I mean really spot on.
I also saw that it looks like we fixed the distance to be equal to the with SD total on the without automatically.

The summary when you rate ramp and incline difficulty needs to have an unable to complete ramp or incline when the slider hits 10.

Also ramps/ inclines I believe should be one .

[finger563]

Now that all of these tasks have been either completed or addressed by other (linked) issues, I will close this issue.