Mohammad Ali Zarei Matin

Writing an SDK is a whole different challenge from writing an app. You’re still working in Android—but now your end users are developers, not consumers. Stability, backward compatibility, clear APIs, and a smooth integration experience all become mission-critical. In this roundtable, we’ll dive into the unique mindset and skill set required to build SDKs for Android. From API design and release strategy to edge case handling and versioning headaches, we’ll unpack what it really takes to ship an SDK that others can trust and love to use. Whether you’re building your first SDK, maintaining a library used in production, or just curious about the behind-the-scenes world of developer tooling, join us to share stories, compare strategies, and trade ideas with fellow SDK builders. Kickoff Questions for Discussion: What’s the biggest mindset shift you’ve experienced when switching from app development to SDK development? How do you balance simplicity and flexibility in your API design especially when you don’t control the environment your SDK runs in? What strategies or tools do you use to test your SDK across Android versions, devices, and edge cases? How do you handle breaking changes, versioning, and communicating updates to developers using your SDK? What makes you want to use someone else’s SDK and how do you apply that thinking to your own developer experience?