New  O4S is now a Great Place To Work Certified™ Workplace!   Read More

Rapid Mobile Development for Product Experimentation

If you ask a product guy what kind of mobile app they want to build, or what future they think of their mobile app, they’ll most probably say that they want to build something like Facebook! It’s no surprise that everyone dreams of building a super app, but what’s important to know and understand is how to achieve that dream!

Therefore, today in this podcast we’ll be discussing one of the methodologies that are being adopted by companies who aim to get the most out of their mobile application, which is ‘Rapid product experimentation for a Mobile application’.

As the name suggests, experimentation in terms of a mobile application means testing out an idea or a hypothesis on a segment of your users and seeing if the results align with the intent or the expected outcomes. It provides a structured approach to discovering unbiased learnings or outcomes and helps you in uncovering the real reason behind the changes in any data or metrics.

It is very critical to do experiments in your applications with features, designs, user flow, and user segments, even with the goal of the product. This helps you to keep your app live. Every product has a deadline, and an expiration date. Unfortunately, it’s hard to determine when it will be. However, if you keep innovating on ideas and testing them out with rapid experimentations, you’ll be able to keep adding something new to your application and make it feel alive and active for your users.

But of course, it’s not as easy as it is being said. For that, you need to have a strong technical team as well, both on the front-end & the backend side. Doing experiments with your mobile application is like creating a deformity in your currently perfectly running product and seeing if it actually degrades it or if it evolves into an enriching feature for your users. To introduce such deformity in your product, you need to ensure that your current product, your mobile application, is running smoothly, and if the experiment fails that it can easily be rolled back to its original state without breaking your product, or code and your users’ experience. Thus you need to shift to a more modular approach than a monolithic approach for your product, which is explained pretty well by our engineer in the podcast.

Additionally, before conducting the experiment on your mobile application, you should be aware of:

  1. What kind of experiment do you want to do on your application?
  2. What type of experiment do you want to do: A-B testing or Split testing or others?
  3. What is the intended outcome?
  4. What metrics to analyze to determine the results?
  5. What will be your rollback option?
  6. If it succeeds, then how do you want to roll it out further?
  7. And if failed, what have you learned from the experimentation and how can you use the insights to create new experiments!

To know about the whole process and more about the ‘Rapid product experimentations’, please check out our podcast! Click here to watch.


O4S raises Series A investment. To be announced soon. Read More