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.
Instabug - Ultimate
InstabugReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
240 reviews
from
and
External reviews are not included in the AWS star rating for the product.
A tool that highlights what is the cause of each bug in the best way possible.
What do you like best about the product?
- Bug reporting
- Rules
- Crash reporting
- Netwrok performance
- Number of Features
- Ease of Use
- Customer Support
- Rules
- Crash reporting
- Netwrok performance
- Number of Features
- Ease of Use
- Customer Support
What do you dislike about the product?
- Lacking an API
- Lacking serious issue management capabilities
- Lacking serious issue management capabilities
What problems is the product solving and how is that benefiting you?
Establising trust between QA team and the dev team cause bugs are easily identified and debuggable and there is no room for people to argue for its validity, thus no fritction.
Categorising tasks per feature or business stream and auto-assigning them for effecrtive triaging and solving
Categorising tasks per feature or business stream and auto-assigning them for effecrtive triaging and solving
excellent way to test your app and get feedback from end user.
What do you like best about the product?
The most important thing in instabug is that i can see all the previous logs like Network request, UI Request
and 2nd thing is we can connect instabug with JIRA so we can easily manage the support stuff without any human resource like we can talk with user and every step i take on the ticket user can also see and track
so my experience is amazing i also recommend instabug to many friends and colleague to inplement in the app
and 2nd thing is we can connect instabug with JIRA so we can easily manage the support stuff without any human resource like we can talk with user and every step i take on the ticket user can also see and track
so my experience is amazing i also recommend instabug to many friends and colleague to inplement in the app
What do you dislike about the product?
i dont see any downside but i found an bug a year ago while my manager assigned me on an project due to users limit it wont allow me to access Insta project but my question atleast i get some appropriate error so i can tell the manager to remove other and add me again.
What problems is the product solving and how is that benefiting you?
it solves me to fix bugs on those device which is not available at time of development
Real-time insights
What do you like best about the product?
That users are able to report real time bugs via our mobile app
What do you dislike about the product?
Not a lot overall is a great product that the whole team loves
What problems is the product solving and how is that benefiting you?
The problem it is solving is that it allows users to report issues they have directly from the app. This allows me and the devs valuable insights
A stable solution that provides visibility into user journeys and enables the filing of RCA reports
What is our primary use case?
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I used the solution a year ago.
What do I think about the stability of the solution?
The tool is very stable. I rate the stability a nine out of ten. We did not have any issues.
What do I think about the scalability of the solution?
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.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What other advice do I have?
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.
Every Mobile Developer Team Should Use Instabug
What do you like best about the product?
- Detailed bug reports including stack traces makes finding and fixing issues so much faster
- Shake to report for end users and internal testers means we learn more about problems AND we're even able to respond to users via Instabug if we need more details
- Very easy to get set up
- The service always works. We've never had an issue with it, ever.
- Shake to report for end users and internal testers means we learn more about problems AND we're even able to respond to users via Instabug if we need more details
- Very easy to get set up
- The service always works. We've never had an issue with it, ever.
What do you dislike about the product?
Overall, it's a great product. It does what you want it to do. Our only hiccup has been on user management (it can be a bit finnicky at times, but definitely no worse than many other dev tools)
What problems is the product solving and how is that benefiting you?
We have users across the world. Apple's crash reporting doesn't give us anywhere near enough detail as to what is going on. Instabug solves this problem for us--we get stack traces, we have the information organized in a clear fashion, we can automatically import these issues into our issue tracker. Our ultimate goal is to have a crash-free and bug free app: Instabug puts us on that path
Captures detailed error data, including screenshots and steps, making it valuable for pinpointing and understanding problems
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
The most valuable feature is the ability to capture detailed error data, including screenshots and steps, which helps us pinpoint issues effectively.
What needs improvement?
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.
For how long have I used the solution?
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.
What do I think about the stability of the solution?
I would rate the stability a nine out of ten.
What do I think about the scalability of the solution?
I would rate the scalability an eight out of ten.
How was the initial setup?
It was easy for us because our company had already set it up, and we were provided with accounts.
What other advice do I have?
Overall, I would rate the solution a nine out of ten.
Very detailed and easy to use too.
What do you like best about the product?
We use Instabug for fatal crashes on our native applications and non-fatal issues/errors we would like to monitor too.
- Easy to monitor issues
- Intuitive User interface
- Easy to monitor issues
- Intuitive User interface
What do you dislike about the product?
It's not easist platform to set up. I'm not saying it's hard but that would be one thing I can complain
- Not easy to set up
- Not easy to set up
What problems is the product solving and how is that benefiting you?
- To identify crashes and non-crash errors and act on them
- Give users option to provide feedback for our application
- Give users option to provide feedback for our application
Useful to keep track of bugs and user feedback
What do you like best about the product?
We can filter and manage all feedback from our users, filter them by country and dates and even tag them. Exporting all of this data helps us make graphics and decisions about our app.
What do you dislike about the product?
We cannot see the complete journey of the user when they submit feedback to us. The screen of the steps, when a user reports a Bug, of the steps they followed before submitting the input is empty.
What problems is the product solving and how is that benefiting you?
It helps us keep track of all our app's bugs every day. It also allows us to collect good and bad feedback from the users to keep improving the app for our users.
Excellent product that covers many aspects of the mobile development flow
What do you like best about the product?
Bug reporting (so much detailed bug information and so well thought, like categories)
Network monotiring
Network monotiring
What do you dislike about the product?
Missing an API to build custom flows
I would like to be able to share filters and send them over using links (if the filter params were part of the URL that would be possible for example for easy sharing)
Too expensive
Too few seats (seats should be cheaper, I cannot think that there is any substncial cost per seat for Instabug)
I would like to be able to share filters and send them over using links (if the filter params were part of the URL that would be possible for example for easy sharing)
Too expensive
Too few seats (seats should be cheaper, I cannot think that there is any substncial cost per seat for Instabug)
What problems is the product solving and how is that benefiting you?
QA reporting effectively bugs back to the team
APM measuring
APM measuring
Best support product ever made
What do you like best about the product?
The contact with customers is smooth
The frontend logs are clear and easily readable
The crash analytics feature is great
The frontend logs are clear and easily readable
The crash analytics feature is great
What do you dislike about the product?
The release dashboard should be more precise by adding the os in the title with the version
What problems is the product solving and how is that benefiting you?
The problems we don't see by default and the problems hard to debug and reproduce on the frontend
showing 11 - 20