A few issues with the Google Now integration.
I running Todoist on a stock Nexus5 running KitKay 4.4
Issue #1. When I say "Note to take out trash tonight at 7pm. If I choose to send the note to Google Now OR even Evernote I get a note with an alarm reminder at 7:00pm. When I choose to send it to Todoist the note is saved without the time attached. Why is the time attached when I send it to Google Now or Evernote but not Todoist?
Issue #2. Why can't we say "Remind Me" to add something to our Todoist instead of (or in addition to) "Note"? I am in the habit of always saying remind be because that's what I want the app to do... remind me. But Todoist is not even an option for the remind me Google now voice command. Yes, I have removed and reinstalled Todoist, still not an option on the "remind me" list.
It's a fairly new feature, and there are some things we will need to improve and change. Thank you for the suggestions, we will look into improving those in future updates.
That's unfortunate. Looks like I'll be going back to CalenGoo and the Google calendar for now. It's not as pretty as ToDoist but it works with the voice commands of Google now to include the time in reminders.
Sure hope this feature is added to ToDoist soon.
I agree. To throw a task into the Inbox without any attributes such as date due and time, much less labels or projects, is just asking for that task to get lost.
Seems to me that Todoist added this feature just to say it was there for marketing purposes. I'd be shocked if anybody, even within the Todoist org itself, regularly makes use of this feature without the ability to assign a date or time as part of the spoken command.
As I've stated before in another message, Todoist should be able to take a task entered from any app and parse out at least due date and time, if not also, based on certain key words or symbols, labels, priority, and project.
It's unfortunate and is another one of Todoist features done half-a$$ed.
We're sorry to hear that. The reason why we don't support dates is because of the way Google Now works. We also want to provide a fully working feature so adding date support now would actually make it only partially functional and not working reliably.
Google Now, as it is now, strips due dates from the voice command "note to self" and doesn't pass it to the app in some cases.
For instance, if you say: "note to take the trash out tonight at 7pm" this is what the app receives: "note to take the trash out tonight at 7 p.m."
But if you say: "note to take the trash out tomorrow at 7pm" this is what the app receives: "note to take the trash out" with no information whatsoever about the due date.
That said, this would make it very cumbersome as most of the times the date or time wouldn't come through at all and you couldn't rely on it. That's why for now, we prefer not to add a half-functioning option until Google Now evolves and will pass all dates and times reliably and then we can implement it.
Thanks for your response David.
But you made my point about half-way adding the feature for marketing purposes. Dates work, but times don't. Yet you implemented the feature without the date.
In your current implementation you're handling less information, and making it even more confusing, than if you at least handled a date (understanding that the time component is trimmed from the string you receive).
In other words, why stop where you did? We already know that that string that is returned at least contains the words "today", "tomorrow", "July 13th" etc. That's all I'm asking for -- with the understanding of your inability to control that times aren't returned.
So, in our example, "Note to take the trash out today", we know that you *always* get the "today" part of the string. Why not use it? Then, when your users ask "Why can't you process time too?" you can at least answer with a straight face "we don't receive the time info in the returned string. All you can use is "today", "tommorrow", "sunday" ... "saturday", or, for example "July 13th"." I tested all of these and the string contained each date reference without exception.
Just as you've said, we prefer not to add features that are partially supported. Given a choice between not adding dates and times consistently or adding dates, but not times and if times are used also not dates because dates are stripped, we choose the former.
Our main goal is to make the app very intuitive and it's not intuitive to have to think all the time to not mention a time because when you accidentally do, it will even strip the date. That said, once dates and times are supported, we'll support them too as consistently as we do on all platforms and with all features.
Dates are not stripped as long as the task is spoken properly ("Take out the trash tomorrow." "Call David Tuesday"). Which shouldn't bother you too much considering that you already have a very specific syntax for due dates, repeating tasks, etc.
The truth is you did release a feature that is only partially implemented. I don't suppose you can see that though. You had four choices:
1. Don't release anything until the interface is complete. 0%
2. Release only descriptions coming from Google Now (GN). 33%
3. Release descriptions and due dates ("today", "tomorrow", "tuesday", etc.) from GN. 66%
4. Release descriptions, due dates, and times from GN. 100%, though granted times aren't available to you currently so a complete implementation isn't possible.
You chose 33%.