Actionable insights to resolve Android performance bottlenecks and errors. Improve your monitoring workflow with a full view of releases so you can mark Android errors as resolved and prioritize live issues.

A month of mobile product updates, help sessions, and tips to improve your app experience.
March 18, 2021 @ 10:00 AM PST
Join us for a conversation on performance monitoring, when to use attachments, and a sneak peek on reprocessing incomplete events.
Register nowGive 3 months Sentry and get 3 months free. It might be awkward, but their users will thank you.
Refer a FriendRead about how CTO and Co-Founder of Popsa, Tom Cohen, uses Sentry to solve what matters most to their customers.
Read moreWatch a quick tour from Sentry Solutions Engineers on how to get in front of bad releases.
Watch nowBreak out your brackets — it’s time for our inaugural Mobile Technology Tournament. Download your bracket and tweet it to @getsentry before March 16th for a chance at Sentry swag
DownloadDownload this handy one-pager to share with your team or refer back to it for when you don’t have internet.
DownloadAdd the Sentry Android SDK to your build.gradle file:
// Make sure mavenCentral is there.
repositories {
mavenCentral()
}
// Enable Java 1.8 source compatibility if you haven't yet.
android {
compileOptions {
sourceCompatibility = JavaVersion.VERSION_1_8
targetCompatibility = JavaVersion.VERSION_1_8
}
}
// Add Sentry's SDK as a dependency.
dependencies {
implementation 'io.sentry:sentry-android:<version number>'
}Configure your SDK AndroidManifest.xml:
<application>
<meta-data android:name="io.sentry.dsn" android:value="https://<key>@sentry.io/<project>" />
</application>That’s it. There’s no step three. Don’t believe us? Check out our Documentation.
See all platforms
Quickly identify performance issues and view full end-to-end distributed trace to see the exact poor-performing API call and surface any related Android errors. Improve Android performance with max efficiency, not max effort.

See Android app crash reports with details like filename and line number so you never have to guess or dig through an Android error log. Filter and group Android exceptions intuitively to eliminate noise. Monitor errors at scale without impacting throughput in production.

See an event trail to know what the app was doing before any error occurred. Record Android stack traces even when devices are offline or in airplane mode, then send errors as soon as connection is regained.

Improve workflow with a full view of releases so you can mark errors as resolved and prioritize live issues. Learn in which version a bug first appeared, merge duplicates, and know if things regress in a future release. Add commit data to automatically suggest an owner of each application error and instantly send deploy emails.
“Sentry in particular is really valuable at tracing exceptions of errors and providing automatic feedback so we can see things clearly and gain a better understanding of what’s going wrong.”
Sentry makes Android app development easier by recording environment and state details.
Recreate bugs down to screen orientation and resolution, Androidversion, and battery level.
Tag distribution graph makes it easy to isolate and prioritize anyAndroid error by seeing how often it occurs in context.
Sentry supports every major language, framework, and library. You can browse each of them here.
You can get started for free. Pricing depends on the number of monthly events, transactions, and attachments that you send Sentry. For more details, visit our pricing page.
Sentry doesn’t impact a web site’s performance.
If you look at the configuration options for when you initialize Sentry in your code, you’ll see there’s nothing regarding minimizing its impact on your app’s performance. This is because our team of SDK engineers already developed Sentry with this in mind.
Sentry is a listener/handler for errors that asynchronously sends out the error/event to Sentry.io. This is non-blocking. The error/event only goes out if this is an error.
Global handlers have almost no impact as well, as they are native APIs provided by the browsers.