djp's UI mockups redux: discussion

Hey there, David here again! I heard rumblings of UI rethinking, and I've done a lot of thinking about that too. As I may have bragged here before, I'm the original Designer of taskwarrior, and earned Design credit on related projects taskwiki, taskopen, taskwarrior.vim and others. I came up with most of tasks core features and functions, and brilliant coder Paul Beckingham made it happen in c++. Anyways, that was long ago and doesn't give me authority to tell anybody what to do with their android app, I know, we do this sort of thing for fun. What authority it DOES give me, is as one of the most taskwarrior and taskwarrior ecosystem obsessed individuals on the planet!!

So like the rest of us, I would really like a good taskwarrior mobile app, and it would ideally support as much core taskwarrior functionality as possible, while being quick and intuitive to use! Just like task at the cli, some people are perfectly happy with the simplest functions, and other just have to dig into all of the crazy crap task can do.

Back to UI;
I have been submitting mockups to issues here, with answers to questions, and I think I've cooked up a UI that could perform a LOT of taskwarrior functionality, without too much confusing detail. The design goal was to present easy access to as much of the existing task data as possible, while reducing visual "non-information" (like Not Selected) and control handles for a lot of it. Allow me to propose this pile of mockups. I don't care too much about theming, as long as it doesn't co overboard with the padding. But I digress! Here's the current thinking;

Task Add dialog


Task Info and Edit

Task Reports


Filter


Report and Sort connection


List with more complex sorting


Please give these a close look, there's a lot going on under the hood!
Feedback?

Empieza revisando las maquetas enlazadas y comparándolas con la UI actual de la aplicación Android. No se han nombrado archivos fuente, pruebas ni un objetivo de implementación concreto; el trabajo no está listo para definirse como terminado hasta que se acuerden pantallas específicas y cambios de UI aceptados.

Escrito por el modelo de indexación a partir del texto del issue.