Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Shipping Mobile Features at Web Speed with Webv...

Shipping Mobile Features at Web Speed with Webview: Sharing React Code Across Web and Mobile

This 15‑minute talk summarizes a Webview‑first approach that uses Webview + React to ship mobile features at web speed while preserving a native‑like experience via a native token bridge and mobile‑appropriate routing. We’ll share a three‑layer architecture (Shared Business Logic / Platform / Foundation), code‑sharing techniques with TanStack Router and React Query, and the lessons that let us roll out features on iOS/Android quickly and confidently.

Key Takeaways
A three‑layer architecture model that separates business logic from platform‑specific UX, enabling high code reuse (up to 50–82% depending on the feature).

Authentication strategies for Web vs Webview: from OIDC on the web to a native token bridge on mobile—smooth, secure, and maintainable.

This talk is from the real-world experience at EarnIn.

Avatar for Siwat Kaolueng

Siwat Kaolueng

March 10, 2026
Tweet

More Decks by Siwat Kaolueng

Other Decks in Technology

Transcript

  1. Shipping Mobile Features at Web Speed with Webview: Sharing React

    Code Across Web and Mobile ABAAAA FOSSASIA Summit 2026 March 10, 2026 Siwat Kaolueng Senior Software Engineer at EarnIn
  2. Agenda for today 1. Why? 2. Technology 3. Project structure

    4. Pattern 5. Bridge event 6. Authentication 7. Result 8. Summary
  3. Technology Nx - Monorepo React - Web & Webview Tanstack

    Query - Web & Webview Tanstack Router - Webview React Router - Web Zustand - Web & Webview Storybook - Web & Webview Module Federation - Web …
  4. Logging send logs to native observability pipeline Error & Session

    Manage errors and authentication lifecycle Analytics send tracking events to native analytics UI Control tell native to perform UI actions Bridge event - Webview ↔ Native Communication
  5. Share the lib, split the app Callback-Driven Components Shared components

    own UI, platform wrappers own navigation and side effects Contract-First Native Bridge Align with mobile engineers on channel names, message shapes, and auth flow before you build Shared business logic in libs, web and webview are just thin deployment targets