android-templates
android-templates copied to clipboard
nimblehq
Our optimized Android templates used in our projects
## Why Most of the apps use API requests and have a `refresh token` mechanism to request new access tokens in case they expire. We don't have the setup for...
## Why [Ktlint](https://pinterest.github.io/ktlint/) will improve our Kotlin code quality with lint checks Once approved we can drop this issue: #182 ## Acceptance Criteria - Add ktlint configurations - Remove lint...
## Why Automate the process for new pull request creating to bump new version after each release: - Checkout. - Bump the new version. - Commit, push & create a...
## Why We're still using the legacy Detekt config for Jetpack Compose project, that's why Detekt reports a lot of issues related to new [Jetpack Compose conventions](https://nimblehq.co/compass/development/android/user-interface/jetpack-compose/#conventions). Hence we have...
## Why Managing resources and themes in Jetpack Compose differs from how we have done with XML. In this task, we will set up app resources and themes management for...
## Why Our current Android template for Jetpack Compose is too inceptive to start a new project. To make our Compose template truly designed for Jetpack Compose and follow the...
## Why The deploy to Firebase workflow uses [Firebase-Distribution-Github-Action](https://github.com/wzieba/Firebase-Distribution-Github-Action) (which is using the `Firebase Token`) to deploy the build to Firebase Distribution Console. https://github.com/nimblehq/android-templates/blob/53d318c598d0b41e4238076765aba7c4c7fee045/.cicdtemplate/.github/workflows/deploy_staging_and_production_to_firebase_app_distribution.yml#L73-L79 Firebase CLI Tools announced the depreciation...
## Why Testing, including UI and Integration tests with Jetpack Compose, also requires a different set of boilerplate to begin with. And currently, there is no UI & Integration test...
## Why We should consider adding unit tests for the XML sample code to increase the code coverage ## Who Benefits? The user of this template
## Issue Currently, we're having a sample to define [BASE_API_URL](https://github.com/nimblehq/android-templates/blob/develop/CoroutineTemplate/app/build.gradle.kts#L41) via `BuildConfig`. **BuildConfig will not be obfuscated by proguard** so this way is not safe to go, especially when we...