User features between ODK/Kobo Collect and Enketo should be equivalent

Hi everyone,

When you are working with Enketo and KOBO collect you need to deal with a big issue: features between KOBO Collect and Enketo can be really different.

What is the general goal of the feature?
it would make it easier for works with form to have equivalent features between KOBO collect and Enketo so that users can use both indifferently for simplicity’s sake.
There are some features which are very problematic: as the CSV preloads

What are the most likely user stories for how and when this would be used by someone on your team?
How useful would this feature be to other users or organizations?
Most users do not have the reflex of checking on both Enketo & the mobile app before they deploy which can create issues later on.
Sometime you only try you form on Enketo, you believe have an error but same form works on KOBO Collect.
Would make it really easier for data collection to have an identic form for an use on Enketo and KOBO Collect.

I am using KOBO Humanitarian response & KOBO Collect

Thank you to think about this suggestion!!

A basic feature difference for Enketo and Collect android app can be seen here.