This is a great hierarchical todo list, but it lacks the features I need for large projects. With 100 tasks, I need to be able to see at a glance what is actionable, on hold, or causing a hold on the critical path. Without Gantt charts or something, I can't visually represent the project timeline or status to other stakeholders. My suggestion would be to walk the list, maybe process it on the client side for cost, and determine lists of the prerequisites for each task to be completed. Save a representation of this, and use that value for filtering out what cannot be done, and what must be done now so other work may proceed. Scanning the list myself, I have to memorize all of the dependencies in the project to know what needs attention. This kind of undermines the point of organizing and assigning dependencies, I'm spending more time figuring out what needs my attention than I am working on the project. I wouldn't consider paying for this app in its current state. Not knowing what it will cost later or what features will suddenly go behind a paywall, I can't commit to integrating this into my management routine either. No XML parser for import/export of models is a bummer, even basic FOSS tools have this functionality. Will you expose an API at some point so we can integrate app events with automation tools? Those features would be critical to making this a valuable business tool IMO. Example use case: Alice assigns Bob a task which must be done before the rest of the project can proceed. Our script sees this task blocks the critical path, adds an entry to a CalDAV object with the criticality rating of the task. Tomorrow, Bob opens his Outlook and sees his work calendar has a critical task entry with the due date and what depends on it. Bob now knows that he should focus on this task, and clicks the link in the calendar event to visit the Quire page for that task. When Bob finishes the task, other backend scripts could notify the assigned persons for the now actionable children that they can get started. Perhaps Bob was finishing a source review, and once Bob marks his review as done, the script could trigger an automated build test and mark the sibling task "auto: build verification" as done when no errors or test failures occur, or mark Bob's calendar with a reminder that there is a critical build error. I hope this makes sense... Were the app more robust with an API, I think I could automate my whole project management routine from a set of bash scripts, or in Python. That'd be cool! An ecosystem of integrated apps could enhance Quire's value but please don't create another app store or a la carte hell, that model sucks. A community of Quire users who work to share tips and enhance Quire would be much nicer.
Via Quire Android