The block editor is coming to the mobile apps

I’m proud to announce that we’ll be shipping the first public version of the block editor in the apps with their 11.9 release. This release will be available for beta testers today (learn more about testing the apps), and the general public in March 11th.

What to expect

For this first version, our main focus was to build a pleasant writing experience with support for the most basic types of content.

Our data showed that 90%+ of the posts created on the mobile apps consisted of basic text and images, so we decided to focus on supporting the Paragraph, Image, and Heading blocks on this version.

Within those limits, we wanted this to be functional and usable as a replacement editor from the start, so we did a lot of work on making sure the little things that you would expect to work on an editor were there: pressing enter would create a new paragraph block, support for undoing and redoing edits, basic formatting,…

Known issues

  • On iOS, using typing suggestions sometimes removes spaces between words.
  • On iOS, dictation doesn’t work at the moment.
  • On Android, when you insert a Heading block it initially shows no formatting.

How to test the block editor in the apps

Once you have version 11.9 of the apps, the block editor will be available, but not always used by default. When you edit an existing post, it will detect if it has block content and open it in the block editor, otherwise it will open in the classic editor. If you prefer to edit a post with blocks in the classic editor you can still do so by going to the editor menu (•••) and choosing “Switch to Classic Editor”.

When you create a new post, it will use the classic editor by default. To change that, you can go to Me > App Settings and enable the Use Block Editor option, and every new post will be created in the block editor.

What’s next

After the release, we will start working on some UX improvements and visual refinements that didn’t make it in time, and any major bugs that comes up. Shortly after that we’ll also spend time adding support for the most common blocks and use cases.

Get involved

You can follow along on the Gutenberg and gutenberg-mobile Github repos, and if you have any questions or want to get involved, you can discuss here or find us in the #core-editor and #mobile rooms in WordPress.org Slack.

Call for Testing: WordPress for iOS 13.2

WordPress for iOS version 13.2 beta is available for testing on TestFlight. You can sign up for our TestFlight program and join as a beta tester by opening that link on your iPhone or iPad.

An important update in this release is the introduction of the option to Sign In with Apple in preparation for the release of iOS 13. 🎉

Disclaimer: iOS 13 is currently in beta. Beta software refers to a version of software that is still under development and is not yet released to the public. Make sure to back up your devices before installing beta software and install only on devices and systems that you are prepared to erase if necessary. If you do not have a device you would like to use, feel free to skip the steps that require iOS 13 (there are just two at the end of the list).

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  • Create a new Apple ID with two-factor authentication enabled to use for testing.
  • Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.

To test:

  1. Block Editor: create and publish post using all of the available blocks (Paragraph, Heading, Image, Video, Lists, Separator, Page Break, Quote, More) and check that each one works as expected.
  2. 12377 Go to My Site and pull to refresh many times to try to get duplicate sites to show. If you can see duplicates, either pull to refresh or wait for a bit for the site to sync and the duplicates should go away.
  3. 12287 Go to Profile and notice the Notifications Settings option is no longer there. Go to Notifications and tap the cog icon at top right. Make some changes to your notifications settings and ensure they work as expected.
  4. 12363 Go to My Site > Settings > Time Zone and choose a timezone other than your device timezone and not UTC. Go to My Site > Stats > Days and make sure the site timezone setting is displayed correctly.
  5. 12303 Create a new post, add a title, add an image, save as a draft, go to More > Preview and make sure the image loads in the preview.
  6. 12107 Go to Profile > Help & Support and test the Contact Us form. Try sending logs both as an attachment and via copy/paste.
  7. 12305 Log out, tap “Log in”, a button view should appear with the following options: “Continue with Apple” (only if you have iOS 13), “Continue with WordPress.com”, “Continue with Google”, and “Or log in by entering your site address.” Check that each login flow works as expected.
  8. 12336 (requires iOS 13) Log out, tap “Log In”, select “Continue with Apple” and follow the prompts to Sign In With Apple.
  9. 12379 (requires iOS 13) Go to Settings > Display & Brightness and tap Dark to switch to Dark Mode. Browse around in the app. Does anything look wrong when in Dark Mode? Try editing a few posts that contain blocks using the block editor and a few posts without blocks using the default editor. Please post general Dark Mode problems/screenshots to the comments on 12320.

