All posts filed under “Developer

What we’ve been up to

It’s been awhile since we’ve posted on our blog and the natives are getting restless.

So what on earth have we been up to these last few months?  A lot!  We built our first iPhone webapp (still experimental, but it’s showing great promise – mad props to the jQTouch team), we re-implemented and streamlined task delegation (to be released in the coming days), we created a framework for internationalization so that Nirvana can render in multiple languages, and we squashed a ton of bugs.

Behind the scenes we’ve optimized countless lines of code, re-factored some back-end data handling, and migrated to new hosting – all in the name of making Nirvana zippier and stronger.

We had hoped to launch our developer API by now but got a bit ahead of ourselves. It’s still slated for release “soon” – but we need to document it properly, really bullet-proof it, and build in some sort of throttling. Better to wait and get it right, we say, than release too early and have a bunch of great 3rd party apps fail because we missed something. We’re working diligently and will announce it when it’s ready.

But enough about that, where’s my beta account?!

If you’ve signed up for a beta account and are still waiting for an invite, here are your options:

1. Be patient and have faith that we’ll get you in as soon as we can

2. Tweet our praises and/or contact us directly to sweet-talk us into creating your account pronto

We figure if you’ve been following our progress closely enough to read this blog post, you deserve an account sooner rather than later.  We’re easy like that.  Give us a shout – we’d love to hear from you.

Developer API

Create widgets, blog embeds, mashups and more.

The Nirvana API utilizes the REST architecture, with requests made via HTTP and responses returned in the JSON format. We may support XML responses in a future release. You will be able to get, add, edit, and delete your tasks, projects and contacts. Calls to the Nirvana API will require both a key for the requesting application, and an authentication token for the Nirvana user. All requests to the API will be handled in the context of that authenticated user. We are leaning heavily towards using the OAuth security architecture, though we have not yet made a formal decision. Your thoughts?

The Nirvana API will be available soon.
Target release date: Late Summer 2009.