Aaron Douglas 1:42 pm on April 26, 2017
Tags: , , , , ,   

Call for Testing: WordPress for iOS 7.5

The WordPress for iOS 7.5 beta will be available for testing on TestFlight soon. Not part of the beta program yet? Please sign up for our TestFlight program to request to join as a beta tester.

What to Test

1. Aztec Native Editor

You may have heard about the new editor that’s included (but hidden) in the WordPress app. Aztec has reached beta status and you’re being invited to test it out!

First step: Read about Aztec here. There are instructions on how to enable it.

Second step: Look at the release notes for Aztec to find out what works, doesn’t work. It’s a beta so there’s still work left to be done.

Third step: If you test with updating an existing post, you may wish to use a test site. While we’ve been working super hard to make a solid experience you could potentially lose formatting.

We’re keeping the testing scenarios pretty loose at this point:

  • Compose a new post.
  • Update an existing post.
  • Add images (video support coming).
  • Try formatting things and verify formatting isn’t lost after posting.

Feedback

Something not work right? Did the app crash? Please tell us if something that seems like it should work didn’t.

2. Post Slug editing

On a post you can now edit the post slug (the unique part of a post URL).

Testing steps:

  1. Create a new post.
  2. Tap the ellipsis button and then Options. Tap Slug near the bottom of the list.
  3. Edit the post slug and provide something different than the default. (currently the default is blank – we’re going to supply the standard text before 7.5 ships)
  4. Publish the post and verify the slug is what you provided.
  5. Also try editing the slug on an existing post (using a test post is suggested).

Feedback

Try and break this – leave it blank, put weird stuff in there, etc. Let us know what happens!

Several Bug Fixes & Improvements

There were a bunch of other improvements made in this release that aren’t being called out in this post. You can view the entire list here.

https://github.com/wordpress-mobile/WordPress-iOS/pulls?utf8=%E2%9C%93&q=is%3Apr%20milestone%3A%227.5%20%E2%9D%84%EF%B8%8F%22%20

Bugs & Feedback

Did you find a bug or come up with a feature request while testing? You can discuss it here, ping one of us in the #mobile WordPress.org Slack room, report it using the TestFlight feedback link, or head straight to the iOS GitHub repository and open a new issue.

Thanks for testing!

#aztec, #beta, #ios, #needs-testing, #wpios

Aaron Douglas 1:45 pm on April 8, 2017
Tags: accessibility, announcements, , editing, editor, , native   

Introducing the Aztec Mobile Editors

The hybrid (HTML & JavaScript) approach has worked well enough to bring a rich editing experience to our users. The limitations of the web view has prevented us from giving those users the anything better than a 7 out of 10 experience. The only real solution for us to reach a full 10 out of 10 was to rethink the implementations to get closer to the metal. That means using APIs provided by Apple and Android to make text editing feel like something that was made for the platform.

The mobile team has been hard at work since July 2016 to improve the post editing experience for our users.

Our hope is the Aztec editor is seen as a component that can be used by many iOS and Android apps to provide a rich HTML editing experience. We feel that we could garner a bigger contributor base to the mobile apps simply because this component exists, is free & open, and is super awesome. We’re not biased at all, of course. 🙂

The Aztec Logo

What Does Aztec Give Our Users?

  • Accessibility – Using OS-provided text controls makes every piece of what you can see to be visible to technologies like VoiceOver. We can now properly support our users that require accessibility. Additionally we can now support dictation!
  • Spell Check – Something as simple as spell check is a nightmare to get working properly in the current hybrid editor. No longer a problem with Aztec! This makes the editing experience feel safer for our users.
  • Speed/Performance – Aztec is so much faster and memory efficient since we have control over the small things.
  • Aztec Everywhere – We plan on using Aztec in more than just the editor view. Aztec is actually a text view implementation and lightweight enough to use in many places in the app. Think of being able to send rich text replies to comments and a more robust iOS sharing experience thanks to a fully custom UI.
  • Contribution – We’re packaging Aztec as a component in its own GitHub repository (each platform has its own repo). This makes Aztec something outside users will want to incorporate into their own apps and contribute back to. Quite literally there is nothing like this out there – every editor we could find uses a web view or has very limited support for any HTML.
  • Undo/redo – The Aztec editor supports undo/redo on both platforms. It’s temporarily disabled on iOS until we finalize some bug fixes.
  • Unit Testing – We’re actually able to write unit tests for scenarios that come up and make sure they’re handled consistently. UI testing is also now possible!