You can find all other changes/fixes and details in the related PRs targeting WordPress-iOS 13.2 and gutenberg-mobile 1.11.

Where to Report

  • WordPress-iOS on GitHub for non-block-editor issues.
  • gutenberg-mobile on GitHub for block editor issues.
  • This post for questions, feedback, or issues you’re not sure how to report in GitHub.

Thanks for testing! ❤️

Call for Testing: WordPress for Android 13.2

WordPress for Android version 13.2-rc-1 is available for testing on the Beta channel. You can ask to join the Beta Program at Android App Testing on Google Play. Once you have been accepted, click the “Become a Tester” button at the same link.

To test with an apk, you can download wpandroid-13.2-rc-1-universal.apk from here.

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  • Create test accounts at LinkedIn, Tumblr, and Twitter for testing Sharing connections.
  • Have an Author or Subscriber user role setup for at least one test site.
  • Add some files to a WordPress.com test site and click to download them while logged out to generate some stats for testing the new File Downloads section in Stats.
  • Set up a Jetpack site for testing if you don’t already have one. You can use jurassic.ninja to quickly create a Jetpack testing site.
  • Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.

To test:

  1. 10362 Go to My Site and make sure the new quick action buttons work. Check that tapping on Site Name or URL opens site preview. Log in to a test site as an author or subscriber role and note that the Pages button is not there.
  2. 10378 Go to My Site > Sharing and connect a LinkedIn, Tumblr, and Twitter account then make sure sharing works as expected. If you already had any connected, disconnect and reconnect them.
  3. 10276 Go to My Site > Blog Posts, select Everyone in the author filter, check that both list view and cards view (icon at top right) show an author name. Select Me in the author filter and check that the author name is not shown.
  4. 10411 From a WordPress.com site, go to My Site > Stats > Days/Weeks/Months/Years and scroll until you see the File Downloads card. Does everything look good? Are the numbers correct? Repeat the test from a Jetpack site and check that the File Downloads card is not there.
  5. 10425 Go to Profile and check that the following notice appears, “Notification Settings can now be found in the Notifications tab.” Find the Notification Settings in the Notifications tab and make sure they work as expected.
  6. Block Editor: create and publish post using all of the available blocks (Paragraph, Heading, Image, Lists, Separator, Page Break, Quote, More) and check that each one works as expected.

You can find more details about all of the updates for this release in the related PRs targeting WordPress-Android 13.2 and gutenberg-mobile 1.11.

Where to Report

  • WordPress-Android on GitHub for non-block-editor issues.
  • gutenberg-mobile on GitHub for block editor issues.
  • This post for questions, feedback, or issues you’re not sure how to report in GitHub.

Thanks for testing! ❤️

#13-2, #android, #call-for-testing, #mobile

Call for Testing: WordPress for iOS 13.1

WordPress for iOS version 13.1 beta is available for testing on TestFlight. You can sign up for our TestFlight program and join as a beta tester by opening that link on your iPhone or iPad.

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  • Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.

To test:

  1. (12234) Go to Profile > Account Settings, tap username, change the username. Note: if the user is an A8C user you shouldn’t be able allowed to change it.
  2. (12275) Go to Stats > Days/Weeks/Months/Years and verify there is a File Downloads and it has data if downloads have happened on the site you are working with. Disable your network and verify File Downloads still has data.
  3. (12273) Open an existing draft and ensure the ... menu doesn’t show a Stats item and does show a Publish Now item. Make sure Publish Now and all of the other items work as expected.
  4. Block Editor: create and publish post using all of the available blocks (Paragraph, Heading, Image, Video, Lists, Separator, Page Break, Quote, More) and check that each one works as expected.
  5. [UPDATED] Go to Profile > Help & Support and test the Contact Us form. Try sending logs both as an attachment and via copy/paste. (12107)

You can find all other changes/fixes for this release in the related PRs targeting 13.1.

