and operations. As the word suggests, it is a set of practices in a process of developing software and managing operations tasks. DevOps is not just a set of practices, but also a way of working in the software development industry; it’s a cultural change in the way development and operations work together. https://devops.com/metrics-devops/
of a technical glitch. • Contributes to team health, individual satisfaction. • Time efficiency & Management. • Devops gives us the facility & flexibility to invent & focus on actual business needs instead of taking hours/ weeks/ months of operational tasks. • People get to focus on what they are good at and get instant feedback. • To deploy often, you can’t break what’s already there, you have to complement it.
is the tooling required to achieve the process. • There are alot of things to consider about Deployment and Feedback in Mobile App Development: • Testing & Quality checking on a wide range of mobile devices with different hardware configurations and OS versions. • Continuous Feedback and Continuous Development have become the most important thing in Mobile App Development. • Example of Feedback: ◦ What scenarios make the app crash on a user’s phone? ◦ Which screen users spend most time on? ◦ What activities users don’t perform in the app?
that requires developers to integrate code into a shared repository several times a day. • Each checkin is then verified by an automated build, allowing teams to detect problems early.
deployed to customers at any time with the "push of a button" (i.e. by running a deployment script). • Continuous Deployment => Software is automatically deployed to customers once it passes through the continuous integration system.
◦ Frontend ◦ Mobile ◦ DevOps • Getting the team balance at the beginning was a bit of a challenge. • Lots of communication and stakeholder management was needed to make things work. Tools: • Github Enterprise • Code Climate • Circle CI • Static code analysis tools ◦ PMD, Checkstyle, Findbugs, Android Lint • Gradle - Build Scans • Flank - a massively parallel Android and iOS test runner for Firebase Test Lab. • Fastlane
your Android Code • Poor code quality and technical debt inevitably lead to developer productivity losses, missed deadlines, and a higher bug rate. • Complements code reviews through peers. • Static code analysis tools help you enforce coding standards and uncover bad coding practices and potential bugs. • Gradle offers a wide range of standard plugins for you to pick and choose from. • NOTE: We use pre-commit hooks with these tools.
manage the build process, while allowing you to define flexible custom build configurations. • Gradle and the Android plugin run independent of Android Studio. This means that you can build your Android apps from within Android Studio, the command line on your machine, or on machines where Android Studio is not installed (such as continuous integration servers). • NOTE: The output of the build is the same whether you are building a project from the command line, on a remote machine, or using Android Studio.
deployed to customers at any time with the "push of a button" (i.e. by running a deployment script). • Continuous Deployment => Software is automatically deployed to customers once it passes through the continuous integration system.
to automate & optimise your development and release/ deployment process. • Saves time automating tasks so you can spend time on the things you care about most. • Open sourced: ◦ Available on GitHub • Fastlane helps you automate the tedious tasks: ◦ Testing ◦ Building ◦ Signing ◦ Deploying your app
Commit and Push • Build • Generate signed APK • Upload • Add Release Notes • Distribute NOTE: • Fastlane reduces all the above to just the push of a button.
your app: ◦ Defines what steps run & in what order fastlane runs them. ◦ A group of steps is called a lane. ◦ To run it: • $ fastlane beta • NOTE: ◦ If one of these steps fail, the whole lane fails.
Using up-to-date library versions • Build Scans: ◦ A persistent record of what happened in a build. ◦ A great debugging and collaboration tool. • Modularization: ◦ Process of taking a big single module app and splitting it into multiple modules.
you have the basics down: • Latest Gradle version • Latest AGP version • Latest Kotlin version • Don’t disable the Gradle Daemon • Make sure org.gradle.caching =true in your gradle.properties file • If possible, enable org.gradle.parallel too, especially if you have multiple modules.
and splitting it into multiple modules. • Extracting rarely-changed code reduces build time. • Decoupled code => Faster incremental compilation • Intermodule dependencies increase build time. ◦ If you have spaghetti code, where everyone is referencing everyone, incremental compilation can’t help that much.
thedancercodes
yokawasa
matthewlujp
lycorp_recruit_jp
rokuosan
ysakotch
lana2548
oguressive
ishikawa_satoru
drumnistnakano
fujiwara3
rayuron
yabakokobayashi
jacobian
morganepeng
jonyablonski
samlambert
keithpitt
aarron
iamctodd
holman
speakerdeck
samanthasiow
productmarketing
shpigford
