Shipping every feature three times (web, iOS, Android) is a tax most product companies quietly accept. At GetYourGuide, we decided to stop paying it and bet on React-Strict-DOM: one React codebase, rendering truly native on mobile and standard DOM on web.
This is not a success-theater talk. I'll walk through how we made the decision and the alternatives we rejected, the problems we knew about going in (ecosystem immaturity, missing primitives, knowledge gaps), and why we treated escape hatches as a first-class part of the architecture rather than an embarrassing workaround.
I'll also cover the part nobody puts in the RFC: the tooling and education investment needed to bring an entire engineering org along.