I just went through the latest reviews 1…
I just went through the latest reviews (1 to 3 stars) and forum posts and, while the sample is small, here are the top issues detected:
- Wrong Credentials/Can’t login
- Self hosted issues
- HTTP Auth
- External keyboard issues
- Visual editor
- 2 step auth (I think many people don’t know about app specific passwords, some credential issues might actually be 2-step related)
- Old posts in app after draft update
- Duplicate reader items
Some of those (specially the 2 first) are usually quite vague and why having a direct contact will be great.
I haven’t included stuff that it’s already fixed on 3.8.3. I’ve included HTTP Auth even though it’s fixed on develop to highlight that it’s something we need to test better.
So, highest priority items for 3.8.4:
- #212 – In-app feedback. @astralbodies let me know if you could use some help in there. I liked @twitkin suggestion on the initial mockups of just adding a ‘Need help?’ link at the bottom of the login screen. Can @twitkin or @hugobaeta review the UI flow from can’t add site to contact us?
- #268 – Clean up logging. Our logs are a mess and not very helpful most of the times. Since the feedback option should include logs when errors happen, make sure those are actually helpful.
When those two are ready to go, we’ll freeze .4 with whatever other improvements we have. With feedback from users we should be able to fix everything on the list for 3.8.5 (except the visual editor ).
Other high priority things according to the list.
- #269 – Better support for 2 step. Even if it’s not full support (asking for the auth code after login), make sure the error messages reflect what’s going on.
- #112 – Duplicate posts on reader
- #22 – Consolidate accounts/credentials. I’d bet many credential issues are still caused by the fact that some places check for credentials in the wrong places. In a nutshell: WPAccount should be the only class to talk to the keychain, and there should be no
[WordPressComApi sharedApi]
, ask the default wp.com account for it’s API.
I’ve ruthlessly moved everything else to 3.8.5, and added a must-have label to indicate blockers for release
Aaron Douglas 5:14 pm on October 17, 2013 Permalink | Log in to Reply
I’m working on both #212 & #268 right now. @twitkin is helping me with reviewing the UX of the feedback screen(s). I’ll keep feedback in its own branch unless you want it merged into develop sooner?
Jorge Bernal 5:16 pm on October 17, 2013 Permalink | Log in to Reply
That’s ok, let’s merge when it’s ready or almost ready.