Where to Report

  • WordPress-iOS on GitHub for non-block-editor issues.
  • gutenberg-mobile on GitHub for block editor issues.
  • This post for questions, feedback, or issues you’re not sure how to report in GitHub.

Thanks for testing! ❤️

#13-1, #call-for-tesitng, #ios, #mobile

Call for Testing: WordPress for Android 13.1

WordPress for Android version 13.1-rc-1 is available for testing on the Beta channel. You can ask to join the Beta Program at Android App Testing on Google Play. Once you have been accepted, click the “Become a Tester” button at the same link.

To test with an apk, you can download wpandroid-13.1-rc-1-universal.apk from here.

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  1. Have a publicly accessible Facebook page available, or create one, to use for testing.
  2. Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.

To test:

  1. Go to View Site or My Site > Blog Posts > View to preview content and use the icon at bottom right to change to a desktop view and back again. (10326)
  2. Go to My Site > Sharing > Facebook > Connect and add a published Facebook page. (10376)
  3. Block Editor: create and publish post using all of the available blocks (Paragraph, Heading, Image, Video, Lists, Separator, Page Break, Quote, More) and check that each one works as expected.

You can more details about updates to version 13.1 in the related PRs targeting WordPress-Android 13.1 and gutenberg-mobile 1.10.

Where to Report

  • WordPress-Android on GitHub for non-block-editor issues.
  • gutenberg-mobile on GitHub for block editor issues.
  • This post for questions, feedback, or issues you’re not sure how to report in GitHub.

Thanks for testing! ❤️

#13-1, #android, #call-for-testing, #mobile

Call for Testing: WordPress for iOS 13.0

WordPress for iOS version 13.0 beta is available for testing on TestFlight. You can sign up for our TestFlight program and join as a beta tester by opening that link on your iPhone or iPad.

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see Where to Report below.

Noteworthy: this release contains an update to how the block editor is auto-enabled in the app—it has moved from an app-wide setting in your profile to a per-site setting in site settings.

What to Test

To prepare:

  • Completely uninstall and re-install the app so that you have a fresh install of the app.

To test:

  1. Go to My Sites > Settings and observe the “Use block editor” setting is disabled. Open any post containing blocks. Go to My Sites > Settings and observe the “Use block editor” setting is now enabled. (12066)
  2. Go to My Sites > Settings and disable the “Use block editor” setting. Close and re-open the app. Switch sites. Switch back. Check to make sure the classic editor opens for the site where “Use block editor” was disabled when creating a new post or editing a post created with the classic editor. (12066)
  3. Try to break the “Use block editor” setting. Does it do anything you did not expect? (12066)
  4. Start a new post in the block editor. Open an existing post or draft that has content already, tap on the title, tap the + icon at bottom left, check that an “Add Block Here” indicator is shown. (1219)
  5. Open a post, select the post title, add any “non-text” block (imagevideomoreseparator, or page break), and make sure the cursor is no longer active in the post title. (1231)
  6. Start with a site with the timezone set a day ahead of your local timezone. Go to My Sites > Stats > Days/Weeks/Months/Years and check that a “Site timezone” label appears showing the offset from UTC.(12159)
  7. Go to My Sites > Stats > Days/Weeks/Months/Years and verify changing the date via the bar or the chart works as expected and matches the same view from Calypso (especially the Days view). (12159)
  8. Go to My Sites > Stats > Insights and verify Today shows today’s stats. Go to Year > View more and verify the date bar behaves as expected. Verify the Latest Post Summary chart is correct. (12159)
  9. Go to My Sites > Stats > Latest Post Summary and click a post to open post stats and verify the date and chart behaves correctly and that the chart data is correct. (12159)
  10. Go to My Sites > Settings and change the site timezone. Go to My Sites > Stats and verify the date bar is updated accordingly. (12159)

You can more details about updates to version 13.0 in the related PRs targeting 13.0.

Where to Report

  • WordPress-iOS on GitHub for non-block-editor issues.
  • gutenberg-mobile on GitHub for block editor issues.
  • This post for questions, feedback, or issues you’re not sure how to report in GitHub.

Thanks for testing! ❤️

#13-0, #call-for-tesitng, #ios, #mobile

