For years, "inclusivity" in mobile development has been treated as a synonym for standard accessibility compliance or simply adding a third option to a gender dropdown. But true inclusion runs much deeper—it’s baked into our database schemas, our form validations, and our UX assumptions. Back for their third year at FlutterCon USA, the Flutteristas are diving into the hidden nuances of identity and inclusion in tech. From the pitfalls of rigid form design to the unintentional exclusion in niche markets like parenting and tracking apps, this panel will explore how "inclusivity in the app" doesn’t always match real-world lived experiences. Join us for a practical, honest conversation on how to evaluate your apps from fresh perspectives, re-architect your data structures, and build software that genuinely represents the diverse world we live in.

AI doesn’t magically make teams faster—it changes how they work. At Ardley, we learned that once you move past dabbling with tools and start relying on them day to day, you run into new problems: unclear code quality, tricky security questions, and tools that don’t always behave predictably. In the AI-Integrated team, the role of the developer starts to shift. Less time is spent writing every line by hand, and more time goes into shaping systems—defining architecture, writing clear specs, and reviewing AI-generated code with a critical eye. This talk is a practical look at what actually breaks (and what holds up) when you build AI into a real development workflow. We’ll cover how to keep standards high in environments where mistakes are costly, and how teams can scale their output without losing the human judgment that good systems depend on. Key takeaways: - How to move from individual AI usage to shared team practices - Setting clear guardrails for security and data use - How the developer role is shifting toward architecture, specs, and oversight - What code review looks like when AI is writing part of the code