Instabug - Ultimate

My main use case for Instabug  is testing and reporting while testing mobile applications. I have tested or started doing tests with Instabug , and while testing, I noticed errors, crashes, or other defects. I shake my phone and report via Instabug to see the logs, what is happening, the steps that were reproduced, videos, and screenshots.

The best features Instabug offers are very useful, helpful, and informative in the logs of what is happening with the mobile application. When I mention the logs, I find the information detailed enough to quickly diagnose issues. Instabug has positively impacted my organization because it helps identify bugs and enables real users to report bugs easily to us, allowing us to find the core issue, what is happening, and on which device. It is really informative and helpful for the developers and for me as a QA to find out what the issue is and what happened.

I think it is a very interesting question regarding how Instabug can be improved, but I have not thought about it. Everything is working well for me.

I have been using Instabug for three years.

Instabug is stable.

The customer support for Instabug is great, really fast, and helpful. I would rate the customer support on a scale of one to ten as nine.

We did not previously use a different solution before Instabug.

I have seen a return on investment while using Instabug; it is really helpful and we can report so fast. However, we stopped using it because of the company's issues with the cost.

My company has recently stopped using Instabug because of the pricing; it was really expensive for my company. The overall cost made the pricing feel too high.

We did not evaluate other options before choosing Instabug; it was a startup and we started using Instabug right away.

The advice I would give to others looking into using Instabug is to use it because of its really reliable features and tools, which are also really helpful, informative, and fast. Users can report issues really fast, and we receive them really fast and can react on them. I would rate this product a ten out of ten.

I primarily use Instabug  to monitor the performance of my app, to report any crashes, and to get feedback from our beta users.

For some new modules we are trying to develop in our application, I initially get them tested by a set of beta users. I directly use Instabug  to generate feedback and beta user crashes. Users can submit their feedback and crashes by simply shaking their phone, and through that method, the collection of this particular feedback and crashes is quite easy.

That is the primary use case for Instabug.

The shake to report a crash feature is excellent, and the performance monitoring is also strong.

Since the gathering of crash reports is seamless while using Instabug, a more refined product is delivered to final users from the beta to deployment stage. The crash-free user percentage has drastically improved since I started using Instabug.

At my previous company, the crash-free user percentage was above 99.5% crash-free users for over a million monthly active users.

The QA team efficiency has greatly improved, so fewer QA cycles were needed, which saved a considerable amount of time.

Sometimes the reporting with Instabug is a bit delayed, and that can be improved. Crash reports usually take a few minutes to get reported, which represents room for improvement.

A better live reporting experience is something I noticed. The delay in reporting can be improved.

If the delay in the reporting is addressed and live crash reporting is provided, that would be a significant advantage for me to rate the product a 10.

I have used Instabug for around four years in my previous company, and I am recently trying to use it again for some of my new projects.

Instabug is stable, and I have not faced any difficulties in that regard.

Instabug is quite scalable as it can handle a substantial volume.

I have not interacted with the customer support team of Instabug, as it was never needed. The requirement for customer support was never necessary.

At my previous company, I used Crashlytics earlier, then in addition to Crashlytics, I also deployed Instabug, particularly for the beta testing phase. That deployment improved a lot of features for us.

Earlier I was using Crashlytics, then I switched to Instabug specifically for the beta phase.

The pricing, setup cost, and licensing details were taken care of by the finance team. I do not have the exact numbers, but I think it was competitive with other solutions.

Instabug is a great crash reporting tool, and I would recommend trying it. I rate this product a 9.

My major use case for Instabug  involves sharing beta customer feedback and obtaining crash reports, tracking user sessions, and monitoring app performance. These are the major features that I consume and use in my app.

With the help of Instabug , we can easily obtain actual beta customer feedback. Customers simply need to shake the phone, and they will receive a pop-up where they can share their feedback. If they experience anything wrong or want to express appreciation or disappointment, they can raise it with us.

Instabug is definitely on track. Whatever features we are using are totally stable, and we can use them in production as well.

For the performance monitoring of a mobile application, Instabug provides a core feature that is the very best feature offered. We can track our app's health, and if my app is performing well, it is excellent to have.

Sometimes the crash reports come with a delay. When the app crashes, we receive the report after 10 or 20 minutes. This could be improved.

The sharing of feedback and crash reporting is not always real-time with Instabug. While it is otherwise good, this is an area for improvement.

I have used Instabug for the last five to six years. I used it around four years ago for two years, and recently for the last two years, I have been using Instabug again.

We have not faced any lagging or crashing of the application with Instabug.

Instabug is definitely on track regarding scalability. Whatever features we are using are totally stable, and we can use them in production as well.

I have not had a chance to connect with their technical team for Instabug because it is working as expected.

Before Instabug, we relied on Crashlytics. We were using Crashlytics, but Instabug provides additional features such as network tracking and app performance. Additionally, we can take user feedback simply by shaking the phone, which is a feature we use as well.

The initial deployment of Instabug is too easy. We simply need to plug in and use a dependency from Instabug's GitHub  repository.

It took us one month to fully deploy Instabug in our company. We implemented it on the same day, but we shared the build with our beta customers after one month so that they could share their feedback.

One person is enough to deploy Instabug.

For every software, including Instabug, there is a need for version upgrades, and for that purpose, we definitely need to track the latest version of Instabug.

I read that Instabug provides integration with third parties such as Jira  and gives the opportunity to deploy into CI/CD as well, but in my use case, this is not applicable for now.

I rate Instabug 10 out of 10. I use the core features of Instabug, so I am totally happy with them. I will definitely give it 10 out of 10.

I am not analyzing user behavior with the analytical reports from Instabug. I use those reports for analyzing crashes. If my application crashes, I use the journey that users tracked and the path they took to replicate that crash and fix the issue. My overall review rating for Instabug is 10 out of 10.