Call for Testing: Second Android Beta

Hi everyone! I’m Aaron, one of the people leading the team working on the upcoming WooCommerce apps. We are ready with the second beta of the Android app. Thanks to everyone who installed the first beta and gave us feedback – it is appreciated!

You’re running a store, you can’t always be sitting at a computer, and frankly, some things might be done better on a mobile phone. We want to help!

What is it?

While this is the second step on a longer journey to build many of WooCommerce’s features in this companion app, this app is already providing some useful features that can make your work easier and faster โ€“ especially on the go.

  • You can check basic orders and revenue statistics with time period selection.
  • You can view orders list in chronological order, with status and total value.
  • You can review individual orders with all the standard details, and contact customers.
  • You can perform basic order fulfilment.

 

Coming soon

There are some features that we plan to add before the first public release:

  • You’ll get notifications about orders and reviews, and the ability to moderate them.
  • You’ll see a list of the top selling products on your store.

These are coming soon, with much more on the way so stay tuned!

How to join the test?

If you’ve already installed the first beta of the app, check the Play Store for updates.

If you haven’t helped test the first beta, just follow the instructions on how to join the Android beta.

What to test?

Try doing these tasks:

  1. Check the reported orders and revenue and see if they match what you see in WooCommerce Reports on web. Make sure to try changing the time periods between “days”, “weeks”, etc.
  2. Verify that the name of your store matches on the Settings screen.
  3. Check the list of orders and verify the “infinite scroll” works properly if you have more than 50 orders on your site.

Where to report your feedback?

Sharing your feedback or issues is simple: just comment on this post. Add separate comments for every issue so we can reply specifically, or write one comment with all your thoughtsย  — up to you. And if you’re new to testing,ย take a look at these tips on writing great feedback.

We are aiming to gather all your feedback in the next two weeks, and close this round of testing on July 31st.

Thank you!

Published by

Aaron Douglas

Geek to the core. Mobile (iOS) Maker @ Automattic by day, occasional photographer & gypsy by night. I like to know how things work and that drives my being.

9 thoughts on “Call for Testing: Second Android Beta”

  1. Still no delineation between the features that actually need Jetpack and those that don’t ๐Ÿ˜ฅ

    Can’t blame me for hoping.

    (PS: your ‘skip the call for testing’ link in the email, sends people to the Beta 1 page. Not sure if you send these emails out at once or in waves, but if it’s the latter, you might want to fix it.

    Liked by 1 person

    1. Hi Dovid! Thanks for letting me know about the e-mail. I forgot to edit those links before scheduling the e-mail – oops.

      Regarding Jetpack we did add a note in the FAQ about the requirement and what exactly it provides. Hope that helps!

      Like

      1. Yeah yeah I know ๐Ÿ™‚ I had this conversation on the 1st beta post.

        And while admittedly I don’t know how y’all coded this, from my understanding of the APIs (and non-Automattic WC apps), I still maintain that a large portion of this functionality does not need to be locked behind Jetpack.

        Even if you were to say that Jetpack is only a current requirement, and the long-term plan would be to take the same approach as the WordPress App (that only locks the functionality that _actually_ needs Jetpack to work), it’d silence a bunch of detractors.

        Until then, I’ll just be keeping my fingers crossed ๐Ÿ™‚

        Liked by 1 person

      2. PS speaking of the FAQ:
        Would you mind clarifying a bit why the same XML-RPC notice/troubleshooting steps suggested on the WordPress App would fall short in this scenario (again assuming jetpack was still used for unsupported endpoints, eg how it is required for Stats).

        Similarly – do Push notifications in the WordPress App only work with jetpack enabled? For the life of me I can’t remember and when I checked the FAQ for that app, there’s no mention of the Jetpack requirement. If it isn’t required, then why would it be here?

        To be clear, I’m really not trying to trash all the amazing work on this app, and the obvious potential here. It’s just between the lack of clarity as to whether the Jetpack is a temporary solution to either simplify beta testing or until the issues mentioned in the FAQ (like missing endpoints in core) are resolved, and the fact that while the FAQ spends a lot of time discussing the technical aspects it comes off as a superficial explanation to a forgone conclusion, it’s hard to keep from scratching our collective heads.

        Like

        1. Dovid, thank you for your reply. You point about clarity is good, so let me add it here: Jetpack is not a temporary solution. There’s a large number of people that use WooCommerce and Jetpack, so as it’s a small team working on it, for the foreseeable future we aren’t going to deal with all the additional complexity that non-Jetpack sites will include.

          While this means that it’s not an option on the table right now, it also doesn’t mean we won’t reconsider it in the future โ€“ say, a year from now โ€“ as the technical and market considerations will shift.

          I’m aware this isn’t the answer many of you expect, and I understand this means some of you won’t test the app for this reason. I’m also sure that you all can understand โ€“ as both business people and developers โ€“ how the balance of constraints and marketplace can shape decisions.

          There will be a moment in the future to review the Jetpack decision, just, this moment isn’t now. The best thing you could do today is to help us make sure this app ships without bugs and it’s successful. ๐Ÿ™‚

          Liked by 1 person

Comments are closed.