What was so Hard?

Editors are hard. I think many of us here working on WordPress can attest to just how difficult dealing with HTML is sometimes. We had a number of technical hurdles to get over. Some of the challenges were:

  • HTML Synchronization/Consistency – Switching between HTML and visual editing mode presents a ton of challenges keeping things in sync. HTML tags that don’t visually alter the rendering need to be retained – dropping that markup would dissatisfy users fairly quickly.
  • Lists & Block Quotes – We’re still having struggles with getting the editing and rendering experience just right with lists and block quotes. They’re deceptively complex and have been one of the places we’re spending the most time on to get right.
  • Amount of Work – There’s just a lot to do with an editor. Edge cases are so numerous that they really aren’t edges. Editors are more like spikey balls on chains.

Okay, I Want to Test it Out!

We wanted to ship Aztec quietly to limit the number of voices providing feedback. The projects aren’t 100% ready for feedback from the full community quite yet but we feel everyone reading this blog can get an early peek. We’d like you to keep some things in mind as Aztec isn’t completely finished on both platforms. We’re not rolling out Aztec to our public beta testers until we’re sure the editing is a beta or better experience.

  1. Aztec is not quite ready for posts where losing formatting would ruin your life. We’re still working out bugs and HTML synchronization between what you see and what ends up on the server is one of the areas we need testing for.
  2. Lists and Blocks aren’t fully finished. Nested lists on iOS aren’t supported yet.
  3. Media support is limited to images. Videos aren’t supported quite yet and images may have some funk with how they’re presented on Android.
  4. External keyboards are supported but not fully feature-enriched. Feel free to use your keyboard with your tablet. Things like the tab key may not be spot-on yet.
  5. You can check out the open issues lists on GitHub to understand what’s left to work on.

Turning on Aztec in the WordPress Apps

You’ll want to become a beta tester for the WordPress app to get access to the newest changes. Join the iOS TestFlight program for Apple devices. Android users can join the beta from the Google Play Store on your device (under “Become a beta tester”).

The next step to using Aztec in the WordPress apps is to unlock it as it’s a hidden feature right now. In the web browser on your device, visit this URL:

wordpress://aztec?available=1&enabled=1

This unhides Aztec in settings and turns it on. You can turn the new editor on & off by following these steps:

iOS: To turn on Aztec in WP iOS 7.2 or newer, navigate to the Me tab, tap App Settings, turn on Visual Editor (which should be on already), then turn on Native Editor.

Android: Turn it on by navigating to the Me tab, tapping the App Settings option, tapping the Set editor type setting, and choosing either Legacy or Visual.

Using Aztec Directly

Each of the Aztec repos also contains a demonstration application to use the Aztec component without it being inside of the WordPress apps. If you want to start hacking away on the component itself, this is the best way to start looking at it.

iOS: https://github.com/wordpress-mobile/WordPress-Aztec-iOS
Android: https://github.com/wordpress-mobile/WordPress-Aztec-Android

What should I report?

  • Discrepancies between what you saw in the editor and what actually got published – If you lost formatting or had other problems we really want to know.
  • Crashes – any time you get the app to crash whilst in the editor, let us know.
  • Content that freaks out the editor – if you found some HTML that the editors just do not like, let us know. We’re looking to bulk up our unit tests with examples that make things get wonky.
  • Anything preventing you from publishing – specifically on iOS we rewrote the code around the entire editing experience. If you discover state issues that don’t let you tap publish (for example), let us know.

