How we shifted 6Wunderkinder to Wunderlist, again

With Wunderlist we've already seen many repeat users and have daily users adding new tasks, especially during the week. With Wunderlist 2 we will have more features that will help grow this.

Fred Wilson wrote about user metrics, he called it the 30/10/10 rule (http://www.avc.com/a_vc/2011/07/301010.html) - 30% monthly active users, 10% daily active users and 10% new users each month. We can apply this rule to Wunderlist, but as we're in the 'task' market, we generally have more monthly users than daily users - because the product is more optimized for weekly use.

It's a nice, pithy answer to give, and in general you shouldn't rewrite a backend "just cause". However, Wunderlist's backend was built with the intention of being a bit of a prototype, and the skills on the team are vastly different from when it was written (in PHP) compared to where we are now (using mainly Rails with a little Node.js in the backend).

In addition, contrary to Spolsky's claim, unmaintained code does rust, or "rot". Libraries you were using might go unmaintained in newer versions of a framework that fixes critical vulnerabilities. Code that held up well to thousands of users doesn't necessarily when you're talking about millions of users. Fighting code/app entropy is a real thing.

But we're taking steps to make sure this backend neither suffers from the "second system effect" (we got that out of the way with Wunderkit ;-)), nor simply needs to be rewritten again in a year or so. Spolsky is correct that in general, code is harder to read than write - which is why we're writing Wunderlist 2's backend to be easier to read at the cost of extra work up front. Strict conventions, enforcing documentation, challenging any code that isn't the clearest way to express the problem it's solving - well, we'll have an engineering blog post to discuss our "Pull Request Parties" and other related process improvements in depth at a later point in time/

The short version, though is that the WL2 backend is probably the most beautiful, readable codebase I've ever had the privilege of working with. Of course I'm more than a little biased, but hopefully the proof will be in the pudding when we launch it out into the world.

At one point, the web and API team were a little more intermeshed, but this had the unfortunate side effect that the web was a de-facto a "privileged" client, while the other clients were like second-class citizens. These days, the Rails app serves no human-readable web interface, only a RESTful JSON API. In fact, the Web app uses CORS to speak to the API on an entirely different host! There's literally no overlap whatsoever between the codebases, deployments, or teams now; the web client has exactly the same status as the Mac, Windows, iOS and Android clients.