External dependencies

[rakibhasanbd4723]

It is worth to look at external dependencies along with the versions they are using. They will tell you what technological stack was used and familiarize you with concepts used in the code you will work on. Other words, they will help you to understand why the code is written the way it is.

If you are quite new in Android bulgaria phone number development some of the external dependencies can surprise you or can be new for you if you had no opportunity to work with them before. For example, you can encounter RxJava 1 which reached his end-of-life (EOL) by March this year, Event Bus (very popular some time ago), or even MaterialEditText library not maintained since 2016. Or GCM (Google Cloud Messaging) recognized by Google as deprecated. In some cases, migration to a new technology will be necessary.

API level requirement
The Gradle file is also a good place to make sure we meet the Google Play’s target API level requirement. Google Play requires that apps target at least Android 8.0. So probably you will have to make some changes to the project before the next app release.

Especially you have to make sure if your UI flows provide affordances for granting Runtime permissions. Wherever possible, your app should be prepared to handle rejection of permission requests. For example, if a user declines a request to access the device’s GPS, your app should have another way to proceed.

Support Library
Next potential source of issues can be the Support Library used in the app which can be outdated. So in case, you would like to update it, don’t be surprised if some things won’t work as you expected. Support Library Revisions can be helpful.