How should I report?

  • GitHub – Report issues to the main WP Android or WP iOS repos. If you know for sure the issue lies with the Aztec component you can report it directly to the appropriate Aztec repo.
  • Slack – We’re hanging out in WordPress.org Slack in #mobile.

What’s Next?

Here’s a list of the milestones we have in the project and approximate dates:

  1. Alpha – Turned on for the development team & testers to dog food. We’re here now.
  2. Closed Beta – When the editor is good enough to advertise to beta testers (turn on w/URL) and to get feedback from them. Starting with WPiOS 7.5 beta & WPAndroid 7.3 beta which equates to April 24th.
  3. Open Beta – When the editor is good enough to unhide the option to be able to turn it on/off for everyone (advertise it to App Store users with the caveat of beta). Ideally shortly after closed beta; May 22nd would probably be the earliest.
  4. Release Candidate – When the editor is good enough to turn Aztec on by default but allow it to be turned off. We’re estimating a month or more of beta time; June 19th+.
  5. Full Release – When Aztec replaces all current editors and legacy code is removed. This is mid to late July or later depending a number of variables.

Closer to the open beta we’ll start focusing on improving documentation for contributors on the individual project repositories. You can also look forward to seeing posts here on technical discussions for both platforms.

Special Thanks!

None of this would have been possible without the hard work of: @0nko @diegoreymendez as technical leads,  @rachelmcr heading up our testing efforts, and @heckofanapp @hypest @klymyam @lanteanar @sergioestevao @mbiais @bummytime @folletto @aerych @koke working on the engineering and implementation.

#accessibility, #announcements, #aztec, #editing, #editor, #native

Rachel 6:16 pm on March 28, 2017
Tags: , , ,   

Call for Testing: WordPress for iOS 7.3

The WordPress for iOS 7.3 beta will be available for testing on TestFlight soon. Not part of the beta program yet? Please sign up for our TestFlight program to request to join as a beta tester.

What to Test

1. Publicize Improvements

If you tried the Publicize feature that came out in version 7.1 you’ll want to take a look at these improvements:

  • Fix a broken publicize connection from the editor’s post options.
  • Switch back to the default publicize message (post title & URL) by deleting the custom message.
  • Tap the whole line (not just the toggle) to toggle a connection on or off.

To test:

  1. In your site’s Sharing section, connect to at least one sharing service.
  2. Bonus: Break the publicize connection (for example, by deactivating the social media account you connected — you might want to use a test social media account for this!).
  3. Create a new post.
  4. Open the post options.
  5. If you broke your publicize connection in step 2, tap the error symbol to fix the connection.
  6. Set a custom publicize message.
  7. Remove the custom publicize message.
  8. Tap anywhere on an individual sharing connection to enable/disable it.
  9. Publish the post and confirm the default publicize message (your post’s title and URL) was used.

Feedback:

  • Did the three improvements work as expected? Please report anything that didn’t work or other parts of the Publicize feature that you still have trouble with.
  • Flow Challenge: Were you able to fix a broken publicize connection and return to your task smoothly? What happens if you change your mind in the middle of the process? Please report any point where you get stuck or can’t find your way back to the post you’re working on.

(Related Github pull requests: Reconnect a broken connection, Switch back to default message, Toggle behavior.)

2. Recent Sites

You can now find your most recently used sites at the top of your site list (under My Sites > Switch Site), if you have more than 11 sites in the app.

 

Feedback:

  • If you have 11 sites or fewer, does the recent sites section appear? (It shouldn’t appear unless you have more than 11 sites.)
  • If you have more than 11 sites, do your recent sites appear in the order you most recently used them in the app?

(Related Github pull request.)

3. WordPress.com Site Icons in My Sites

Site icons for public WordPress.com sites will now appear in the site list and the site details on the My Sites tab. (Previously, only a site icon placeholder appeared there.)

