A quick post to let N1 users know that the “blank screen” bug in N1 mobile has been resolved. So if you’re logged in, hit refresh to load up the latest version. We also tweaked a few things so that N1 (in general) consumes less resources server-side.
It’s been a bumpy ride, but we’re finally back on track! Nirvana has been migrated to new, beefier servers — a bit sooner than we were planning for. But now that it’s done we have room to breathe. With the boost in capacity we feel comfortable letting in all of the folks who have been stuck in the beta invite queue for weeks (thanks for being patient).
We lost a few days of development time, thanks to the emergency migration. But hey, we actually pushed a release out a day early (build 136) once we realized that we were pretty much spent on energy for the week, given the unexpected all-nighters we were pulling to stabilize our infrastructure.
So what actually went live this week?
New and Improved Rapid Entry
- rapid entry text field now accepts #tag notation for adding contexts inline
- for example: finish this to do #work
- or maybe: finish this too while you’re at it #personal #due next friday
- or even this: clean out the attic #project #star
- more to come
Desktop Browser UI Annoyances Fixed
- clicking on “focus” star icon when editing a task no longer cancels out
- project due / scheduled dates are now properly captured when editing via project view
- rapid entry textfield no longer “freaks out” under certain conditions (chrome 9 specific)
- new pretty inbox icon (this one’s for you @Slith_hideout)
- some css niceties here and there
- recurring tasks engine (for unit testing in production)
- parallel vs sequential tasks (ditto)
Looking forward to relaxing a bit this weekend, and then attacking our list of new features for the next release first thing on Monday. Thanks everyone for sticking with us.
Production web and database servers have been successfully migrated to new hosting for a major boost in capacity. We will continue to keep a close eye on things throughout the coming days and tweak for performance as needed. Thanks everyone for tweeting us encouragement throughout the evening. :-)
It’s been a rough couple of days and I think the team deserves a little shut-eye. Better to have fresh brains in the morning. A more in-depth blog post awaits.
Thank you and good night!
We’ll be performing server maintenance tonight, starting at around 9:30pm ET (Feb 16). The maintenance window is expected to last about an hour.
Please follow @nirvanahq on Twitter for updates. Thanks for your patience.
Nirvana is back in active app development after several weeks of team reshuffling and infrastructure planning. As some of you may know, Nirvana is an offshoot of plu, a web agency — and sometimes as the agency side of the business gets busy, resources have had a tendency of getting diverted towards keeping our client work on schedule, at the expense of Nirvana progress. Thankfully, we now have some bright new faces to help keep the workload from crushing us, plus we have a commitment to ensure we always have enough resources devoted to active Nirvana (N2) development.
We are adopting an every-two-weeks development / release cycle. Our old release-when-new-features-are-ready model, we’ve realized, wasn’t providing the steady-stream of regular updates, fixes or visibility that we all want. Constraints can often be a good thing and time-boxing ourselves to two weeks should also help us stay focused on the prize.
So what are we working on for this Friday? After combing through, no kidding, over a thousand support requests, we came to the conclusion that we can no longer ignore what we had considered minor UI annoyances, but in the real-world have been driving people mad. Like when task editing cancels out when clicking on the star icon, or due dates not being saved under specific project editing views, or ampersands causing all kinds of havoc in tagging… Where there was a workaround we tended to ignore these problems as we were focused on other issues. But as they say, quality is the absence of negative cues, so it’s high time that we restore the bar to where it should be.
The rapid entry textfield will accept #tag notation as in N1, but we’ve also added syntax for adding due dates and start (scheduled) dates, effort (time/energy) and more.
The recurring task engine will be put to the test in production during this release cycle, with the goal of having recurring tasks as a feature ready for the following release.
Changes to support a proper unified next list are in progress. (why can’t we get our act together on this already?) Will let you guys know the prognosis via the comments as we get closer to Friday.