5 Major Mistakes Android Developers Make With GitHub
Both new and advanced Android developers can make mistakes. Some of these mistakes are due to ignorance and naivety. Knowing about new trends and paradigms in mobile development is a part of a programmer’s due diligence and helps them become a better Android developer. Embracing best practices will result in creating better, robust and responsive apps. Here are five mistakes Android developers should stop making.
1) Not Knowing About Docker Android
Containers can be used to package the application and all its dependencies. Finding and running the desired version of the emulator can be very difficult. Docker Android provides a solution, we can build Android projects and run unit tests on them with the latest build tools in different emulators. UI tests and monkey tests can be run for Android apps with different frameworks such as appium, espresso and robotium.
Appium is a framework used to test both native and hybrid mobile applications. Appium can be dockerized (Docker-Appium). Multiple devices can be tested at the same time in the isolated containers to fasten the testing process. The advantages of using Docker Android include the ability to connect to Selenium Grid, screen-mirroring, ability to record video during tests for debugging and its easy integration with other cloud solutions such as Genymotion cloud. Additional test utilities such as SMS simulation are also available in Docker Android.
JFrog Artifactory is another tool used in DevOps to store build artifacts that have been created in the code pipeline. In Android CI/CD JFrog Artifactory offers a centralised binary repository for artifacts and project dependencies. JFrog is compatible with Docker Images among other DevOp technologies.