To test:

  1. Add a site icon to a WordPress.com site (from the site’s general settings or customizer).
  2. In the app, open the My Sites tab.
    1. Check your site list and confirm the site icon appears next to the site in the list.
    2. Open the site details and confirm the site icon appears next to the site title/URL at the top of the screen.

Feedback:

  • Please report any issues with the site icon not appearing next to a public WordPress.com site, either in the site list or on the site’s details (dashboard) screen.
  • Bonus: Try removing the site icon as well as adding it, and confirm the app updates the site icon in both cases.

(Related Github pull request.)

4. Sharing to WhatsApp and Telegram

You can now share posts to WhatsApp and Telegram, using the sharing buttons on the post:

  1. Install and set up WhatsApp and Telegram on your device.
  2. Open the Reader in the WordPress app.
  3. Find a post that has the WhatsApp and/or Telegram sharing buttons enabled.
  4. Tap on “Visit” under the post in the Reader list view.
  5. Scroll down to the sharing buttons under the post.
  6. Tap on the WhatsApp and/or Telegram buttons to share the post.

Feedback:

  • Please report any errors or unexpected results when you share the post to WhatsApp or Telegram.
  • Testing Challenge: Can you find the other ways to share a post from the Reader? Test those out and confirm sharing works as expected in each place.

(Related Github pull request.)

Bugs & Feedback

Did you find a bug or come up with a feature request while testing? You can discuss it here, report it using the TestFlight feedback link, or head straight to the iOS Github repository and open a new issue.

Thanks for testing!

#beta, #ios, #needs-testing, #wpios

Rachel 8:52 pm on February 28, 2017
Tags: , , ,   

Call for Testing: WordPress for iOS 7.1

The WordPress for iOS 7.1 beta will be available for testing on TestFlight soon. Not part of the beta program yet? Please sign up for our TestFlight program to request to join as a beta tester.

What to Test

1. Publicize (Sharing) Support for Posts

You can now manage your sharing connections for individual posts, to control where each post is shared when you publish it. Try it out:

  1. In your site’s Sharing section, connect to at least one sharing service.
  2. Create a new post.
  3. Open the post options.
  4. Set a custom publicize message.
  5. Enable/disable individual sharing connections.
  6. Publish the post.

Voilà! Your post will be publicized to the selected social media accounts, using your custom message.

Feedback:

  • Things to check: Did all of your connected accounts appear in the post options? Did your custom message show up on the publicized post? Was the post publicized to your selected connections (and only the ones you selected)?
  • Flow Challenge: Did the publicize settings make sense in the sequence of steps you took to create your post? Did you ever have to disrupt your publishing process to manage those settings, or did you experience any confusion or frustration along the way?

(Related Github pull request.)

2. Noto Font Update

The Merriweather font has been replaced with the Noto font in the app, to provide better support for non-Latin scripts.

Here’s how it looked before, with Merriweather:

And after, with Noto:

Feedback:

  • Please use the app in your language of choice. Let us know if you notice any overall issues with the font, or specific issues in your language (such as characters not appearing or displaying incorrectly).

(Related Github pull request.)

3. iPad Layout for Notifications

Notifications now have a splitview (sidebar) layout on iPads, similar to the rest of the app. iPhone users should not see any difference in the Notifications layout.

Feedback:

  • Please navigate through your Notifications, interact with them, and report any quirks or bugs in the new layout or behavior.
  • Testing Challenge: Try to catch the Notifications with unexpected layout behavior, especially while rotating the device or multitasking on your iPad.
  • Flow Challenge: Does the new sidebar make the best use of your iPad’s screen? Are there actions in the Notifications that don’t use the layout as expected, or places where you now get stuck?

(Related Github pull request.)

Bugs & Feedback

Did you find a bug or come up with a feature request while testing? You can discuss it here, report it using the TestFlight feedback link, or head straight to the iOS Github repository and open a new issue.

Thanks for testing!

#beta, #ios, #needs-testing, #wpios

Rachel 6:07 pm on February 14, 2017
Tags: , , ,   

Call for Testing: WordPress for iOS 7.0

