Vadym Pinchuk

Building applications for TVs, kiosks, and other remote-controlled devices isn’t the same as building for mobile. There’s no touch. No gestures. Just a handful of buttons—left, right, up and down. That constraint changes everything. In this talk, you’ll learn how to design and build Flutter interfaces for these input-limited environments using the power of focus navigation. We’ll dive into Flutter’s focus system, directional navigation logic, and how to create clean, intuitive UIs that users can control from across the room. And the best part? The presentation is the app. Shaped like a TV-style Flutter interface, the talk itself will demonstrate how to structure widgets, style your UI, and guide the user using focus alone. If you’re used to building for touchscreens, this session will help you shift your thinking—and show you how to create smooth, accessible, and fun experiences on remote-controlled devices. Key takeaways: - Understand how to navigate UIs using only directional inputs - Learn how Flutter’s focus system (FocusNode, FocusTraversalPolicy, etc.) enables non-touch interactions - Discover UI design patterns for limited-input environments like TVs - See how to structure widget tree for predictable, intuitive focus behaviour - Gain practical techniques to build polished, accessible apps for remote-controlled devices

AI tools like ChatGPT can solve coding problems instantly—and remote interviews make it hard to know who’s really behind the keyboard. So what should Flutter teams do when traditional technical interviews stop reflecting real-world skill? In this roundtable, we’ll dive into how hiring for Flutter roles is changing and what fair, effective assessments might look like today. Let’s explore how teams can balance trust, rigor, and realism in the age of AI-assisted development and remote candidates. Bring your experience, challenges, and ideas—this is a space to share what’s working (and what’s not) in your hiring process. How has the rise of AI tools changed your expectations for technical interviews—especially for Flutter or mobile roles? What signals do you now look for to gauge a candidate’s real-world ability, beyond algorithm puzzles or live coding? How do you address concerns about authenticity and cheating in remote interviews without creating a hostile experience? Should we be testing how candidates use AI, rather than pretending it doesn’t exist? If so, how? What alternative interview formats (e.g. take-home projects, pair programming, system design) have worked well for your team?