Call for Testing: WordPress for Android 13.0

WordPress for Android version 13.0-rc-1 is available for testing on the Beta channel. You can ask to join the Beta Program at Android App Testing on Google Play. Once you have been accepted, click the “Become a Tester” button at the same link.

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see Where to Report below.

Noteworthy: this release contains an update to how the block editor is auto-enabled in the app—it has moved from an app-wide setting in your profile to a per-site setting in site settings.

What to Test

  1. Delete the app, do a fresh install, tap “Log in”, tap “Help” at top right and verify the app does not crash. (10302)
  2. Go to My Sites > Settings and observe the “Use block editor” setting is disabled. Open any post containing blocks. Go to My Sites > Settings and observe the “Use block editor” setting is now enabled. (10254)
  3. Go to My Sites > Settings and disable the “Use block editor” setting. Close and re-open the app. Switch sites. Switch back. Check to make sure the classic editor opens for the site where “Use block editor” was disabled when creating a new post or editing a post created with the classic editor. (10254)
  4. Try to break the “Use block editor” setting. Does it do anything you did not expect? (10254)
  5. Start a new post in the block editor. Open an existing post or draft that has content already, tap on the title, tap the + icon at bottom left, check that an “Add Block Here” indicator is shown. (1219)
  6. Open a post, select the post title, add any “non-text” block (imagevideomoreseparator, or page break), and make sure the cursor is no longer active in the post title. (1231)
  7. Open a post that has an image block in it, add a caption, select caption text and add formatting (i.e. bold), verify the image caption remains horizontally centered. (1243, gutenberg/16722)
  8. Go to Sites > Switch Site, click on the + button at top right, enter a site address and verify an error is only shown if you have not typed anything for at least 2 seconds and that the Next button is only enabled if the URL is valid. (10255)
  9. Log out, tap “Log in”, tap “Login by entering your site address”, enter a self-hosted site address and verify an error is only shown if you have not typed anything for at least 2 seconds and that the Next button is only enabled if the URL is valid. (10255)
  10. Go to Settings > General > Accessibility > VoiceOver Settings > Accessibility > TalkBack and toggle the setting on. Go to Stats and explore. Is anything broken? (10274, 10277)
  11. Browse through various screens from the app and look for any colors different from Color Studio v2.0.0 colors. (10283)

You can more details about updates to version 13.0 in the related PRs targeting 13.0.

Where to Report

  • WordPress-Android on GitHub for non-block-editor issues.
  • gutenberg-mobile on GitHub for block editor issues.
  • This post for questions, feedback, or issues you’re not sure how to report in GitHub.

Thanks for testing! ❤️

#13-0, #android, #call-for-testing, #mobile

Call for Testing: WordPress for Android 12.9

WordPress for Android version 12.9-rc-1 is available for testing on the Beta channel. Request to join the Beta Program at Android App Testing on Google Play. Once you have been accepted, click the “Become a Tester” button at the same link.

Bugs & Feedback

If you find a bug or come up with a feature request while testing, you can comment here, or ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see Where to Report below.

What to Test

  1. From the Reader or from the My Site > Comments > Comment Detail screen, use the expand/collapse icon to expand the view when editing a comment. (10140)
  2. Block editor: add a video block to a post and try to break it. (1150)
  3. Block editor: on the web, create a group block as described at 1206 or use the sample content noted in 1209 then open the post in the app and make sure no content is lost.

You can more details about updates to version 12.9 in the related PRs targeting 12.9 and 1.9.

Where to Report

  • WordPress-Android on GitHub for non-block-editor issues.
  • gutenberg-mobile on GitHub for block editor issues.
  • This post for questions, feedback, or issues you’re not sure how to report in GitHub.

Thanks for testing! ❤️

#12-9, #android, #call-for-testing, #mobile

Call for Testing: WordPress for iOS 12.9

WordPress for iOS version 12.9 beta is available for testing on TestFlight. You can sign up for our TestFlight program (open the link on your iPhone or iPad) to join as a beta tester.

Bugs & Feedback

If you find a bug or come up with a feature request while testing, you can let us know in the comments, or ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see Where to Report below.

