top of page
Marco Gomiero

Marco Gomiero

Senior Android Engineer @ Airalo - Android GDE

Marco is a Senior Android Engineer at Airalo and a Google Developer Expert for Android. He’s passionate about building great mobile experiences on both Android and iOS, and loves working with Kotlin Multiplatform to share code where it makes sense. He also maintains open-source projects, shares what he learns on his blog, speaks at conferences, and helps organize GDG Venezia. When he’s not coding, he’s probably playing basketball.

Working with AI, Not for AI: Practical Strategies for Android Development

AI is reshaping how we write code—but for Android developers, the real question is: how do we make it genuinely useful, without slowing down, over-automating, or rewriting our process for the hype? In this roundtable, Android engineers and tech leads will share how they’re integrating AI tools like Gemini, Cursor, Copilot, and others into their Kotlin development workflows—from code generation to test scaffolding, refactoring, documentation, and more. We'll dig into what’s actually helpful in practice, how to avoid tool overload, and how to think critically about where AI fits into the developer experience. Whether you’re experimenting with AI tooling or trying to get buy-in from your team, this is your space to compare notes, ask questions, and learn what’s working (and what’s not) in real-world Android development. Which AI tools (e.g., Copilot, Gemini, Cursor) have you tried in your Android development workflow, and what stuck? What kinds of tasks—test generation, boilerplate reduction, code reviews—have you successfully offloaded to AI? How do you balance AI-generated code with code quality and maintainability in a Kotlin-heavy project? What risks or annoyances have you run into when trying to integrate AI into your daily work? Are your teams using AI collaboratively (e.g. shared prompts, memory banks, pair programming with AI), or is it still an individual tool?

From Kotlin to Native and back: accessing native macOS API in Compose Multiplatform

Compose Multiplatform makes it easy to build cross-platform desktop apps with Kotlin and Compose, but what about native APIs, like iCloud on macOS? Accessing such APIs isn't possible through the regular Compose Multiplatform toolchain. However, with a bit of “magic,” we can turn dreams (or feature requests) into reality. In this talk, we'll explore how to combine Kotlin/Native and the JNI (Java Native Interface) to bridge the gap between a JVM-based UI and native system features. We'll write Kotlin code, compile it into a native library, and call it back from Kotlin. You'll learn how to build Kotlin/Native code into a native macOS dynamic library and integrate it into a Compose Multiplatform desktop app, unlocking access to iCloud and enabling features like backup and restore for your app’s data.
bottom of page