Support Toodledo "Due After" functionality for real
Your help doc says, "Note that Toodledo also has a “due after” option to specify that a task an only be completed after the due date. Ultimate To-Do List does not implement this, since the start date field can be used instead."
Start date is not the same as due date. It's simply wrong to assert that the start date field accomplishes the same purpose as the due date field. Screen real estate is at a premium both in the Ultimate To-Do List App and in the Toodledo web app, and I don't want to have to waste space displaying the Start Date field for hundreds of tasks in both apps just because a few of my tasks fall into the "Due After".
Also: If you mark a recurring task as "Due after" in the Web app, and then later you mark it complete in the Android app, the newly created recurring task LOSES THE DUE AFTER ATTRIBUTE that the old task had before you marked it complete. This is data corruption / loss, and it's totally unacceptable. Even if you don't support entering a "Due After" task in the Android app, you absolutely, positively, 100% need to preserve the attribute if it's already set on a task.
Daniel Link commented
As long as "due after" is not supported, it would be fair to revise the following sentence on the UTL homepage: "Supports ALL features supported by Toodledo and Google." It does not.
I use "due after" a lot, especially to get waiting or delegated tasks out of my face for a while and then receive a reminder (what SES21 said). If changes are made to the due date in UTL, it loses its "due after" flag on Toodledo. It's not exaggerated to say that this corrupts my system.
Yeah, what he said! I use Due After a good bit, sometimes those tasks have real Start Dates too so faking it isn't an option, & I find it hard to believe that UTL doesn't truly support this.
Besides the above, you're overlooking the fact that we can't set a reminder on a Start Date, which means that we still need a Due Date (at least in TD) which would have to have an erroneous modifier since it can't be Due After! Also, if we don't put a Due Date, then that changes the Importance calculation & throws that all off, too. TD also treats the Start Date & modified Due Date differently when it comes to hiding Future Tasks. "Future Tasks" are hidden until their Start Date while tasks with modified Due Dates are only hidden until a week before they are due unless their start date keeps them hidden longer. That means, if we use your method, we wouldn't have visibility of that task until the day it was "due after" - which puts a kink in my workflow or takes me back to needing to use the Start Date field to make it show up the week before like it should have! But wait, I can't do that because it's already occupied with my Due After date! *Face Palm*
Based on what I read in TD's API doc, it's a matter of a single-digit value & you're already dealing with that field for BY, ON & OPTIONAL. How can this be so hard to implement?? If it's a matter of the characters following the Due Date in the UTL GUI, just use (After) instead of the whole phrase...