@Souirji_Abdelghani Thanks for all your contributions on the forum so far and for bringing up this important issue!
Our goal in the short term with Collect has been to update underlying libraries, fix bugs, and add long-requested features with minimal user impact.
I think we've done a decent job so far. Active installs are up and crashes are down. And when we've been told about a bug in a release, we've been able to fix it in a day or so.
You are correct that there are sometimes changes that require re-training and I know that can require a lot of work your part. That's a problem for sure, but before we make a change in the process, it'd be good to understand how big of a problem this has been for you.
-
Is there a specific example of a change we made that required re-training (e.g., the change in the date/time widgets)?
-
How much work was the retraining? Minutes? Hours? Days?
-
Is the change something you would have caught in our beta program that ships betas one week before the production release?
In general, we've tried to ask feedback on the forum about changes that might be disruptive but we haven't had much response. We want to do more there, so if you have ideas on how we could do that better, please do include that in your response.