I think most here understand that there is likely a lot of stuff going on to get this to GR that we can only begin to guess at. That isn't the problem. At least not for most of those here.
We see an update announced for the next day (which would have been June 1st). Then we see it delayed to the next day. Okay, things happen, right? Then the comment about the update coming being self-regulating because it really bothers you to not have it done. Yet here we are 77 days since that first "next day" announcement and 65 days since the "self-regulating" comment.
Okay, even with all that, I think most people, while being really frustrated by those things, would still say, "Okay, things happen. We'll wait". But then they also remember that it was just days away back on June 20th of 2018 with similar statements coming after that. And that's where they, understandably, will ask themselves, "How many times can something unexpected come up for an update that causes a last minute delay!"
I'm sure the things you are doing are productive. That isn't the issue though.
My present theory is that you don't want to post any major status update until certain things (no idea what things) are "done". I submit it doesn't matter if things aren't done. Every single update you've ever given was made while many things were still not done.
I've begun working on your last update, taking everything written in it from the top down to just above the part which gives the history of a person's order.
It started out as about 23,000 characters (not words). And that isn't new info in that update only. I think all updates have retained a good portion of what came in a prior update. For example, the Q-bot info was in multiple status updates, unchanged. I'm in the process now of seeing how well I could provide the key information in that update, as if everything in it was new. So far, just by deleting stuff that was more about how great the TextBlade is rather than actual update info, I have it down to about 16,000 characters and I haven't even begun the bigger task of how I can shorted the actual tech update info.
My point being that a lot of basic tech info can be given without extensive detail. I have no issue with details. I love them. I bet you do too. But that can always be added later, if you wish without holding back the whole update.
An example might be (the numbers are just made up": One of the recurring challenges has been the inherent flakiness of BT-LE. Not only the basic tech, but how companies handle it in their systems, which is beyond our direct control. This was causing 5% of our users to serious problems periodically every few days and another 7% to have them more rarely and less serious maybe every couple weeks. We have gotten Apple and Google to make some changes which has helped reduce those numbers and have also found a way to handle problems when they do happen with some special code in the TextBlade so that the numbers above have been cut to 2% and 3% respectively, which we think, considering it is intermittent, is better than other BT-LE keyboards and so good enough for initial shipping."
So, explanation of an issue, some rough numbers of where you were and where you are now, and general comments about how you made it better. But nothing specific such as "Apple changed their stack to alter the order of events" or "The way we changed our code to handle problems better was....".
Trust me. Between me and my father, we know EVERYTHING. I can prove it - just ask anything!