Well, QuODK was inspired by the original version of FooODK - so there is a common root there (and my Swahili is better than it was, so I could understand the code). However, whilst there is a lot of overlap in terms of functionality, I think we have diverged significantly! Probably to meet different needs.
The new version of FooODK appears to have some real advantages for analysis (I have not tried to incorporate that into QuODK as it is intended only as a connector). I’m struggling to get it to load data at the moment, but I can see some useful options for checking the dataset and audit log.
My approach has been to ‘grab-and-go’ from the Central Server, whereas I think @Langen_Mallya has a little more finesse . However, for ongoing data download, I think the grab-and-go is a bit quicker to load data into QGIS - I use Append to Layer plugin to avoid duplicates (if there is a chance of overlap with existing downloaded data), and have saved geopackages with the required columns, so that anything extra can be stripped easily (e.g. Note / calculate columns). Not as good, but less coding!
Dealing with entities was a big challenge for me - especially because ODK is agnostic about geometry type and QGIS isn’t! So I had to build some processes around that to detect and handle different geometries and load multiple layers as required. Maybe no need to reinvent the wheel, but it is undoubtedly possible to make a better one…
My code is open-source, so can be adapted (an attribution always appreciated if deserved )
So, FooODK v2.x is based on the experince We have with FooODK v1.x. The work I support, PMEL team and project leads have to supervise community data collection. the current version will avoid downloads, But will focus on simple analysis on data and audit. Also, geotagged images for other applications (like storymaps, google Earth, comms, etc).