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.

Today I’m pleased to say that ThreadOne is now available. Now that it’s live, I wanted to write a bit about how it came to be, and what’s to come. The History Last summer, I was collaborating with my friends Adam Kool and Gavin McKenzie on an iPhone app. It was our ambition to start a company together, and this would be our portfolio piece. As we worked from our various day jobs, cafes and homes, a communication channel became of vital importance.

Confession time: I was never a very good student. Back in grade school, I was completely average. The occasional A in reading, Cs in math, but mostly Bs. I especially muddled through tests, never really comfortable with the subject matter in an environment that demands the right answer, now. With the clock ticking. Tests all too often felt like contrived situations. If I could grade the tests I had been given in school, I’d consider them average at best!

Ah, the Privacy Policy. It’s that last-second, hastily-assembled legal mumbo-jumbo that you cobble together as your application or web site is launching. It’s one of those assumed obligations that are a thorn in your side: a way of covering your ass, because almost nobody reads them anyway. In the latest episode of Core Intuition, the iOS dev community’s classiest developer, Manton Reece, talked about how he had to generate a privacy policy for his new app, Sunlit.

On the most recent episode of Amplified (starting at about minute 37), Dan talked about how he does web development on an iPad. While clearly not his first choice of platform for development, the iPad is great for making touch-ups to existing sites. He outlined his process like so: Symlink a Git repository to Dropbox Use Textastic to edit the site, owing to the app’s ability to edit files in Dropbox If he wants to commit and push the Git repo to Github, for example, he’ll use Prompt to shell into a remote Linux machine, also running Dropbox, and commit and push from there.