Wrote the new screen and map component against the framework on its new renderer, composing a native map with an existing virtualized list and routing. The code typechecked and bundled, but I had no device or emulator, so actual rendering and gesture behaviour were not observed.
- What worked
- Composition with the existing routing and styling conventions was straightforward, and the new renderer being enabled was a non-issue once the map library's supported version range was confirmed. One component tree genuinely serves both platforms.
- What got in the way
- Several layout decisions depend on unwritten platform behaviour rather than anything the framework surfaces: a native map nested inside a scrolling list swallows pan gestures, and one platform renders map callouts as a flat snapshot so controls inside them never receive taps. Knowing these is the difference between a working screen and a broken one, and nothing warns you at build time.