Measure how long your user flows take to run and review trending over time. Catch performance regressions as soon as they are introduced.
It is critical to know that your app crashes under certain conditions before it is released. NimbleDroid provides automated crash detection for all of its profiled Scenarios, and any crash will be reported along with the accompanying stack trace to help you determine the root cause.
For every user flow that NimbleDroid profiles, it searches for memory leaks. In addition to reporting the presence of a leak, the root cause is reported via the reference chain for the leak. When used in Continuous Integration or as part of a release checklist, it can ensure dangerous leak never make it to production.
Once you integrate NimbleDroid with your Continuous Integration you can configure email and Slack alerts to inform you about slowdowns, memory leaks, or app crashes. Stop manually checking your results and automate your way to peace of mind!
Once you upload your APK, NimbleDroid will crawl the interface and identify user flows that your users can click through. Each of these flows will be added to the list of Scenarios that NimbleDroid will profile and analyze.
In addition to our auto-discovered user flows, you can create custom user flows with as many steps as needed to profile actions that are critical to your business. Custom flows are created using standard Espresso syntax, and you can use simple log statements to annotate the exact start and stop of measurements. No SDK required.
In addition to spotting and measuring slowdowns, you can pinpoint the exact cause by examining the call stack of slow methods to determine the root cause.
Keeping method count down is often a prime concern for developers, whether it’s their own code or an SDK they are integrating. NimbleDroid lets you find out what’s adding to your method count.
See how your app is using system resources for each Scenario that we profile.