It's time to return to our regularly scheduled status updates. We're multitasking pretty heavily, but most importantly, we're catching up and beginning to have tangible things to share. Naturally, not all of this is exciting, but we feel it's important to share what we're up to.

Receiving feedback is a time-consuming process. Unfortunately, even the most eloquent and brilliant feature requests aren't guaranteed to make it into an application. Every developer or team has to choose their battles, and while customer requests carry weight, they aren't the only factors. We've put together a list of the four factors we use to decide if a feature makes it into production.

One of the most difficult aspects of creating a new product is deciding which features are necessary for launch. Leaving out features can make you uncomfortable. However, there's a point where you should be more scared of adding features than leaving them out.

While we still don't have much outwardly visible progress, things are really starting to pick up steam on the issue tracker, and April looks like it will be one of the most exciting months yet.

We haven't made a lot of outwardly visible progress, but there's a whole lot going on behind the scenes. We're starting to pick up steam, and things are looking really good.

In the interest of consolidation, we've aggregated links to all of the posts about the design of the issue tracker. Going forward, they'll all be posted here, but this is a good summary of the progress thus far.