If you who joined our Building Mobile Apps At Scale webinar last week, you know how fascinating it was to hear Gergely Orosz’s journey at Uber, and how their mobile team responded to the engineering and scaling challenges. If you didn't have the chance to join, you can still watch the full recording here. This is the second part of a series of blog posts summarizing the Q&A part of the webinar, where Gergely was joined by GDE Pooja Bhaumik, Coding Mentor at MentorCruise and Startup Clinic initiative by Google For Startups; and Franz Busch, Staff Software Engineer at Sixt who responded to a wide range of questions. Today we’ll be answering questions surrounding platform teams and culture. Gergely suggests that having a killer argument for stakeholders is crucial, focusing on the benefits of a platform team such as increased productivity and scalability. Franz emphasizes that it's vital to write down topics covered by the platform team and prioritize them, making a 95% net positive time calculation for the company. Pooja Bhaumik notes that sharing tasks with feature teams can be beneficial if done correctly, but also highlights the importance of mentorship and pair-coding sessions for new developers. Gergely stresses the need to keep teams small and boundaries clear, while Franz recommends engineering foundational blocks of applications well, such as networking and persistence design systems. The discussion also touches on structuring teams, with Gergely advocating for cross-functional teams and Franz suggesting that ownership and governance are key factors in avoiding over-engineering. Overall, the conversation highlights the importance of platform teams in enabling mobile teams to move faster and more efficiently.