Google Tasks API Released
code.google.com
code.google.com
I can expertly tell you that people use Google Tasks because of very low friction to entry. If you are using Gmail, starting to use Google Tasks is a one-click process.
Friction is paramount to adoption of, well, pretty much anything!
What? Can you indent a task to anther in Evernote and when checking the parent task, check all of child tasks?
My only gripe with it is the icon/logo of the app. A little garishly and too-brightly colored. Amazing app otherwise.
The poll will be announced within the app itself, so just keep installing the updates and you will not miss it.
If you tell me your specific problem I might be able to help. Shoot me an email via support page on geetasks.com
If your problem is specific to Google Tasks API I will not help you. Sorry, business is business. :)
But I wonder... lets say you show how to solve some problems with Google Tasks, you get a higher page rank, and people with a problem with Google Tasks arrive at your page... where you incidentally note problems that your solution solves better than Google Tasks (which will be true, since they are mass market and general, and you can be happy with a smaller, more specific niche).
When your competitor has made larger market share than you, this can work. It can be help that is applicable to every product, even advising where your competitor is a better solution.
But I guess this mightn't work for a developer API, if they want the platform with the largest install base.
disclaimer: I'm not seriously suggesting this - just thinking aloud.
I'm delighted to find (so far) two happy users on hacker news and it brightens up my day. It rains so heavily today in Seattle that I need all the brightening I can get. :)
To be fair (he-he) I now have a new unfair advantage - a significant number of happy active users. I hope they will help me to stand out.
#1 GOOGLE TASKS APP IN THE APP STORE
NO ONE COMES CLOSE TO BEING AS AWESOME AS US
OBAMA HIMSELF USES THIS APP AND HE LOVES IT!
Don't forget to litter the description with emoji stars and thumbs up and whatnot.
Honestly the GTasks app for Android (which was written before the API) is the only reason I use GTasks.
I've created a new list and added 4 tasks a, b, c and d, and later added a2 after a.
Here's what they are doing:
Position:
a 01111111111111111111111111111111
b 10111111111111111111111111111111
c 11011111111111111111111111111111
d 11100111111111111111111111111111
a2 10011111111111111111111111111111
So it seems a clever way of allocating the position numbers without having to change them all everytime a task is moved, but I'd love to read more about it.http://en.wikipedia.org/wiki/Self-balancing_binary_search_tr...
But why number them at all - why not just use the order in the list as the ordering? I haven't studied their API, so there may be a good reason.
This is not specific to Google tasks. If you tried to display a list of items that your users could reorder, you'd run into the same problem.
But I guess for RDB (and other DB?), the "physical" order isn't meant to be used as a "logical" order, and it might not even be reliable - so you need some other ordering mechanism, like position numbers. Also, not good if anything in the system depends on that physical ordering.
\not a DB programmer
They're using JSON to describe sets of possible JSON instances, using conventions of "..." to represent other items in a list; and italics to represent variables (though not always: example text such as "My Task" is used for some variables).
Perhaps a shell-style convention, like $taskListID and ${My Task} would be clearer? It's going outside the JSON syntax, but so is "..." - and obviously extra-linguistic constructs help alert the reader that it isn't part of the instance syntax (like italics).
I've looked at some "JSON schema" proposals, but they take the same meta-approach as XML Schema, which somehow seems even worse applied to JSON.
Regarding the actual format, they the kind attribute (kind="tasks#taskList") like a class. Since it defines the type of the message, maybe it would be clearer if it were distinguished in some way (like XML tags: <tasks#taskList> - invalid, I know).
disclaimer: I don't mean to rag on these guys - their focus is Google Tasks, not a schema for JSON. It's just that it's very well documented, and so it's a clear example of using JSON as a schema. This issue will become more important over time.
I do feel like a whore of the 'tasks' world going from one solution to another. Recently, it was teuxdeux > todoist > thinkery (My current 'lover'). I wish someone could combine them all -- that's actually a 'sometime in the future' personal project of mine.
Which is probably why I love TaskPaper for GTD. Plain text but with smart data-detection.