WT, thanks for the update.
I've been a (more or less, but practicing) patient customer since Jan. 19th 2015. Personally, I like the idea to make a product right before you deploy it to customers. I work in software development as product owner, and I'm also rather tedious to refine the workflow and appearance of a software feature/product before it hits productive environments. I call that "strive for completion" because I consider that an essential part of a complete feature/product. I also call it that way to differentiate it from perfection.
What I noticed over the years in WT's posts and reports is an apparently constantly moving target. After the hardware issues had been fixed, basically there appeared not so much more software defects but rather a change in feature scope: The product had to deliver more layout control options before it could be considered "ready", it had to work in more environments, offer more language options - all of those requirements apparently added over time rather than being part of an initially defined set of features.
While it may be a good thing to notice underway that an essential feature is missing to allow a new product to surge in market, and add this to the product's definition of "ready", for some features there is no reason why one just wouldn't deliver it with a software update. That applies for instance to features which might enable rare use cases not relevant for the vast majority of use scenarios, especially if there are obvious workarounds to cover even those scenarios.
So are you really telling us that we wait more time for you to finish a feature which involves implementing workarounds to overcome limitations of the Bluetooth specification? Why not limit it to 3 devices for a start and add that extraordinary capability in an update? No one would feel this is a bad or even limited product when he/she gets hands on it, and those few who will encounter situations with more than 3 simultaneously(!) used devices will just be happy when you add that capability - they will hardly have felt a sensation of deficiency or incompletion before that.
It appears that what you strive for is "perfection" in the worst sense of the word - a perfect product that covers all imaginable use scenarios and thus will never be ready to ship because you keep identifying features to cover yet another use case/scenario. I get the impression that the product long had a feature set which was "complete" - meaning that it had enough capabilities to just declassify any other "portable" keyboard on the market and for many users, render stationary keyboards obsolete. A focus on quality controlling this feature set might have enabled you to ship it quite a while ago.
In case my assumption is wrong, and all those features were part of your initial master plan, you did not really tell us the truth from the beginning concerning the development status at time of purchase, and the assumed remaining development time. In case my assumptions are correct, may I petition for shipping just a high-quality complete product to us? Pretty please?
Thank you for all the passion and tedious refinements you invest in this product, and REALLY looking forward to using Textblade.