Document Actions

Roadmap

by Édouard Mercier last modified 2008-11-01 10:30

TooDo is still at an early stage and does not take benefit from all the potential of external web services. We list here what TooDo intends to propose in the future.

The forthcoming/on going development tasks

Adopting a "eat-your-own-dog food" philosophy, you can take a look at the current development tasks list here.

Notification conditions

TooDo already offers the opportunity to define time-based reminders, geographically-based reminders. But this can be much harmonized and enhanced. TooDo intends to be notification-condition centric, i.e. propose the user to define as many and/or-conditions that are being checked in real-time, in order to determine whether a reminder alerts should be triggered.

  • Notification based on the current user context ("Working", "In an interview", "On the phone", "Walking", "Driving", ...) will be proposed
  • Notification based on time frames will also be proposed, repetitive or not. Example: every other Monday, between 9 AM and 15 PM, for the next 3 months
  • TooDo will offer a smart graphical interface will enable to mix all those conditions: conditions can be inclusive, exclusive, grouped, nested...

Synchronization with Internet to-do applications

The purpose of TooDo is not to create a new web service application which manages to-dos. The idea is to be able to synchronize with the ones already existing, and pretty smart. The best already offer web REST APIs that make this possible.

"Remember The Milk" and ToodleDo two-way synchronizations

Iit is possible to synchronize your Remember The Milk lists and tasks wih TooDo seamlessly and vice-versa. The same is true for the ToodleDo folders and tasks. However:

  • conflicts are not being solved: TooDo should ask the end-user what to do, instead of just notifying the end-user with conflict occurrences;
  • the sum-up dialog box is a bit rough, and should instead display addition details regarding the remote service tasks and todos that have been impacted;
  • in addition, the synchronization should propose a flag in order to indicate whether all external completed tasks should be deleted from TooDo (or archived), and a flag which also propose to automatically delete (or archive) todos when they have been marked as completed by the end-user through TooDo, and that they are synchronized;
  • at last, an option should be given to automatically synchronize when a todo is modified in TooDo, or to schedule regular synchronizations.

Voo2do

It should not a hard work to support the two-way synchronization with Voo2do... TooDo will very likely support that in a close future.

Synchronization with Google Calendar

Before the m5 version of Android, TooDo was able to retrieve Google Calendar events and turn them as tasks. Unfortunately, the API that enabled that in m3 version have been discarded by Google. The button for importing is still there, but does not work anymore. TooDo will support a synchronization with the Google Calendar service, and you will be able to mark some of your calendars events as todo.

Synchronization with Google Notebook

It would be even more interesting to turn Google Notebook as todos, and thus propose a synchronization process (we have already done that for the Windows Mobile OS, and it's great). Unfortunately the Google Notebook API is not usable from Android at the moment (we'll have to write REST calls ourselves), and the Notebook is accessible in read-only mode (this will be only a one-way synchronization).

Media notes

Media notes will be improved (it will be possible to store them outside the Android PDA), as soon a media-recording-working Android SDK is available.

Tip of the day/help

In order to enhance the end-user experience, the "tip of the day" should be proposed. A comprehensive documentation should be made available.

Sending todos

TooDo already offers the opportunity to submit a todo to someone via SMS and GTalkService. But this is not enough, in order to make it more interoperable. The e-mail medium will probably also be used, in order to extend the communication possibilities.

Todo via XMPP/GTalkService

The XMPP protocol is obviously a must have when it comes to make Android PDAs communicate. At the moment, only SMS are supported in order to send a todo to someone, but TooDo will support that protocol in order to make it more portable, and thus enable to send a todo from a computer (not necessarily from a mobile with SMS capability).

Workflows of notifications and todo life cycle

Quite a good deal of noticeable developments have been done there and are available in v1.3. The only think which is missing is to notify that a todo has been amended or deleted. This is something that I will work on, if requested.

Optimizations for better performance

The application can be much optimized, since it is not always as responsive as one could expect. A major optimization work is already forecast.

Better look and icons, and better ergonomic

The current look of TooDo can be improved, and especially the icons, in order to make it more comfortable and intuitive. Ergonomy is an essential point on small-screen devices, thus attention must be paid on that. A large overhaul should be forecast, in order to make the navigation more intuitive.

Related content

Next development

Posted by TooDo at 2008-04-25 22:08

There are chances that the XMPP procotol be the development step...