top of page
Manuel Vivo

Manuel Vivo

Staff Android Engineer

Manuel is a Staff Android Engineer at Bumble Inc. With previous experience at Capital One and Google, he currently focuses on App Architecture, Dependency Injection and Jetpack Compose.

The Future of Android...And How to Prepare For It

In this keynote, you'll hear from well-known Android experts about their hot-takes, predictions, wishes and advice about how they expect the Android ecosystem to change and how to best prepare for that future. Join us as they answer the question: Where do you see Android Development in three years, and how do you think developers should prepare for that future? After all experts are done making their pitch for the future...its your turn to ask the questions in a rapid-fire Q&A format.

System Design for Mobile: Sharpening Your Architecture Skills Beyond Interviews

System design questions like “Design YouTube” or “Build a chat app” are now common in senior Android interviews—but they’re also highly relevant to real-world technical leadership. Whether you’re preparing for your next role or making high-impact decisions on your current team, mobile system design is a must-have skill. In this roundtable, we’ll explore how Android engineers and leaders approach system design—from interview prep to production-scale architecture. We’ll discuss real-world trade-offs in mobile-first systems, share frameworks for breaking down complex design questions, and compare strategies across experience levels and org sizes. Join fellow developers, tech leads, and managers to swap insights, case studies, and templates you can apply immediately—whether you’re building for performance, scale, or clarity in the next big interview. How do you approach open-ended mobile system design questions—whether in interviews or real-life planning sessions? What patterns or frameworks help you break down large, vague problems into concrete components (e.g., for chat, video, or sync)? What are the most common blind spots or mistakes you’ve seen in mobile system design—especially among less experienced devs? How do you factor in mobile-specific concerns like offline support, battery impact, caching, and flaky networks when designing systems? For leads and managers: how do you evaluate system design skills during hiring, and how do you help team members grow in this area on the job?
bottom of page