As a seasoned UX/UI designer, I share the insights and lessons gained from stepping into the role of an Android engineer on an actual project. I found striking similarities between the design philosophies of JetpackCompose and Figma, discovered Kotlin’s high readability and expressiveness approachable even for designers, and realized that possessing perspectives on both “design” and “implementation” made specification adjustments and communication far smoother. From a designer’s unique standpoint, I unravel the development process. I hope these perspectives will be helpful for designers considering Android development and for engineers facing collaboration challenges with designers. 1. Why I decided to take on Android development 2. JetpackCompose and Figma: Shared approaches to UI design 3. Writing Kotlin and feeling its “designer-friendly” ease of use 4. The smooth specification adjustments revealed through UI implementation 5. Insights gained in team development and changes in communication 6. A message for those eager to take on the challenge next (Translated by the DroidKaigi Committee)
Kanon Fujita Yumemi Inc. / Design Engineer
- Designers interested in Android development - Android engineers struggling to collaborate with designers - All developers curious about “making things” beyond job boundaries
Breaking Up with WebViews: Server-Driven UI with KMP + Compose
AmniX
#Cross-platform Development
Careers as an Android Engineer
mhidaka
#Soft skills
Beyond Exceptions: Building Resilient Android Apps with Safety-Critical Principles
Bogusz Pawłowski
#App Architecture