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.

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.