Eppo Reviews

My main use case for Eppo is AB testing to determine which particular module works best for us or which particular UI layout works best for us. We also plan to use it to manage our rollouts. If rollouts to our users fail and we want to switch back certain modules that we believe are not performing well, we can switch them off without releasing an actual build. These two are our primary use cases.

The primary challenge we face is running AB testing on our different modules to drive our return on investment so that we can have a better understanding of our users' cohorts and can target more paying users with better modules and better UI features.

In my opinion, the best features Eppo offers are its intuitive UI and dashboard, which are very intuitive. The experimentation capabilities are also excellent, as Eppo offers the ability to experiment on different new UI designs, algorithms, and machine learning models to see how they impact user behavior.

Eppo has positively impacted our organization so far because we can better plan our future releases. If something fails in the production environment, we can easily roll back that feature without having to wait for the whole app cycle review that Apple and Android require, so users are not immediately impacted if something fails in the production environment.

Since we have not deployed Eppo in the live environment yet, I cannot share measurable improvements. However, it will definitely help us preserve our users from uninstalling our app, as if something fails, we can switch it off remotely and the user experience will not be hindered.

Eppo seems pretty complete to me at this point, and nothing appears to be missing. I have nothing to add regarding needed improvements or features I wish were different.

I have used Eppo for around four months.

Based on my experience so far, Eppo is quite stable, and there has been no downtime during my testing.

It is still early to say how Eppo's scalability will perform, but according to my understanding, it should be pretty scalable and should be able to handle any future traffic loads.

I personally have not interacted with Eppo's customer support, and no need arose to conduct a customer support call. However, in my assessment, it should be good.

We used Firebase in the past and are still using it. We are in the process of finding a better solution, and Eppo was one of the contenders that we tested.

Eppo has not been deployed yet in my organization.

I am part of the engineering team, so the pricing, setup cost, and licensing for Eppo are handled by the finance team, and that information is not available to me.

It is too early to say if we have seen a return on investment. However, we definitely believe that it will lead to cost savings since we will be able to better plan our releases and better target users.

I am part of the engineering team, so the pricing, setup cost, and licensing for Eppo are handled by the finance team, and that information is not available to me.

Before choosing Eppo, we evaluated other options, specifically Firebase for this particular use case, but the results were not satisfactory. We then found out about Eppo and are in the process of rolling it out.

Eppo's accuracy and reliability of output are quite good, as it consistently switches off and provides better AB testing capabilities.

My advice to others looking into using Eppo is that they can try it, as it is a good product. I found this interview valuable and have no suggestions for change in the future.

I would appreciate a short poem or haiku that summarizes this review. I give this review a rating of eight out of ten.

We are looking for someone experimental and feature flagging, so we are evaluating some applications, libraries, and SDKs, and we found Eppo is one of the great options, so we are integrating that.

For the LiteX application, we are trying to do feature flagging, as we have two applications like image to video or text to video options, and we want to determine which type of model will generate more revenue or be more user-interface friendly for users. We initially tried to do this with Firebase, but we did not get much result from that, and some results were confusing too; perhaps we were not able to understand, or something else was the issue, but we are now exploring other options, so we are exploring Eppo.

I am looking for a way to run experiments where we can have 10% of users on experiment A and 10% on experiment B to get a real example of how many users are interacting with that model and how much our revenue is going, so we want to split that way.

Based on my exploration, I find Eppo to be more powerful in providing result-oriented, data-oriented results for feature flagging and experiments. I am expecting that if Eppo tracks data on how 10% of users are engaging with experiment A and 10% with experiment B, it will provide insights on how many users are using our features and how much revenue generation is occurring. That type of data is what I think Eppo will work more result-oriented on. The main thing we are looking for regarding features is that Eppo stands out to me because I am exploring something, and the data is easily aligning with our needs.

Eppo is stable, and I have not encountered any crashes or issues. Based on our early evaluation, I see that Eppo will work great for me regarding the accuracy and reliability of its output.

I do not have anything to add about my main use case or how I hope Eppo will help.

Till now, I do not have any improvement points, so I cannot comment on that at this time.

I do not want to add more about the needed improvements for the evaluation or integration process.

Until now, we have not deployed Eppo; we are still exploring options.

Based on my evaluation so far, Eppo is stable, and I have not encountered any crashes or issues.

I am hoping that Eppo's scalability will handle growth as our usage increases.

Until now, I do not prioritize customer support much because if the finance team has connected with them, my team as developers or engineering managers has not coordinated with any customer support.

I was using Firebase as a different solution for feature flagging and experiments.

We are still in the evaluation phase, so we cannot determine how much Eppo has helped us; that will be determined in the future. I am expecting that Eppo will work closely with our needs, leading to improvements.

So far, there have been some challenges in integration, particularly with SDK detailing, but overall I have managed to work through the process, and we are trying to experiment with something and evaluate.

It is too early to tell if we have seen a return on investment because I am still exploring, so I cannot answer that yet.

The pricing, setup cost, and licensing are part of the finance team, so I am not able to answer that.

Until now, we are exploring other tools such as Split and Statig. I have explored Statig before choosing Eppo among other options.

I found that competitors such as Statig and Firebase do not provide me actual results, which is why I am switching to Eppo.

We will use something else for other purposes. For feature flagging, we will not require Azure; based on my exploration, if we determine which SDK we are using, we will not deploy on AWS or something similar.

I am hoping that Eppo will work closely with our data and provide better results, unlike the experiences we had with Firebase. I am hoping Eppo will perform better compared to others. I would rate Eppo as nine overall based on the process we have experienced so far.