Thank you for pointing to social media sources. I have subscribed on LinkedIn and will try to keep up with the news.
Regarding the translation, I have checked and looks like the current version of the app has been translated into several languages almost completely. The missing languages are indeed country-specific. But I guess this work is community-based and we cannot expect a vast coverage. I will try to contribute as much as I can and will ask my colleagues who speak the missing languages if they can help out. But as I understood, all translations go through beta process and it can take some time to have them in the final app. How long does it approximately take to role out a translated app version after the language was added in Transifex?
Our workflow for a cross-sectional population-based survey (STEPS):
data collector visits a household (HH) (can visit 3 times if people are away and needs to save and reopen the draft form marking the visits) > opens a blank form starting with location and IDs > enters HH members of a specific age range > does a random selection of the participant from HH members > proceeds with the interview (STEP1) > proceeds with the physical measurements (STEP2) > records GPS coordinates > finalizes and sends the survey (the latter is done automatically by ODK Collect)
When the data collector cannot get a signal from satellites to record GPS coordinates inside the HH, he/she saves the form, gets outside and tries to get a better signal there.
Thus, there are two main cases when the data collector needs to save the form as a draft and reopen: 1) during multiple visits to the HH, 2) when GPS coordinates cannot be immediately recorded. The third case (rarely happens) is when the survey is paused for whatever reason, saved as a draft and continued at a later time.
From our experience, the issue of tapping the wrong button to accidentally submit the survey was mostly done in the second case - GPS coordinates. The data collector could accidentally finalize the survey and send it before recording the coordinates. The GPS question is not mandatory, since it was often very difficult to get a signal indoors or in a remote area. Therefore, data collectors had an option to either try several times outside the HH or submit some a their completed surveys without GPS coordinates when even outside the GPS did not work.
However, this year, we have introduced a change to the forms, upon switching to a new version of ODK Collect, which allows to "warm up" the GPS when opening a blank form (using start-geopoint). We also adjusted the accuracy of the geopoint. So, these changes have drastically improved the recording of GPS coordinates inside the HH, which could potentially allow us to make the question mandatory. Although it needs to be tested on several surveys to see the rate of recorded coordinates.
Please note that only specific app menus / elements are visible to the data collectors (the rest is password protected by the admin). Thus, they cannot edit finalized and sent forms.
I would like to add here that we would really like to see the updates to ODK Central to allow us remove test submissions, which are done during the data collectors training. Currently, we have to mark them all as "rejected" and filter out during data cleaning, which complicates the process.
The second feature that is really needed is the possibility to remove any old or test projects with forms as well as individual forms. The latter are currently can be put in trash, but it is not automatically emptied. So, emptying it manually should be allowed. Of course, all removal should be done only by admins.
Just FYI, we self-host the UAT and PROD instances of ODK Central on our servers.