It’s this simple: I screwed up.
When I tested ThreadOne with my beta users, everything seemed fine. But when ThreadOne went on sale, it got into the hands of a completely different class of user: the ADN private messaging power user.
And ThreadOne, it turns out, can’t handle the kind of volume these people deal with.
Since ThreadOne’s launch, I’ve been anxiously investigating the nature of the crashes people were experiencing. As I circled closer to the cause, it became clear that ThreadOne has a fundamentally flawed networking architecture. I’ve tried a number of approaches to patching it up, but I haven’t been successful.
I’m instead investigating an approach that will see me recompose a great deal of ThreadOne’s plumbing. Early indications are very positive, but I can see that there’s a lot of work ahead.
I was hoping for a quick fix, but that’s looking less likely. And meanwhile, the app remains for sale in the App Store, and I know that for the people most likely to make use of it, the app will be fundamentally flawed.
So I have decided to pull the app from sale. Those of you who have voted for ThreadOne with your money, I want to thank you for your support. But I can’t in good conscience continue selling this to more people who will no doubt be frustrated that it doesn’t do what it says on the tin.
I can’t promise when the new version will be ready. But rest assured: I’m not giving up on ThreadOne. This thing is going to come back, stronger than ever, and I can’t wait to deliver it to you.
If you have any questions about ThreadOne’s future, please send me an email.