What to Test

  1. Be offline, go to Blog Posts > Published or Drafts, tap the “Create Post” button, you should see a save draft option when exiting and the post should then be created as a draft and queued for upload. (12023)
  2. Block editor: add a video block to a post and try to break it. (1150)
  3. Block editor: open any post with the block editor, tap on the empty editor area, a new paragraph block should be added. (1200)
  4. Block editor: open a post with at least one block in the content area, tap the Title, add any block, make sure the new block is added at the top of the post. (1201)
  5. Block editor: open a post with at least one block in the content area, make sure no block is selected, add any block, check that a new block should be added to the bottom of the post. (1201)
  6. Block editor: open a post with at least one block in the content area, make sure an existing block is selected, add any block, see that a new block is added below the previously selected block. (1201)
  7. Block editor: on the web, create a group block as described at 1206 or use the sample content noted in 1209 then open the post in the app and make sure no content is lost.
  8. Go to Blog Posts and observe there is a new compact layout option. Try to find any problems you can with the Blog Posts screen. (12087)
  9. Go to Blog Posts and check that the post list matches the mockups in 11646. (12087)
  10. Go to My Sites > Switch Site > “+” (at top right) > “Create WordPress.com site”, follow the prompts until you see a site preview, make sure you can scroll all the way down to the bottom of the site and the “Done” button doesn’t block the site view. (12052)
  11. Go to My Sites > Switch Site > “+” (at top right) > “Create WordPress.com site”, accept help when offered assistance, in “Customize Your Site” tap “Upload a site icon” and make sure it behaves well. Try it multiple times in a row. (12051)
  12. Using a very poor network connection, go to Blog Posts > Published, open a post, update it, tap “Preview”, you should see “Generating Preview” in the nav bar. Make sure you can exit the editor and perform other actions. After exiting, the nav bar in the editor should go back to its previous state and no longer say “Generating Preview”. (12031)

You can more details about updates to version 12.9 in the related PRs targeting 12.9 and 1.9.

Where to Report

  • WordPress-iOS on GitHub for non-block-editor issues.
  • gutenberg-mobile on GitHub for block editor issues.
  • This post for questions, feedback, or issues you’re not sure how to report in GitHub.

Thanks for testing! ❤️

#12-9, #call-for-testing, #ios, #mobile

X-post: Updates to the WordPress User & Developer Survey

X-comment from +make.wordpress.org/updates: Comment on Updates to the WordPress User & Developer Survey

Call for Testing: WordPress for Android 12.8

WordPress for Android version 12.8-rc-1 is available for testing on the Beta channel. Request to join the Beta Program at Android App Testing on Google Play. Once you have been accepted, click the “Become a Tester” button at the same link.

Bugs & Feedback

If 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 room on WordPress.org Slack, or head straight GitHub and open an issue—please see Where to Report below.

What to Test

  1. Using 12.8-rc-1 or later, go to Me > App Settings > Use Block Editor to enable Gutenberg Mobile for testing on new posts. Posts created using Gutenberg on the web should open in Gutenberg on the app regardless of what is selected in App Settings.
  2. Widgets for All-time, Today, Weekly Stats are now available for your device home screen. (10122)
  3. Block editor: Open the editor (a new post or existing post), select the Post Title field, delete any existing title content, and paste some text inside the empty Post Title. Check that pasting works as expected. Press Enter and check that it creates a new block and that gets focus as expected. (16116)
  4. Under My Sites > Stats in the Posts and Pages, Authors, Tags and Categories sections, a percentage bar has been added to graphically show the impact of each item. (10073)
  5. On a site using Jetpack, go to My Sites > Blog Posts and tap the search button. Try different searches and confirm that the search results work as expected. (10023)

Find all other changes/fixes and details in the related PRs targeting 12.8 and 1.8.

Where to Report

  • WordPress-Android on GitHub for non-block-editor issues.
  • gutenberg-mobile on GitHub for block editor issues.
  • This post for questions, feedback, or issues you’re not sure how to report in GitHub.

Thanks for testing! ❤️

#12-8, #android, #call-for-testing, #mobile