The WordPress for iOS 7.0 beta will be available for testing on TestFlight soon. Not part of the beta program yet? Please sign up for our TestFlight program to request to join as a beta tester.

What to Test

1. Navigation Arrows for Notifications

You can use arrows (in the top right corner) to navigate through your in-app notifications without returning to the notifications list. (This is designed to match how you can navigate through your notifications on the web.)

Feedback:

  • Check your notifications in the app. Use the arrows to navigate to older or newer notifications. Do the arrows work? Are they disabled when you reach the end of your notifications?
  • Flow Challenge: How do the arrows feel for navigating through your notifications? Were you surprised or confused by anything? Did the navigation feel natural and expected?

(Related Github pull request.)

2. Add Excerpts to Post Editor

You can now add and edit post excerpts directly from the app:

  1. Create a new post.
  2. Open the post options.
  3. Scroll down to the excerpts (bottom of the options screen).
  4. Tap and enter an excerpt.
  5. View the post and confirm the excerpt is being used (e.g. in the Reader list view, in subscribers’ email notifications, or on your site if your theme uses excerpts).

Feedback:

  • Try adding excerpts to new posts, editing excerpts on existing posts, and creating/editing posts without excerpts.
  • Testing Challenge: Compare the app’s excerpts feature with the same feature in the web editor. Do the app and web excerpt features work in the same way? Do your excerpts stay intact when moving between the app and the web?
  • Flow Challenge: Did you encounter any confusion or obstacles adding an excerpt to your post? Does the excerpt act as expected throughout the rest of the app (for example, in your posts list or in the Reader)?

(Related Github pull request.)

3. Better Support for RTL Languages

The app got a facelift for right-to-left (RTL) languages, with an improved layout throughout the app. Check out the pull request for a series of before/after screenshots showing the changes, and try it out:

  1. Open the Settings app.
  2. Go to General > Language & Region > iPhone Language and select an RTL language (e.g. Hebrew).
  3. Open the WordPress app. (Bonus: Log in to a WordPress.com account with the same interface language.)
  4. Navigate through the app and look for any layout issues, e.g. incorrect padding or alignment.

Feedback:

  • Do you speak an RTL language? Please let us know if we missed any layout issues or created new ones!
  • Testing Challenge: Log out and check the login/signup screens. Do they work as expected for the allowed input? Do the error screens look right?

(Related Github pull request.)

Bugs & Feedback

Did you find a bug or come up with a feature request while testing? You can discuss it here, report it using the TestFlight feedback link, or head straight to the iOS Github repository and open a new issue.

Thanks for testing!

#beta, #ios, #needs-testing, #wpios

Aaron Douglas 7:27 pm on February 6, 2017
Tags: make.wordpress.org/polyglots, p2-xpost   

X-post: WPiOS 6.9 Translation Help

X-post from +make.wordpress.org/polyglots: WPiOS 6.9 Translation Help

Rachel 1:34 pm on January 30, 2017
Tags: , , ,   

Call for Testing: WordPress for iOS 6.9

The WordPress for iOS 6.9 beta will be available for testing on TestFlight soon. Not part of the beta program yet? Please sign up for our TestFlight program to request to join as a beta tester.

What to Test

1. New “Post-Post” Screen

After you publish a post (“post-post”) you’ll now see a screen confirming the post was published (and where it was published), with calls to action:

  • Share the post
  • Edit the post
  • View the post

Feedback:

  • Try publishing a post in different ways (creating the new post in different ways, or publishing the post from a different status) and confirm the post-post screen appears as expected.
  • Testing Challenge: Try to find a scenario where the post-post screen appears when it shouldn’t, or where the calls to action do not work as expected.
  • Flow Challenge: How does the post-post screen make you feel? Are you able to move on to your next action in the app smoothly, or do you get stuck anywhere?

(Related Github pull request.)

2. iPad Layout in the Reader

The Reader now has a splitview (sidebar) layout on iPads, similar to the My Sites and Me tabs. iPhone users should not see any difference in the Reader layout.

