Instabug - Ultimate

My main use case for Instabug  is as an APM  tool.

I use Instabug  for several purposes. One is for release management. Whenever we release, we check Instabug for crash rate and any increases or decreases. The Apdex score is really required for us; it is basically a metric for us. Another thing we use Instabug for is to look at crashes that are coming and to create tickets from there, and to create alerts based on different screens and different teams. These are the three major use cases.

Instabug has positively impacted our organization by being a good tool to analyze. Most of the things we were doing before were done using New Relic . New Relic  does provide a lot of things, but Instabug gives you curated dashboards, good customer service, and essentially whatever we require for an app release management process, we get from Instabug most of the time. It also provides good features such as allowing you to create Jira  tickets directly from the Instabug dashboard, which is valuable.

Instabug offers an MCP, a really good dashboard for looking into your app's performance, and another dashboard for release management where you can check what is happening with your current release. Another thing Instabug provides is alerting, which allows us to create PagerDuty and Slack messages so that whenever a metric drops or SLA breaches, we get the alerts at the right places.

There are a few improvements that Instabug could benefit from, such as having a specific set of APIs. They provide very little data out of their system. Essentially, the data that Instabug provides could be improved; if there are APIs to tap into and receive the data we see on the dashboards, those APIs would really help streamline workflows and pipelines so that we don't have to look into Instabug for release management.

API access is a key area where I believe more metrics should be available. We currently only get crash-free rates and a few other metrics, but if we could get more details for a release, such as frustration-free sessions, that would greatly assist in understanding release performance. This would allow our pipelines to make informed decisions and reduce human intervention.

I chose the number nine because Instabug does most of the things an APM  tool should do. With the new agent assistance, it also provides MCPs. One area where it lags is accessibility through APIs. Even though we are partners or clients, we should be able to access data shown on the dashboard via an authenticated API if we have an API token.

I have been using Instabug for two and a half years.

Instabug is stable.

Customer support is really good; they reply within hours through Slack and email. They are very quick in that sense and have weekly progress meetings set up with us, which makes for a really good customer support experience.

Before Instabug, we were using New Relic, and we compared it with Crashlytics and some other tools that are available in the market, and I think Instabug performed really well.

I have seen a return on investment in terms of time saved. Regarding setup cost, I believe it took one engineer to get Instabug up and running, and there was definitely initial cost required. It took around a month to set things up on the Instabug front, but that is not solely because of Instabug; it is also due to our review pipelines, including security and legal reviews.

Instabug does save time because it offers user stories about how users used the app, which allows you to check and address bugs. A bug that might take a developer two to three hours to recreate can be solved much faster with Instabug, as it provides recreation steps.

We evaluated Crashlytics and New Relic before choosing Instabug.

I would advise others looking into using Instabug to evaluate how they want to use it. It is a really good tool, especially if you are looking for something that can help with APM. You should also consider the pricing, which might be higher or lower depending on your use case, but Crashlytics is free for bug hunting, so check your use cases. I gave this product a rating of eight out of ten.

My main use case for Instabug  is for an Android production application. I initially adopted it for crash and bug reporting, but I found it more useful during production troubleshooting. It provided valuable context such as logs, device information, screenshots, and user feedback, which helped me investigate issues faster. I appreciated how it consolidates bug reporting and analysis into a single workflow instead of relying on multiple tools. The integration was straightforward and it works well in real production environments. My overall experience was positive, as it helps improve visibility into production issues and reduces the time required to identify and resolve them.

Recently in my production application, I faced a complex situation where I had to track individual events in a high concurrency area with more than 10,000 users who onboarded to that event. This was a challenge for me to track each user individually from their entrance until their exit and gather information about them. In that case, I used Instabug  to examine their logs individually within the panel. This helped me track user experience and user flow in production when under production pressure.

I can share my recent project on the Beacon  testing application where I tracked individuals in a high concurrency area. Instabug definitely helped prevent distortion of the radius between individual users who onboarded into that event. The metrics I achieved from that product deployed into NSE and NSC show that the users who attended that event were more than 10,000 in that section, working in the production area with Instabug continuously tracking that section in the panel. I tracked everything from Instabug.

I shared my metrics about how Instabug worked in production.

The best feature I personally use in Instabug is the logs and crash listing details for individual sections and the analytics that I use during testing, internal development, and production development under pressure. These are the individual tool cases I personally use in Instabug for different types of development and production.

