Eden Full Goh’s Post

One of the best parts of my job at Mobot is getting a chance to connect, learn from, and work with great cross-functional business leaders like Satya Ramachandran. 6 years into my founder journey, I'm still learning something new every day from our partners and customers about the different ways that Mobot's technology can be applied to a wide range of different industries.

Wondering if Mobot’s managed services or using Mobot Live yourself is a better fit for your iOS and Android product development? It all comes down to the resourcing that's available on your team. If you have a dedicated automation and manual testing team, you may have the time to be able to build out your own in-house effort, leveraging multiple tools on the market. You're simply looking for automation platforms that will be able to augment your toolkit, covering features and use cases that other solutions cannot.This is where Mobot Live comes in. It can be a great offering for engineering, QA, product, and marketing teams that want to have full control and visibility over every aspect of their mobile product, test cases, and execution status. On the other hand, for those teams and businesses that are stretched for time or have limited resources, Mobot has a managed services offering that can be really useful. Our expert team will do all of the heavy lifting of test case authoring, automation, setup, and execution for you, followed by the ongoing maintenance and management so that every team at your company can quickly add test cases, request testing, receive reports, and digest them through aggregated analytics. Our managed services platform also enables critical stakeholders to be able to give feedback as needed.This allows your team to focus on building new features and delivering builds to the App Store and Google Play, instead of worrying about regression testing. Have any questions about Mobot’s offerings? Leave them in the comments below.

👋 How does Mobot Live allow iOS and Android teams to say goodbye to manual testing? There are a few instances where manual testing can occasionally be useful: ✔️ You've created a new mobile product feature for the first time and want to gather usability/user experience feedback. ✔️ You want to evaluate if the UI of the product is polished and meets design guidelines. If you’re still manually testing without learning anything new after a feature has been stable in production for many releases in a row, it no longer makes sense to cover that with manual testing. Mobot aims to empower teams to stop manually testing when it is no longer necessary. Human time should be spent on manual testing when it involves high leverage responsibilities that require human instinct and creativity, like the two examples above, not pressing buttons on a screen over and over again. Mobot Live creates operating leverage for engineers, QA professionals, product managers and mobile marketers because you can: 👉 Build one workflow 👉 Execute the test multiple times 👉 Run it on multiple devices in parallel 👉 Get feedback and execution patterns faster For example, you could be testing on three phones at the same time and watching them run in Mobot Live, rather than serially testing one device at a time using phones on your desk. Mobot’s system enables teams to efficiently cover multiple workloads and responsibilities. That’s how we want our customers to experience testing and product monitoring through a modern, mobile-first product development tool. Instead of inefficiently executing tasks one at a time, our robots democratize access to more devices and more flexibility. In a world where products are increasingly used in the physical world on a staggering number of hardware devices, we're driving automation in a way that previously has never been done before by automating the non-automatable. Want to learn more about Mobot Live? Head to our website. https://lnkd.in/dx7cjd7b

🎉 Here’s a cool success story of one of our Mobot Live customers. As an identity verification SDK, one of Mobot’s customers built different versions of their toolkit to run on native iOS, native Android, React Native, Flutter, and mobile web reference apps. Their goal is to build a universal SDK that can be leveraged across all of these different platforms. This customer was having challenges with automating the same test case across all of these different apps, so they approached Mobot about leveraging our solution to support their development workflow. Every time their engineering team deploys a new version of their SDK, their engineers want to be able to quickly test it on other devices. They have a suite of automated regression tests that are managed and executed by Mobot daily on a standard set of iOS and Android devices. In addition, their team also needs to be able to access additional devices on a more ad hoc basis. As an identity verification SDK, confirming that the SDK is compatible with the actual device camera on a variety of iOS and Android hardware manufacturers and models is extremely important. If testing is not sufficiently comprehensive, images captured in production could be invalid, blurry or incorrect. Having direct access to Mobot Live is highly beneficial. At a moment’s notice, an engineer can use the physical camera from an iPhone 12 running iOS 17, an iPhone SE 3rd gen running iOS 16, a Motorola device running Android 10, and much more. This gives them a lot more flexibility and agility during the software development process. This drives faster release cadences and fewer bugs, which is especially critical when writing code that manifests outcomes in the physical world. Want to learn more about Mobot Live? Head to our website. https://lnkd.in/dx7cjd7b

