Thanks for you post.
I would suggest giving the dev a little more room to respond positively and fix.
It sucks that there are bugs and I’m sorry you had to run into them. At the same time it would be valuable to everyone of there was a good TaskPaper iOS client, and I am unlikely to build one. To my eye (of just playing around) PaperTrail is still a good candidate for TaskPaper on iOS.
I think it would help a lot of you could provide specific examples of each of your cases. I don’t know quality of PaperTrail code, but to me the polish in app looks pretty great. And the feedback/development cycles in forum discussion also looks good/healthy. I bet if you report each bug that you run into with detail you’ll see positive results.
-
“Folder disorganized”. I’m not sure what this means? Are you referring to what TaskPaper calls “Projects”. And in what way did it get disorganized, how to reproduce this problem?
-
“Blank lines addition between folder”. This is clearer, but still if you could break it out into an example it would be easier to quickly understand/fix.
-
“No respect for tabulation when hitting return” Again example will help get it fixed. I just tried this and was about to write you back and say “it does work for me”, then I tried from middle of paragraph and see what you mean. Indent is respected at end of paragraph, just not when return in middle. Definitely a bug, but shouldn’t be too hard for dev to fix. But they may think the same thing that I did when first reading… "already works!”
I expect the developer does very much want these things fixed. While at the same time if a user comes at me with negative language without many details, it’s difficult to find the energy to investigate.