General:

Q. How do I assign due dates to actions?

A. Try prefixing your action description with 10 Jan, 15 Dec, etc. When theaction description begins with digits followed by a "3" character monthname, colored due date appears right before the rest of the description.

Q. Whats the purpose of the little pointer/arrow, present at the left of my actions? or What keyboard shortcuts does sGTD support?

A. Try all four arrow keys, 'k', 'l' and 'e'. You'll figure it out by your self :) I think arrow keys don't work in IE.

Feature Requests:

Q. Where do I post suggestions and features requests? 

A. Suggestions can be posted here on FeVote. And completed requests can be found here.

Q. How about an offline/downlodable/desktop/standalone version of sGTD?

A. Sorry no such plans. Actually, downloadable applications are a pain to maintain:

• Its an Ruby on Rails application, so one needs ruby+database+rails+server and other gems installed to run it. 
• Imake changes to application very frequently, upgrading applicationwhich is already installed on end user machine is another pain point.
• Since this is an RoR application I'll have to give away the source code, something I am not comfortable with right now.
  

Maybe once the application is mature enough and/or I decide to make itopen source, one will be able to download and run the application ontheir machines. But as of now, no such plans. 

Q. How about nested project list? my project list is very long.

A. Ya the project list can become long, But project hierarchy can become very deep, can projects can get lost within it. Allen says the project list should be flat, its there for weakly/daily review where if some project is not being worked upon that we can either create an action or mark the project as SD/MB. So, project hierarchy will probably
won't make into Simple GTD.

But some project categorization, based on context, is necessary like "home projects" and "work projects" etc. I am thinking along these lines, may be we could tag projects. I personally prefix home project names with "H:" for now ;) 

Q. How about the ability to add a recurring action for something that must be done every (day/week/month/year) which appears under the relevant context/project on the said date.

A. This is definitely a good feature and a required one. But its bit complicated. Basically, I have to figure out what happens under various scenarios.

• what if one recurring action is not checked, and time has arrived to create a new one.
• what happens when one deletes recurring NA.
• what happens when one marks one action done, then deletes it.
• what happens when context in which RA was there gets deleted.
• and more...

These are not tough questions to be answered, but it will take some time. I do have recurring actions in my todo list. But, I am not sure when will I end up implementing them. Also I want to do this perfectly, without complicating existing interface. All of this requires lots of time. But, sooner or later, sGTD will have recurring actions.