📱What’s one of the biggest benefits of Mobot Live? Our newest offering, Mobot Live, allows engineers, product managers, marketers and QA professionals to access an expansive catalog of devices that they do not physically have in their possession. Especially in a post-pandemic world of remote work, it has been increasingly difficult for teams to ensure that they have optimal device testing coverage in their product development strategy. Rather than worrying about owning and managing all of the different devices, operating systems, and variations that exist on the market, Mobot Live provides you with instant access to the necessary hardware in the cloud, all within your browser. With our control interface and camera feed, we give you access to a broader set of devices for automating tricky test cases that cannot be covered by existing software frameworks. Our solution can be complementary to any existing test automation that teams may have implemented already. By accessing these physical devices in the real world, Mobot Live now empowers our users to automate and scalably execute test cases on a recurring basis that were previously un-automatable, such as push notifications, home screen widgets, camera testing, multi-device testing, and more. Want to learn more? Head to our website. https://lnkd.in/dx7cjd7b

💭 Why did we build Mobot Live? Over the last few years, we’ve been supporting iOS, Android, engineering, product, QA and marketing teams by providing a co-managed solution that enables teams to import their existing test cases into the Mobot platform. Our team collaborates and partners with our customers to set up their automated testing and monitoring workflows on our robot fleet for execution. Through this process, we started getting feedback from some of our customers that they would like to have a chance to directly train, control and update the tests themselves. This would unlock more efficiency and control, especially for opportunities like live debugging and troubleshooting directly on the test device after Mobot has surfaced bugs. This is where Mobot Live comes in. With Mobot Live, teams can now control their own robot interacting live with an iOS or Android device in the cloud, collecting their own logging and reporting, generating assets that can be shared with their teammates and attached to bug tickets and internal product documentation. We are excited that Mobot Live provides additional capabilities for new and existing Mobot customers across various use cases, including: push notifications, home screen widgets, camera testing, multi-device testing, and much more. Learn more about it on our website. https://lnkd.in/dx7cjd7b

🚀 Introducing: Mobot Live. Our team at Mobot has been hard at work building the future of iOS and Android automation and empowering engineering teams, QA teams, product teams, and marketing teams to be able to have more control over the kinds of test cases that they can execute. Mobot Live is an offering that we've built to enable anyone, anywhere around the world, to be able to control a robot in the cloud from their own web browser. How does it work? Our users can log in, select the device they want to use, and then access an interface to control the robot, referencing a real-time camera feed. Wherever the user clicks on their screen, they can actually see the robot respond in real time to execute the corresponding action, recording a sequence of steps that can be rerun as many times as they want in the future. This drives the ability to automate workflows that were previously manually laborious. Test cases that were deemed un-automatable in the past — such as push notifications, home screen widgets, camera testing, multi-device testing, and more — can now be automated using Mobot. We can even have multiple robots running side by side in sequence with each other for a regression test case or product monitoring flow. For the first time in our industry, Mobot Live places the power in our users’ hands to control a robot testing software on a physical device in the cloud. What more could you ask for? Learn more about it on our website. https://lnkd.in/dx7cjd7b

👎 Nothing will make a user uninstall your iOS or Android mobile app faster than intrusive ads that hinder their user experience. However, that doesn’t mean that your app can’t have ads at all — it just means that you need to be intentional about how you use them, with a robust strategy for configuring and monitoring each asset. This means two things: ☑️ From a technical perspective, configured ads should be rendering correctly on the screen. When a user taps on the ad, the asset should deep link the user to the correct destination. This could be an App Store/Google Play installation page, a deep link in your native mobile app, a deep link to a third-party partner’s native mobile app or a particular mobile website in a mobile browser. This involves having a level of trust with the user. ☑️ Additionally, from a usability and a product perspective, the ads should render well on different screen sizes, with different aspect ratios, colors, styling and accessibility settings. The ads should not disrupt the core user flow or overlap other components in the native iOS/Android app. Both of these requirements are business critical and involve making sure that the ads not only work properly but also placed intentionally. It may entail asking these questions: 👉 What is the right deep link strategy for a particular mobile ad campaign? 👉 Are the ads being inclusive of different audiences? 👉 What happens when the phone is in portrait versus landscape mode? Do the ads stretch or handle variable aspect ratios correctly? 👉 Are the ads on the right part of the screen? 👉 Do the ads need to be dismissed? 👉 Can users still perform actions in parallel on the app? There are a lot of considerations there. Prior to configuration and monitoring, effective mobile ads require thoughtful product research. Building this long-term strategy provides a scalable schema for how mobile ads are to be implemented. This provides guidance to marketing, product, growth and engineering teams that must collaborate cross-functionally. How does your company’s mobile app use ads?