Feedback:

  • Please navigate through the Reader, use each section, and report any layout quirks or bugs.
  • Testing Challenge: Try to catch the Reader with unexpected layout behavior, especially while rotating the device or using Reader actions (e.g. sharing, viewing the post/site).
  • Flow Challenge: Does the new sidebar make the best use of your iPad’s screen? Are there actions in the Reader that still don’t use the layout as expected, or places where you now get stuck?

(Related Github pull request.)

3. Refreshed Reader Comments UI

The Reader comments styles were updated to more closely match the web:

Feedback:

  • Please make sure the comments appear correctly (with up to 4 levels of nesting), with the full contents of each comment, and that comment actions work as expected.
  • Testing Challenge: Try to find a piece of content or comment thread that doesn’t show up correctly (a missing emoji? a photo or video that doesn’t load? a problem when rotating your device or loading comments from a particular source?).
  • Flow Challenge: Can you open and read comments starting from different points in the app? Are there any accessibility or usability problems with the new layout?

(Related Github pull request.)

Bugs & Feedback

Did you find a bug or come up with a feature request while testing? You can discuss it here, report it using the TestFlight feedback link, or head straight to the iOS Github repository and open a new issue.

Thanks for testing!

#beta, #ios, #needs-testing, #wpios

Rachel 4:37 pm on January 4, 2017
Tags: , , ,   

Call for Testing: WordPress for Android 6.5

WordPress for Android version 6.5-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: New oEmbed Support

The app now supports more oEmbeds, including:

  • Kickstarter
  • Reddit
  • Twitter Moments
  • Facebook News

To Test:

  1. Create a new post with some text.
  2. Copy a link from one of the sources above.
  3. Paste the link on a new line in the post.
  4. Publish the post.
  5. The source content should automatically embed in your post.

Note: We’re currently investigating an issue where the embed is sometimes not created if the link is added to the first line of the post. For now, adding at least one line of text before the link (as in the screenshot below) will avoid this known issue.

Feedback:

  • Does your content embed as expected? If not, what is the link you tried to embed and/or the a link to the post where the embed didn’t work?
  • How did you feel while publishing the post?
  • Bonus: Try getting the source link using a variety of methods: copying the URL from a browser’s address bar, sharing from an app, using a “Share” button in a browser, etc. Do all of those links embed as expected?

(Related Github issue and pull request.)

New: Recent Sites in the Site Picker

If you have more than 15 sites, the site picker now shows your four most recent sites at the top of the list. The recent sites section only appears if at least 15 sites are unhidden (showing in the site list), and doesn’t appear in search mode.

 

To Test:

  1. Make sure you have at least 15 sites showing in the site picker (the site list that appears when you select “Switch Site” under your site in the app).
  2. If needed, use the 3-dot menu in the top right to unhide sites so that at least 15 appear, or use the + sign to create new sites.
  3. Select a site from the list.
  4. Select “Switch Site” to go back to the list. Your last selection should appear at the top of the list.
  5. Repeat with several other sites, and confirm that the most recent sites appear at the top of the list as expected.

Feedback:

  • Did the list of recent sites work as expected? Did it show up anywhere unexpected, or not show up when you were expecting it?
  • Describe how it felt to have your most recent sites at the top of the list. Did it help you find the site you were looking for when switching sites?
  • Please report any issues with the list of recent sites.

(Related Github issue and pull request.)

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.

Thank you for testing!

#android, #beta, #needs-testing, #wpandroid

Rachel 10:40 am on December 23, 2016
Tags: , , ,   

Call for Testing: WordPress for Android 6.4

WordPress for Android version 6.4-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:

Updated: Refreshed Reader Design

