SDKs and Libraries Used by Alarmy Pro
Last Updated & Effective Date: May 26, 2026
Purpose of this page: This page lists the main third-party SDKs, Android libraries, and development libraries used by Alarmy Pro: Loud Alarm. These libraries support core app functionality, reliability, app stability, ads, QR/barcode scanning, local storage, app updates, and user experience.
SDK and Library Summary
| SDK / Library | Purpose in Alarmy Pro | Provider / Reference |
|---|---|---|
| AndroidX Core KTX, AppCompat, Fragment, Lifecycle | App compatibility, Android lifecycle handling, UI behavior, and stable Android framework support. | AndroidX |
| Material Components for Android | Material UI components and consistent Android interface behavior. | Material Components |
| ConstraintLayout | Responsive app layouts for screens, alarm views, settings, and tool screens. | ConstraintLayout |
| Room | Local database storage for alarms, sessions, and app data stored on the user's device. | Room |
| DataStore Preferences | Local storage for user preferences and app settings. | DataStore |
| WorkManager | Reliable background work support for app-related tasks where appropriate. | WorkManager |
| Dagger Hilt | Dependency injection to keep app architecture maintainable and reliable. | Hilt |
| Kotlin Coroutines | Asynchronous operations such as database work, settings updates, and background tasks. | Kotlin Coroutines |
| ZXing Android Embedded | QR/barcode scanning for optional alarm missions. | ZXing Android Embedded |
| Glide | Image loading and display support for image-related app features. | Glide |
| Google Mobile Ads SDK | Ad display and monetization where ads are enabled. | Google Mobile Ads |
| Google Play In-App Updates | Helps users update Alarmy Pro through Google Play. | In-App Updates |
| Firebase Analytics | General app analytics to understand app usage and improve user experience. | Firebase Analytics |
| Firebase Crashlytics | Crash reporting and diagnostics to improve app stability. | Firebase Crashlytics |
| Firebase Firestore | Remote configuration and app service configuration, such as ad control/configuration. | Cloud Firestore |
How We Review SDK Compliance
We use SDKs from trusted providers such as Google/Firebase, AndroidX, and established open-source Android libraries. We review the purpose of each SDK before adding it, keep SDK versions updated, and monitor whether SDK behavior remains appropriate for Alarmy Pro's app functionality and Google Play policy requirements.
Data and Permission Minimization
We aim to use SDKs only where they support a clear app purpose. Alarmy Pro's main alarm, mission, session, and tool data is stored locally where applicable. Sensitive permissions are requested only for features that need them, and optional permissions are controlled by the user. More detail is available on our Permissions Used page and Privacy Policy.
Related Pages
Please also review our Privacy Policy, Terms and Conditions, Disclaimer, and Permissions Used pages.