Hey hunters,
Waldo is back with the first release of their new product Sessions. It helps mobile teams test their apps right from the browser. Super neat. You should check it out!
Thanks a ton for hunting us @dessaigne !
Hi everyone, I am Laurent, the CTO of Waldo.
I am super excited about this new product that we’re launching.
After spending some / a few / a good number of years on building the best (we hope) tool to automate mobile apps, we’ve decided to give away some parts of the technology to serve more use cases around mobile testing.
One of the most common frustration we hear from mobile teams is how hard it is to **share** information around a mobile user flow:
😠 it’s hard for product and developers to efficiently do a new feature review. Sure, both can run the pre-release build on their own, but what if a button is not properly implemented and does not correspond to the original specs? where do you capture that?
😠 it’s hard for developers to know what to do when they receive a bug ticket that states “Login button does not work”. Sure, there might be a few more details in the ticket than that, but more often than not the ticket will get closed as “cannot reproduce” because there’s simply not enough information and context to work with
😠 it’s hard for mobile teams to share with the rest of the org what just got shipped. A Changelog.md is great, but that’s far from giving the real picture..
We’ve made Waldo Sessions with all those use cases in mind. It allows to run your app on any device right from the browser, to annotate at specific time of the session, and to share the replay with its full context:
😃 the review is now a breeze: the developer records the new feature flow, the product manager goes over the replay and annotates all its nits along the video.
😃 in case you notice a bug, you simply share the link (better yet, at the time it happened) and the developer has all the information to debug: logs, network requests, video stream, list of gestures.. there’s no need to reproduce, all the information is already there.
😃 and that replay link also becomes the best way to showcase your next great feature with the rest of the org!
We’re really looking forward to all your feedback on this release, we hope you like it!
@dessaigne@laurentsigal Great job, Waldo team! Waldo Sessions seems like a game-changer for mobile app testing and collaboration. Can't wait to try it out! 👏👏👏
I'm excited that our team has just released Waldo Sessions! We've been working hard on this tool and we're proud to have it out in the wild.
If you're tired of manually checking the latest builds on every PR, then Waldo Sessions is perfect for you. With this all-in-one tool, you can easily preview all the latest builds, and what's even better is that you can share a video that includes all the interactions, console logs, and network requests. This will help you close the feedback loop and streamline collaboration across teams, which is super important when it comes to delivering high-quality apps.
I'm talking to developers and QAs every day and they all share how challenging it can be to ensure that your app is top-notch. That's why we've made Waldo Sessions free for everyone to use. So, if you're involved in building mobile apps, give it a try and let us know what you think!
We have been Waldo customers for years running 2 apps with 4 mobile engineers and one part time QA person for 10m active users.
This is a logical next step and I can’t wait until we have it as part of our Eng workflow
Thanks for your support @philippberner ! and you haven't seen yet what we have in stock for the next steps of Waldo Sessions! I'll be super happy to discuss this with you.
@flexbox totally! You are usually good to go without any problems, but sometimes, react native builds lack the main.jsbundle file. We have a short medium article dedicated to this issue if it arises: https://onexlab-io.medium.com/no...
Great product with a smooth onboarding! Always great to be able to test your app on multiple devices before releasing your build 🙌
In love with the 🦙 !
Congrats on the launch! 🎉
For discussing the June report metrics with @manou_febvret and @Edouard from time to time, I can tell you that Waldo’s stickiness is through the roof! Well done Waldo!
Hi everyone, I'm the PM behind Waldo Sessions, excited to launch today as we have worked a lot these past months to provide a smooth experience for Waldo Sessions, and make Waldo more accessible. I'm pretty happy with our "time to magic" now: see by yourself, give it a try, and Ask Me Anything, I'll follow this thread the whole day. 🚀
@laurentsigal - Congrats on the launch. It is interesting to have a collaborative tool like Waldo Sessions that allows mobile teams to run pre-release builds on any device right from the browser.
How does Waldo Sessions integrate with other mobile app testing and collaboration tools commonly used by mobile teams, such as Jira or Slack?
@salil_sethi Waldo takes care of the run and capture part, but for now it does not try to own the conversation.
In other words, you run your manual QA on Waldo, if anything weird happens you can annotate and / or share the link, and bring it to your existing collaboration tools like Jira. It will look like this: "can you look into this bug => app.waldo.com/{replay}" and that will provide all the info. A bit like how Sentry provides the full stack trace and info about any error that happened, but then you can collaborate around it on Slack or Jira.
I'm so happy to be part of this amazing team that is constantly pushing the boundaries of what's possible. The team has been working hard to release Waldo Sessions so people can inspect and debug their app in an all-in-one tool without any local setup!
@marclou agreed 💯 ! Meeting @manou_febvret in my interviews was decisive in my decision to join Waldo a few months ago 🫶. And he is not just a super talented designer, he is also a great guy to work with :)
I think this feature could be as big as a change in Product Development than when Figma was introduced... The ability to play with a iOS simulator directly from the browser, test a new branch, and comment inline is absolutely game changer.
Algolia