Reader streams (the list view, such as “Followed Sites” or tags you follow) got a design refresh to match the current WordPress.com Reader design. A couple big changes to note:

  • There are now five different layouts for posts in the list view. Here are the rules:
    • If the post has 0 images: Text card.
    • If the post has 1 or more images and less than 100 characters: Photo card (using featured image or first image).
    • If the post has 1-3 images and over 100 characters: Default card (using featured image or first image).
    • If the post has 4 or more images and over 100 characters: Gallery card (using first 4 images).
    • If the post has a video as featured image or a video as first usable media: Video card.
  • Tag streams now have a an image header.

Feedback:

  • Does each post layout work on your device, for example in your Followed Sites list?
  • Do you notice any design issues while scrolling, rotating your device, or navigating through the Reader?
  • Look at a tag you follow: Does the image header load correctly? Can you tap to view the post the image came from?

(Related Github issue and pull request.)

New: Draft Reminder Notification

The app now sends you push notifications when you have a local draft that is more than 3 days old. (Local drafts are drafts saved locally on your device and not synced with your site’s server.) There are a few cases:

  • For a draft 3-30 days old, the notification includes the post title and age of the draft.
  • For a draft >30 days old, the notification includes the post title (but not the age).
  • If you have multiple drafts, the notification includes the number of drafts (but not the title/age).

These cases work independently on each site, so as you switch between sites in the app the notifications will adjust to the site you’re working on.

To Test:

  • Write a new draft and exit the editor to save the draft locally. (You’ll see the text “Local draft” in yellow on your draft in the list of posts.)
  • Go to your device settings and set the date to more than 3 days in the future.
  • Open the app again.
  • The notification should appear on your device.
  • Tap “Edit” to open a single draft in the editor or the post list for multiple drafts. Tap “Ignore” to dismiss the notification (it won’t appear again for that draft). Swipe to dismiss the notification, and receive the notification again later (after 24 hours).
  • Repeat these steps for different sites with different numbers/ages of local drafts.

Note: If you don’t have any local drafts on your site to begin with, the notification may not appear (Github issue). This is a known issue with this first beta release and is resolved for the next release.

Feedback:

  • Was the notification clear and compelling to you? What was your reaction to it?
  • Describe what you intended to do after seeing the notification. Were you able to complete the actions/flow you intended, or did you get stuck anywhere?
  • Please report any issues with the notification itself (the number of drafts, the age of the drafts, the timing of the notification, etc.).

(Related Github issue and pull request.)

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.

Thank you for testing!

#android, #beta, #needs-testing, #wpandroid

Rachel 4:45 pm on December 7, 2016
Tags: , , ,   

Call for Testing: WordPress for Android 6.3

WordPress for Android version 6.3-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: Swipe between notifications

In the Notifications tab, you can now swipe left/right to move between notifications. (Previously, you had to go back to the notifications list to open another notification.)

  1. Open the Notifications tab (the bell icon)
  2. Tap on a notification to open it
  3. Swipe to move to the previous/next notification in the list
  4. Tap the back arrow in the top left to return to the notifications list

Feedback:

  • Did you notice the “swipe snackbar” pop up at the bottom of the screen to explain the swiping action?
  • Were you able to swipe as expected between notifications? Did the direction of the swipe feel natural to you?
  • Did anything confusing or unexpected happen while checking your notifications?

(Related Github issue and pull request.)

Updated: Styles on the login screen

The app’s login screen has new styles to differentiate between the login forms for WordPress.com and self-hosted sites. To see the difference, log out of the app (or install the app fresh on your device):

  • By default, you will see the WordPress.com login form with the WordPress.com logo and “WordPress.com” stated above the login form.
  • Tap “Add self-hosted site” at the bottom of the screen to switch to the login form for self-hosted sites. This screen now displays the WordPress.org logo with a grey background.
  • Tap “Log In to WordPress.com” to return to the WordPress.com login form.

The new styles:

Feedback:

  • How do the new styles look to you? What feelings do they evoke (for example: surprise, confusion, satisfaction)?
  • Can you log in as expected with each form? Do you have any trouble using either form?
  • Is the transition from one login form to the other smooth?

(Related Github issue and pull request.)

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.

Thank you for testing!

#android, #beta, #needs-testing, #wpandroid