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:

  1. Wrong Credentials/Can’t login
  2. Self hosted issues
  3. HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. Auth
  4. External keyboard issues
  5. Visual editor
  6. 2 step auth (I think many people don’t know about app specific passwords, some credential issues might actually be 2-step related)
  7. Old posts in app after draft update
  8. 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 UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. 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 APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways..

I’ve ruthlessly moved everything else to 3.8.5, and added a must-have label to indicate blockers for release