AI summary by TwinMind

React Native is kind of broken (they NEED to fix this)

Theo - t3․gg

16m 16s

React Native Controlled Inputs Crisis

  • Dan Abramov (former React team member, now at Blue Sky) creates PR to discourage controlled inputs in React Native
  • Claims controlled inputs are "deeply broken" with no confidence they'll be fixed
  • Issue represents major perception problem for React Native's ability to build quality apps

Controlled vs Uncontrolled Inputs Demo

  • Controlled inputs: value managed by React state via onChange handler
    • Problems occur when main thread blocks (even 100ms)
    • Causes laggy keystrokes, cursor position issues
    • State owned by React, not browser/native platform
  • Uncontrolled inputs: value managed by browser/native input itself
    • Remains responsive even with blocking operations
    • Must pull data using refs (input.current.value) instead of onChange
    • State owned by platform, not React

React Hook Form Concerns

  • Traditionally recommended solution for form management
  • May still have same issues when used with React Native controller
  • Controller uses render function passing value to text input
  • Likely creates same controlled input problems

Dan's Specific Bug Reports

  • Primary issue: Cursor jumps to wrong position during fast typing
    • Affects basic Hello World example
    • Causes incorrect user input, not theoretical bug
    • Exists in production, described as "embarrassing"
  • Secondary issue: Multi-line controlled inputs enter infinite loop
    • Occurs when using portals with multi-line text input
    • Removing multi-line prop fixes issue
    • Demonstrates fundamental architectural problems

Framework Architecture Problems

  • Native vs JavaScript control: Input element is native but value control is JavaScript
  • Performance impact: Having to leave native layer for typing is inherently bad
  • Platform fidelity: React Native should faithfully wrap native components without degrading behavior
  • New architecture: Issues persist even with Fabric architecture

Community Response & Solutions

  • Jose Soana (React Native team) acknowledges issue doesn't meet standards
  • Will prioritize investigation ASAP
  • Proposed immediate fixes:
    • Add warning documentation about controlled inputs
    • Recommend default value and uncontrolled inputs
    • Consider deprecation warnings in editor

Broader React Native Ecosystem Issues

  • Getting started problems: Default templates missing basic linting rules
  • Focus misalignment: Team focused on large-scale projects vs onboarding experience
  • Expo burden: Handling infrastructure, debugging, deployment while React Native team focuses elsewhere
  • Severity classification: Should be treated as S0/S1 severity issue (critical)

Historical Context & Recommendations

  • React historically made default usage patterns successful
  • Need dedicated person for maintaining happy path onboarding
  • Establish baseline where native controls don't degrade platform UX
  • Treat platform fidelity degradation as high severity issues
  • Consider whether original project ethos still relevant

TwinMind

Get summaries like this for your own meetings

TwinMind takes notes in the background during meetings, lectures, and calls, then writes the summary for you.

Free plan to get started

No bot joins your calls

Phone, desktop & Chrome apps

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome