Improve UX flow for map widget on mobile device

[stijnvanhoey]

When adding a custom location (the aim is not the 'current location', but some user-selected location), in the online map widget, the flow to submit flow is not clear as our test users are intuitively choosing the 'get current location' button instead of the return button:

Would it be possible to change the 'return button' into a 'Confirm location' to improve the UX of the submission. Note that this would also improve the UX when users actually want their current location to be used.

Whereas we do understand that timing is difficult, we got this feedback from our user group in preparation of a large campaign that starts on Saturday. If you give me some direction on where I can find this component or widget, I'm certainly willing to collaborate towards a quick fix.

[tiritea]

Are you using Enketo or KoboCollect on your mobile device?

If Enketo, this needs to be a new feature request for https://github.com/enketo/enketo
If KoboCollect, this would probably first need to be a UX change to the upstream ODK Collect: https://github.com/[getodk/collect](https://github.com/getodk/collect)

In either case I dont think this is a KPI issue per se.

[stijnvanhoey]

Thanks for the quick reply. We are using https://ee.kobotoolbox.org form (URL), so kobocollect I assume, but not the android app. Users open the form on their phone and whereas the form works responsive, our users were not able to correctly fill in the form (map-placement widget part) or just gave up.

In either case I dont think this is a KPI issue per se

I do understand this might not seem to have high priority at first. However, I do think this small UX adjustment (based on real input of users) can have a big impact on success rate. Maybe converting the <- symol to a checkmark could solve this (without much language-locale work).

If this is not Enketo and not the odk-collect android app, where to look for this kind of adjustment?

[tiritea]

...kobocollect I assume, but not the android app.

KoboCollect is the (only) Android app. I therefore imagine you are using web-based forms; ie Enketo (and presumably on an iOS device of some sort). FWIW Kobo uses the same Enketo web client as, say, ODK Central. So you'll pretty much see the same behavior no matter what backend (Kobo, Central, ...) you are running against.

So this is basically a feature request against Enketo, or minimally a custom patch against the version of Enketo that Kobo is presently using. Its not really a KPI issue per se.

You might also consider porting this - as it is basically a UX feature change suggestion - to either the Kobo Forum Suggestion Box, and since its about Enketo in general, and/or the similar ODK Ideas Forum.

But can you post the specific form you are using to ensure others can reproduce exactly what you are seeing.

[stijnvanhoey]

You might also consider porting this - as it is basically a UX feature change suggestion - to either the Kobo Forum Suggestion Box, and since its about Enketo in general, and/or the similar ODK Ideas Forum.

Thanks a lot for the suggestions, I'm not aware of the underlying structure and codebases. I'll move the discussion to the forum

[tiritea]

You might also consider porting posting this...

D'oh

But yes, this is a UX change request that probably deserves a Forum discussion.