Dominik Roszkowski

In this session, we’ll explore practical tips and some good practices for developing Flutter plugins in 2025. How to simplify the process with type-safe APIs via jnigen and ffigen? How to debug your native code easily? What about swiftgen? We'll see how to combine more legacy approaches like method channels with soon-to-be-stable Flutter native interop. We’ll also demonstrate a real-world example by building a PDF viewer plugin and binding of the Google Play library with jnigen.

Building a Flutter app is one thing—keeping it alive, stable, and evolving over multiple years is another. From growing feature sets and refactors to shifting priorities and tech debt, long-lived apps come with a unique set of challenges. In this roundtable, we’ll discuss what it really takes to maintain a healthy Flutter app over time. Bring your war stories, lessons learned, and open questions—whether you’ve just launched or are years into development, this is a space to exchange practical strategies for sustainable mobile development. What’s the biggest long-term maintenance headache you’ve faced in a Flutter app—and how did you deal with it? How do you balance rapid product iteration with long-term code quality and architectural health? Have you found effective ways to refactor incrementally without breaking everything—or do you sometimes just rewrite? What strategies help you manage dependencies and third-party libraries that don’t age well? How do you ensure the user experience (and store rating) remains stable while making major internal changes behind the scenes?