1. What is the general goal of the feature?
Simplify the server configuration experience. Currently, the three available server types are "ODK Aggregate", "Google Drive, Google Sheets", and "Other". "ODK Aggregate" is confusing for folks who use ODK Central or any third-party server. "Other" is confusing because it's the same as "ODK Aggregate" with the added possibility to specify custom OpenRosa endpoints. The "Other" name suggests this is a whole different kind of server but it's really not.
Mockup of the proposed changes:
We intend to remove custom server paths in an upcoming Collect versions. Analytics show that this is rarely used. It's unclear why an alternate server would implement the
submission endpoints but give them different names. If you use custom server paths, please let us know why.
2. What are some example use cases for this feature?
Folks who don't configure through a QR code need to go through this settings screen. Simplifying it should help the onboarding process.
Simplifying server setup is also a step towards multiple user profiles or client-multitenancy which has been alluded to in posts like @chrissyhroberts's Server URL shown on home screen / multiple servers switch with colour change or Have Collect exactly match the forms on Central.
Deprecating settings that are not commonly used will simplify the settings key/value standard that we would like to publish for all ODK-compatible tools to use.
3. What can you contribute to making this feature a reality?
Project management, development.
Please share if you have any feedback! This was briefly discussed during the latest @TSC call but we didn't have much time for discussion.