Instabug Reviews

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.

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.

Our main use case for Instabug is to gather the capture and the user's data and also to identify any crashes or bugs that are available because we are migrating from our old native legacy applications to a new framework application. We are transitioning from the old codebase to the new codebase, and there are many ways that we introduce more bugs or experience some crashes, so we want to gain insight into those bugs and reduce them as much as possible.

Instabug helps me track those bugs during the migration in many ways. Whenever a crash is happening on the user side or on the server side, it alerts us, and it also has features that allow us to sort the bugs, and users can report them as well. Additionally, we have a feature for surveys where we can determine if the user is feeling satisfied about the applications or which parts the user is using more often, so that's how we try to use Instabug, and it helps us in many ways to get feedback. It also has the AI feature which helps us solve and exactly pinpoint the bugs.

Instabug fits into our workflow in many ways, including helping us to get user survey responses as well, along with different ways to identify network errors and also our API speed, which is how the API is performing on the client side. This is another use case for which we are using Instabug.

In my opinion, the best features Instabug offers include the dashboard and the KPIs provided, along with the crash-free rates and the detail of each crash report, which I consider one of the main features of Instabug.

The dashboard and crash report details help our team day-to-day in many ways. Whenever we are updating any new versions of the applications, we use the dashboard and the KPIs to perform and compare them with the last version available on the stores, and that's how we compare it with the old versions. If we encounter any confusion or irregularities, we try to revert that and fix it as well, so it helps us track the metrics of our application.

Instabug has positively impacted my organization by allowing us to have fewer crashes and less bugs, and it enables us to connect with real-time users and get feedback, which leads us to new product goals and prioritization of features coming in the future.

Instabug can be improved in a way that while delivering the crash reports and bugs, if they can provide a way for us to share our codebase with them, we could get more detailed information about where exactly a particular crash is located or on which screen the crash is happening for most users. That would be helpful for quick resolution of bugs and crashes.

I wish Instabug could provide some additional AI assistance. There is already an AI assistant available for bugs, but it could be improved by delivering more specific results rather than general, generic responses.

I have been using Instabug for the last three years. The client provided us the SDK and we have integrated it into our project.

Regarding Instabug's AI capabilities, its governance and security are good. Whenever we try to use their support engineers, they are always available and make sure to take consent before visiting our dashboard. Security-wise, it is also good because they ask for a password or a frequent change of the password.

My advice for others looking into using Instabug is to give it a try because most features are really informative and detailed, which could help improve their product. However, they need to look into the budget because the cost is quite high, so if it proves worth it, then definitely go for it. Overall, Instabug is a good product, and I would say everyone should definitely give it a try. I would rate this review an eight out of ten.

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.

My main use case for Instabug is to conduct a survey. I use Instabug for a survey and to receive feedback about our app, as we have a new app. My team uses Instabug because we have an app in which people can subscribe to find a job.

The best features Instabug offers are that it is very easy to obtain immediate feedback. The immediate feedback feature for my app is very simple to use, which helps my team and users focus on the target and focus on a different objective.

Instabug has impacted my organization positively because it is very simple to use, and I can find in a short time the feedback I need to work on a specific target.

Maybe it can be more simple to separate customers by age.

I have been using Instabug for some months.

Instabug is stable and reliable for me.

In my experience, Instabug's scalability is good because I think it increased the users.

I have never interacted with Instabug's customer support.

I did not previously use a different solution before Instabug.

I have not seen a return on investment because I am a simple employee.

I don't have experience with pricing, setup cost, and licensing.

Before choosing Instabug, I did not evaluate other options.

Instabug has helped me get a faster response, but I don't have any experience with different sites, so I cannot make a comparison. My advice to others looking into using Instabug is to use it simply because it works very well. I would rate Instabug an eight out of ten because the app works very good and I think it deserves a good rate.

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 used the solution to perform RCA for my app. I used to review the crash reports every week and check which API or call was failing repeatedly. I created a debugging configuration in Jira and reported it to the developer to fix it. I also monitored the apps to see if an API takes too long to respond.

The product makes it very easy to reproduce issues. Everything was logged, and I could see the network logs very clearly. I knew what the user was trying to do. I could replicate the user journey, making it much easier to create the issues and file the RCA report to my manager.

The end users were not able to report bugs. We had to depend only upon the crash reports. For example, if an application was not crashing, but a specific functionality was not working, the QA personnel and developer could report the bugs. However, the end-user could not do that in the production application.

I used the solution a year ago.

The tool is very stable. I rate the stability a nine out of ten. We did not have any issues.

I rate the tool’s scalability a seven out of ten. The insights were not very clear. We did not know why some glitches were happening or why our throughput was low. We were not able to predict the future. I used the solution in my previous organization, and it was deployed in two to three projects.

Currently, we are using Bugsnag. The insights in Bugsnag are pretty great. We are able to find where the issue is happening and why we are dropping down on our conversions.

The initial setup was really easy. There were some calls that we had to integrate into our code. Instabug was easy to integrate with our app. If we needed special logs for some calls to check the response rate of some end-to-end procedures, we could also integrate them. There were some APIs we could use for end-to-end integration.

The product was deployed on Bitbucket. The beta app was deployed in our local environment. The deployment process was not time-consuming. The production phase took a day. It was just a one-time effort. For the beta app, we had to do it multiple times, but it was easy to deploy.

Instabug is a good tool. Filing RCA reports without products like Instabug and Bugsnag is hard. It reduces a QA personnel’s job. Overall, I rate the product an eight out of ten.

I was in the Q&A team, so we ensured quality assurance. As a QA, I find it useful for debugging purposes. Whenever there are crashes or problems, we use Instabug to send reports with screenshots and error details to the development team. It helps us debug problems on the mobile application side and also with API responses.

Once, there was a crash in our mobile application that kept occurring. The developers couldn't debug it through the code, despite their efforts to investigate. They needed to create a Instabug report and examine the logs. After I generated the bug report for the crash issue, they analyzed the reports and logs, ultimately identifying the solution. This process also resolved many problems with our iPad and mobile applications. 

Moreover, our customers have also benefited from this as they received training when encountering production issues, primarily through debugging in the Instabug portal.

The most valuable feature is the ability to capture detailed error data, including screenshots and steps, which helps us pinpoint issues effectively.

It would be beneficial if the tool could be more precise in capturing steps, focusing only on the relevant ones. For example, there were some times when it caught some extra screenshots which were not included in the steps. Sometimes, it also happened that it got some extra steps that were not in there to reproduce the bug. We also called that screenshot and the steps there as well.

I would like too see a video recording feature added to Instebag so that users can report problems by showing developers exactly what is happening. For example, we can record any video and upload it on Instabug, so we can also add the steps there. Like we record the pain from the mobile app, there should be an option to report the video, and that should serve the purpose for the end user to record their screen to show how the error is occurring on their end. After they upload their video, we can use this for debugging purposes. Because most of the problems are from the end user customer side, it would be easier if we use the video recording feature in Instabug or just take the device, and it should also show the video recording option.

I have worked on my previous company for mobile application testing, and I was using a server for diverging the errors and finding solutions for them.

I joined almost six to seven months ago. Whenever we faced any problems, Instabug was integrated with our app, so we reported the problem to Instabug. That's how we used it. 

However, I am not currently using it because I left my previous company in March 2023.

I would rate the stability a nine out of ten. 

I would rate the scalability an eight out of ten.

It was easy for us because our company had already set it up, and we were provided with accounts. 

Overall, I would rate the solution a nine out of ten.