I personally consider the logs and Crashlytics features provided by Instabug as the most helpful when working with development parts internally and externally when I'm attached with teams that work globally and remotely. The remotely available logs and Crashlytics work well when sharing data for particular development before things are put into production.

The main things I track with Instabug are the internal and external logs in bound operation. It would be great if Instabug works with AI tools and modules. That would be a great addition from Instabug.

I already mentioned that it would be great if Instabug works with AI tools for the environment structure and to work with frameworks and other things natively. That would be a great thing to integrate.

I don't see other improvements that would justify changes for Instabug. If it does not get attached with upcoming tools and other things that parallelly work with developers, that would be a discontinuation of these features by Instabug or by the developers.

It would be great if Instabug introduced AI integrated tool features to individually track for native frameworks where multiple developers and domains are working on that particular section. It would be great if there were a single panel where multiple domains could collaborate together to focus on a single production pressure.

Regarding Instabug's AI capabilities, I think everything cannot be pushed into the AI section because when things are in production pressure, somebody needs to take ownership for that. Definitely AI will help, but it should be used according to the structure of things, not completely blindly following rules. Governance  and privacy also matter when working with fully automated tools.

I have used Instabug for more than 1.5 years.

From the point of view of testing and maintaining things, Instabug works well to prevent problems when working with system issues, handling millions of users, managing state management, working with lifecycle flaws, or addressing internal structure of development and production applications. This definitely helps me track internally and externally before putting things into production.

The scalability of Instabug is very good based on my recent tracks of the application and domain. It performed well in scalability because when things are scaled or when production scales, the inbound operation also gets scaled into Instabug. It excels in scalability.

I did not connect with customer support personally. I used the service and got connected with support via email.

I did use different solutions before Instabug. I previously used Firebase Crashlytics and Liber CS. They provide similar kinds of things that Instabug offers, but one thing I want to emphasize is that Instabug provides the full panel control with detailed logs and input when things are in production pressure. That was one of the good things I got from Instabug.

Regarding my experience with pricing, setup cost, and licensing, at that time it was efficient, but I don't know about the current cost and licensing pricing of Instabug.

My company was a partner with Instabug.

I already shared my experience when working on the Beacon  testing application. In that condition, I saved a lot of time for the QA testers and my internal testing teams who were working manually. After using Instabug, they automated their decisions and internal thinking to work and coordinate with Instabug to get things more accurate and make decisions before putting things into production pressure.

Regarding my experience with pricing, setup cost, and licensing, at that time it was efficient, but I don't know about the current cost and licensing pricing of Instabug.

When evaluating other options before choosing Instabug, I considered Firebase Crashlytics and Liber CS for free or these types of small things as great options. For production and other needs, Instabug or its alternatives can perform well based on my experience.

My personal experience and advice would be that if you want detailed logs and crash lists when working under production pressure, then definitely you can choose Instabug because it provides complete detailed system logs and the internal development inbound or outbound formations when teams collaborate before putting things into production.

You can add questions related to AI framework integration, which I mentioned Instabug should have for future improvements because other domains are already working on that.

I would rate this product an 8 out of 10.

I use Instabug  for mobile app quality monitoring, crash reporting, and bug reporting as my main use case.

Instabug  supports quality monitoring, and when I publish an application over the Play Store, crash reporting and bug reporting become quite easy for live bugs and on beta builds. This helps my developers maintain the code and quality.

The best feature I rely on is in-app bug reporting and screenshot annotations, which is the main thing my team loves most.

Instabug helps my team in bug reporting by identifying where crashes are happening, what kind of crash it is, and how we can resolve it, all along with a screenshot at the time of the crash. These are the features my team loves most.

Instabug helps us maintain crash-free users and quickly improve our crash percentage because we fix bugs quickly and can maintain a higher crash-free user percentage of 99 percent plus.

In Firebase, it is showing 99 plus, which means the crash percentage is quite low. This means if there are a thousand users, only two, three, five, or ten users are getting the crash out of 1000, so it is around 99 percent. That is how we measure that.

As of now, I have not checked for areas of improvements, but Instabug could provide advanced dashboard customization options so that users can maintain their use case type of dashboard.

Customization dashboard and better filtering and segmentation capabilities are the areas that Instabug can improve upon.

I have been using Instabug for approximately two and a half years.

Instabug is a quite good, feature-rich mobile observability platform that you can really use. If someone is looking for an observability platform and they are stuck somewhere in resolving bugs with lots of live crashes in their apps, Instabug will help them better in respect to other apps. I give this product a rating of 9 out of 10.

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.