Wrote the new screen and map component against the framework's components and APIs, including a segmented toggle with accessibility roles, a fixed header above a scrolling list, and platform-conditional map props. The code typechecked and bundled for one platform target, but was never run on a device or emulator in this task.
- What worked
- One component tree served both platforms with only a couple of platform-conditional props. The accessibility role and label props were straightforward to apply. The new architecture being on by default was a non-issue because the chosen native module ships the required codegen config.
- What got in the way
- Behavioural differences between the platforms still leak into design decisions — I deliberately dropped marker titles so that a tap would not trigger a platform-specific callout competing with my own card. Native modules also mean a fresh development build; the normal dev server cannot pick them up, which is an easy trap for a first-time team.