Brief Update June 19

waytools 2017-06-20 05:00:24 UTC #1

Hi All - briefly, we're working through the points we described in our post last month. These are areas relating to Bluetooth, lala state, and some others. We've settled certain points now and see some nice improvements, but some areas have required new diagnostic and logging tools, so we had to build them. We'll post some technical details next week, but topline, we're mainly grinding through the work for those items learned from the recent user observations.

Thanks to all TREG users for the excellent comments and suggestions. That input from real-world, heavy usage is exactly what drives the train forward to general release.

Thank you

colinng 2017-06-20 05:25:27 UTC #2

Thanks for keeping an even keel and doing the tireless work of continuing to fix issues and build better flows for capturing debug info!

I have no doubt that when you decide it is time for GR, that those who receive a TextBlade will find it as empowering, indispensable (and fun!) as I do!

discokvn 2017-06-20 05:29:04 UTC #3

there's an old joke that goes, "How do you keep an idiot in suspense?"

SamuraiJack 2017-06-20 06:14:08 UTC #4

Nice to know that the folks at Waytools are alive!

I'm thinking of starting a pool on the forums to let people predict how many grandchildren I will have when my TextBlade arrives... And none of my kids are even married yet!

My money is on 3....

@waytools, you'd better hurry, my son just got engaged!

waytools 2017-06-20 06:17:49 UTC #5

dabigkahuna 2017-06-20 07:06:00 UTC #6

I would like to point out something that I think you keep missing. It is based on this statement:

That kind of statement, no matter how accurate, is going to bug people. The reasons are:

There have been lots of variations of that kind of statement
Combined with how a lot of folks don't see the progress, at least not towards shipping, which is what they really care about.

So, they find it irritating. Just something to think about.

Moving on, as we look for next weeks details, what would help (other than giving an actual shipping release, of course):

What are the gating issues? Include anything that, if not improved, would prevent shipping. Even if it is something you expect to be done in a few days (you could turn out to be wrong). After all, if it is fixed quickly, you'll make people feel better when you report that accomplishment.

The hard part is whether there can be any measurable progress given. That can be difficult, depending on details. But if you can do it, it would be welcomed.

Miscellaneous stuff: Is hardware considered to be done - obviously assuming nothing new comes up? If so, have you ramped up production yet so that when the firmware is ready, you have a very high number of units in storage ready for final assembly?

Or maybe more of a generic statement about how long after you initially think you have everything working acceptably. An example might be, "As soon as we think we have the firmware problems solved, we'll continue to test for another X number of days/weeks. If nothing serious comes up during that time, we'll move forward on shipping. It will probably take another X number of days/weeks before the first general release units go out."

This doesn't lock you in to anything since firmware issues is still open-ended. But it gives us an idea of how long it will be to moved from the end of that to actual shipping.

Progress on Android app (or any other OS system)? I don't know what your plans are beyond iOS and android, but I can see a real use to have something for windows, Mac, Linux.

arimendelow 2017-06-20 16:39:20 UTC #7

I agree with everything you said. It's nice to finally hear from @waytools after all this silence, but their post is little more than the sentiment that they've been throwing at us for the past few years (a CRAZY timeline). Us non-TREGGERS want to see real, tangible evidence of progress.

gilli 2017-06-20 22:17:42 UTC #8

...would love to assist in driving the train. Consider me for TREG!

Andy1138 2017-06-20 22:23:46 UTC #9

Awesome! Glad to hear things are moving along!

Scott 2017-06-20 23:04:20 UTC #10

I think you need to reevaluate your scale. I would suggest years/decades not days/weeks>

dabigkahuna 2017-06-20 23:38:30 UTC #11

I'm well aware of the practice of applying high numbers to any estimate. If they say "summer", the comeback is "what year" for example.

But my focus is on more likely things. And since this isn't about when the problems will be solved (a very hard thing to know for sure), I think some fairly precise information can be offered. And we can base some of it on what they have said before.

Treg was originally intended, at least partly, as a final test of the product before shipping. That is, when they shipped treg units out, they thought it was ready to go and Treg was just an extra confirmation, hopefully. Well, obviously they were wrong about it being ready, but that doesn't take away the rest of the plan.

