Be a Business-Driven Android Engineer

With the rise of Kotlin Multiplatform, Android engineers now have an unprecedented chance to become true drivers of business growth. This session will: 1. Share the hard-won lessons and the importance of cross-disciplinary action (“border-crossing”) learned after a mobile engineering team developing a food e-commerce product with annual sales of ¥60 billion took on “revenue” as its KPI two years ago. 2. Present practical border-crossing approaches for Android engineers, centered on the technical choice of Kotlin Multiplatform. 3. Highlight the most impactful border-crossing cases we encountered. Through these stories you will gain both the courage and the concrete examples needed to take business-oriented action as an Android engineer. 1. What we learned by setting “revenue” as our KPI Two years ago our mobile engineers, who build native Android and iOS apps, set “revenue” as their KPI. Many of our early efforts produced no measurable results. We will share those failures, what we learned, and real-world cases of an engineering team carrying a revenue KPI. 2. Let’s cross borders! Contributing to the business means acting beyond your usual domain, which can feel daunting.Using our adoption of Kotlin Multiplatform as an example, we will map out domains that are easier to cross into. Kotlin Multiplatform is the optimal choice for designing cross-disciplinary collaboration for teams currently developing Android apps. By selecting Kotlin Multiplatform, our team created an environment that makes it easy to tackle cross-platform challenges between Android and iOS. Centering on this case study, we will showcase the diverse forms of cross-boundary work we have undertaken. Surrounding Android app development are adjacent fields not only in software engineering—such as iOS, web, and backend—but also in design, data analysis, marketing, and even hiring and training, each demanding its own expertise. By treating these as options for stepping beyond one’s usual domain and aligning them with your career background and interests, you can uncover new ways to contribute to the business in your own unique style. 3. Border-crossing cases that were effective Over the course of our two-year challenge, were we mobile engineers able to contribute to the business? With quantitative, concrete examples, we will explain the most impactful cross-disciplinary cases and delve into actions that mobile engineers can autonomously take to drive business value. - Customer-behavior data analysis - Customer-experience design - iOS app development (Translated by the DroidKaigi Committee)

• 

  ohzono Oisix ra daichi Inc.