
#Producteev vs omnifocus how to
Mainstream users simply will not tolerate things being pretty obvious as to how to use them. And they could do this without ruining the interface for advanced users. And then, over time one could experiment to see how many additional features one could incorporate before the system become too confusing for newbies to use. One answer would be to have a 'Novice mode', with a greatly simplified interface, but also to keep the full existing what you might call 'Expert mode'. The reason for this is that although early adopters are happy to tolerate lots of complexity and difficulties of use, mainstream users absolutely are NOT.īut I was thinking about this problem. Then again I'm no longer holding my breath. With any luck this dev team will get with the 21st century at some point. It should've been to me but I rushed into my purchase and now I'll just live with it. If responsive dev is important to you this might be a deal breaker. It looks just like the iOS 2.0 app and it took much much much too long to get that little bit out.

Recently, in the face of MANY MANY requests they caved and produced a few screenshots of the coming 2.0 Android app. The devs do NOT share timelines, dev milestones, roadmaps/future plans nor anything else till it's released. The rest of get to wait with baited breath.

You'll have to get selected to be a member of the beta team (which apparently requires quite a bit of involvement - 4+ hrs a week at last check) to have access. There is a Jira bug tracker but that is not for the unwashed masses. There is no one curating the User Voice so it's just a free for all and useless imho.

There is a User Voice community but that too is disheveled and an apparent waste of time as decent feature requests get lost in a barrage of ME TOO's to overarching requests like "iPad app!". So much so I've pretty much given up on reporting or asking for anything. Then note which items the devs DO feel compelled to respond to. Then note how often the devs feel compelled to respond. #12 Spend an hour or too reading through this forum/board and see how many requests are open, long standing, repeats etc.
