Building a solo game is tough, but multiplayer introduces a whole new level of complexity. Every tile placed, word submitted, or opponent reaction needs to feel completely live, even when players are actually hours apart. As the first real-time multiplayer title from NYT Games, Crossplay required us to build a 15x15 interactive board that is fast, fair, and seamless on Android. Getting there forced us to make several technical design decisions we never anticipated. This open discussion digs into the architecture behind Crossplay’s game board. We will talk about why we ended up using a hybrid AndroidView-inside-Compose surface and how we managed its friction points. We will also dive into why Compose gesture APIs broke down across surface boundaries, leading us to replace them with Android's native drag-and-drop framework instead. I will share our practical eight-sector drop intent algorithm for resolving ambiguous touches on small targets, alongside our animation pipeline that uses motion to communicate game state rather than just look pretty. Bring your questions, your own multiplayer challenges, and your experiences with Compose interoperability, as we break down the real-world trade-offs of live state synchronization.