Thank you all for the thoughtful conversation around the updated end of screen flow. We are evaluating different options for understanding what kinds of workflows are impacted, the breadth of the negative impact, and possible adjustments to the new behavior. The more information that those who are negatively impacted can provide, the better solution we are likely to come to.
It does seem we have a communication challenge. Do you follow ODK on Twitter/X, Facebook or LinkedIn? We did not get very good response when we made a request for user interviews on those networks and here. We did get better response when we sent out a survey.
Did you know you can subscribe to specific forum tags and categories by using the bell icon at the top of the screen? That will send you emails if you don't visit the forum often. I'd recommend watching at least the breaking-changes and betas categories. We can and should recommend this in more visible places. If you have recommendations on how to reach you and your colleagues, please share.
We have previously experimented with newsletters but never got as many people subscribing and reading as we do here on the forum. Maybe a community member would want to experiment with putting one together again?
Can you please tell us more about your workflow? In what cases are forms complete but not final? Is there a formal review process? Is it more that there are occasional reasons to make light edits like what @seewhy describes? The more detail you can provide here about what needs to be done and why, the better.
This is something we did consider quite seriously. We decided against it because for many workflows this would provide friction in the most desired path. We also considered making it a setting but more settings add complexity and more chances for bugs. As we learn more about workflows that are impacted, we will reconsider these options and others.
This is very related because it ties into community communication and how we release bigger changes. We spend quite a bit of time planning which text in the app we update when to try and get as many translations as possible. With this release, we started early with many different ways to reach out to community translators. We asked for translations on this forum, through all social media channels, and through the Transifex translation platform. We periodically look at newly-available translations and update Collect accordingly. Is there someone in your network that you could ask about contributing translations for the text you need? Our latest call to action is here.
It can be very hard to think through the implications of a feature or concept when considering it in the abstract! That's why we initially try to gather as much information about what users' end goals are and why those goals exist and we are certainly open to course-correcting as we get new information. Thanks for describing the "just in case an edit is needed" workflow. We heard from a number of projects that they want to prevent the temptation of adding a detail later that may be a fabrication or misremembered. But I can see how in your case it might be real new information and that you are not concerned at all about fabrication. Please note that for now, you can continue editing finalized forms from "Ready to send" by tapping on their name.
For all of you wanting to continue editing finalized forms: is there any difference between finalized and sent forms in your workflows? In other words, would it be acceptable to allow edits for both forms that are finalized and ready to send on the device and forms that have already been sent? If we were to introduce something like that, we would likely make it so that Central would show the difference between source and edit for both of those cases. This would be functionality that form designers would need to opt into.