WordPress for Android version 6.1-rc-1 has been released in the Google Play Store. You can join the beta from the Google Play Store on your device (under “Become a beta tester”), and comment here or join the Google Plus beta community for more discussion with other testers. (Note: If you see a message that the beta testing program is full, you’ll need to wait for space to open up before you can join the beta. Thanks for your interest!)
What to Test:
New: Voice comment replies for Android wearables
You can now reply to comments directly from your Android wearable device, using dictation (voice reply)! Test it out with your wearable device:
- Make sure your wearable device has access to your notifications:
- In Android 4.4: Go to Settings > Security > Notification Access
- In Android 5.0+: Go to Settings > Sound & Notifications > Notification Access
- On the Notification Access screen, make sure “Android Wear” is checked.
- Trigger a new comment notification on a post you published (ask someone to comment on your post, or comment from a different account you own).
- Check the notification on your wearable device.
- Swipe left on the notification and tap “Reply.”
- Speak or use emojis to reply to the notification.
- Did the comment notification appear on your device?
- Did the notification look ok and include enough detail for you to reply from your device?
- Was your comment reply posted as expected?
Updated: Redesigned Reader post screen
The Reader post screen (for individual posts) was redesigned to match the latest design in the Calypso (web) Reader. Changes include:
- A redesigned header for the post which includes the site blavatar + author avatar (or just avatar if there is no blavatar)
- A shortened dateline which includes both the primary and secondary tags on the post
- The like & comment icons in the footer now include text
- A redesign of the related posts section, which now has a “More in [site]” section and a “More on WordPress.com” section
- Do the design changes appear as described above? Do they look good in both portrait and landscape?
- Do you see any strange or unexpected design changes on posts you read? (Watch or test for edge cases, such as posts with no avatar or blavatar, very long tags, etc.)
- Are you able to interact with the post (tapping on tags, likes, comments, related posts) and continue navigating through the Reader as expected?
New: Shortcut to System Settings from App Settings
There is now a shortcut to your device System Settings from the App Settings section. Test it out:
- Open the Me tab in the app (the person icon).
- Open App Settings.
- Tap on “Open device settings.”
- Confirm that your System Settings open to the WordPress app setting screen.
- Did the System Settings open to the right screen?
- Was the shortcut clear and discoverable in the app?
- Were you able to get back to the app afterwards to continue?
In addition to testing new features, as beta testers we can give feedback about the flow through the WordPress app. (Not sure what I mean? Check out how the WordPress Flow team tests and what we mean by flow.)
Here are some things to consider or try out in this release:
- Take a screenshot of each step as you test the new and updated features above. Upload your screenshots (you can create a gallery on Cloudup) and share them in a comment here.
- As you go through each step, pay attention to how you feel. Are you ever confused, lost, surprised (pleasantly or not), frustrated, anxious, or experiencing something else in reaction to what you are doing or seeing? Share those reactions in a comment.
- With each new and updated feature, can you start interacting with the feature, complete the process, and move on to your next intended task? If you get stuck or don’t finish where you expected, share that in a comment.
Bugs & Feedback
Did you find a bug or come up with a feature request while testing? Did you try the additional flow testing? You can discuss it here, report it using the “Enter feedback about the app” form in the Google Play Store, or head straight to the Android Github repository and open a new issue.