And that plan was - one week of SUCCESSFUL Treg testing would mean moving forward to shipping. Didn't know how much time that process would take before first units went out the door, but we did know it was one week to make the decision.

So, what now? I don't think it will still be based on one week of successful treg testing because they'll want to be extra careful to make sure any trend of good reports aren't just coincidence. But I also don't see it being a very long time. My personal guess would be if they were happy with reports for 2 weeks to a month, they'd move towards release.

It would be nice to know their requirements though. And I'd certainly like some idea of how long between giving the word and actual shipping would take. Just for the first ones, which could just number in the hundreds per day. But once started, ramping up should follow soon enough.

phubers 2017-06-21 06:56:17 UTC #12

Let me help drive that train! Just send me a TREG unit and I'll help push

meanderis 2017-06-21 18:09:57 UTC #13

Since it looks like we are getting close to the finish line, are there plans to increase the size of the TREG group? I've been patiently waiting since 3/13/2015. I'm sure more of us long time customers would love to help out. I've lost track of the number of business trips and vacations I've wished I've had a textblade. I've given up hope of getting it in time for supervising the troop at boy scout summer camp or my summer vacation. Many of us have been reading the forums from the beginning and just looking. Figured it was time to sign up start posting.

dabigkahuna 2017-06-21 20:46:16 UTC #14

They have said it will continue to add people even after shipping, as I recall.

dabigkahuna 2017-06-22 03:18:23 UTC #15

In addition to the items I've listed in my first post of this thread that I'd like to see in an update, let me add one more thing.

We started getting reports today that have some people's estimating shipping changed fro Summer to Fall (so far these folks ordered no earlier than November 2016. Meanwhile, others still say Summer (these folks ordered sometime before early April 2016). We don't know where the line is drawn because not enough people have reported in.

But we sure would like to know what this change means!

Gregg 2017-06-24 00:35:28 UTC #16

Couldn't resist checking one more time to see if @waytools provided a summer update. Pleasantly surprised to see they adopted the train metaphor I introduced on another thread.

Signing off the Forums till it arrives, and hope it beats the NY Penn Station repairs.

dabigkahuna 2017-06-24 02:01:09 UTC #17

Well, we're supposed to get more info next week so, the possibilities (and yes, I'm assuming it will be next week):

Sunday - first day of next week for the typical U.S. calendar. I do not expect anything that soon.

So, looking at other dates, we could still have the Monday review meetings of weekend data and get a report Monday night - but typically after midnight so, actually early Tuesday.

Next we look at ending periods. Friday is end of typical work week, though I think we've seen enough to know they at least work on Saturdays (don't know about Sundays). It also happens to be the last day of the month which makes it slightly more likely than some other days.

Saturday would be the last "official" day of the week according to the calendar. Also the start of July so another logical day to update.

More informally, since many people think of work on Monday as the first day of the week, they also think of Sunday as the end of the week. Which would make Sunday the last possible day to update and meet a reasonable definition of "next week", plus adding the usual fact that they tend to post at the end of their day (or at least the end of the day for the person doing the posting). So that can be 2:30 AM their time.

Thus we should know more within 9 day and 8 hours. Personally, I'm hoping for Monday night / Tuesday morning.

petek 2017-06-24 13:07:31 UTC #18

Meanwhile, for the third straight summer after my initial order, I go on my annual bike tour without the lightweight keyboard I paid for 2-1/2 years ago. Further, it seems much of the recent delays are caused by issues with a feature (jumps) that was not on the original plan, and which I, personally, couldn't care less about.

I get the impression you think this keyboard is going to transform people's lives. I guarantee you, however awesome, it won't work well for many people. Meanwhile these delays are the biggest cluster&@^! I've ever seen in a commercial product.

dabigkahuna 2017-06-24 18:42:03 UTC #19

No, but may transform the typing experience for many people. I'm sure there will be some who make no effort to adjust to it though, or people who have special situations which the TB isn't the best choice.

IPdude 2017-06-26 17:33:21 UTC #20

Hi All -- briefly, I'm working through the request to be included in TREG described in my prior posts. This area relates to a quasi-begging state, and some others. I've settled certain points now but still working to identify more effective ways to get noticed. I'll post some technical details next week, but topline, I'm mainly grinding through the hard work of getting included in TREG.

Thank you