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

Summiz Holo

React Native's challenges with controlled inputs, performance issues, and the advantages of uncontrolled inputs in mobile development

• React Native should discourage using controlled inputs because they are currently deeply broken.
• Darren Aamv's perspective on React has shifted as he has become more involved in mobile development.
• Controlled inputs can lead to performance issues, such as lagging keys, especially when the update layer is inconsistent.
• Uncontrolled inputs allow for better performance since the state is managed by the browser instead of React.
• React Hook Form is recommended for managing uncontrolled inputs, but there may be issues when using it with React Native.

Inherent issues with controlled inputs in React Native leading to user experience degradation, cursor lag, and persistent bugs

• Discouragement of using controlled inputs in React Native due to inherent issues.
• Basic controlled text editing is broken in React Native, affecting user experience.
• Cursor lagging behind typing leads to incorrect user input, which is a significant problem.
• The perception that React Native cannot produce high-quality native apps is influenced by these issues.
• Bugs related to controlled inputs persist even in the new architecture of React Native.
• Workarounds often involve using default value to avoid controlled inputs entirely.
• Multi-line controlled inputs can enter an infinite loop under certain conditions.
• The implementation of the value field in text input is broken in multiple subtle ways.
• There is a need for prioritizing fixes for fundamental features in React Native.

React Native's critical input handling failures, user experience degradation, and the urgent need for prioritizing native behavior restoration

• The problem with controlled inputs in React Native is that they detach from the native layer, leading to poor user experience when typing.
• There is frustration with React Native's handling of text input, especially compared to Flutter.
• Inputs must not drop keystrokes or lose cursor position; these issues undermine trust in the framework.
• React historically set users up for success, but there are concerns about the current state of React Native's input handling.
• There is a need for greater focus on the onboarding path and getting started experience in React Native.
• Inputs being broken is considered a severe issue that should be treated with higher priority.
• React Native should not degrade the default behavior of native components, especially in common use cases.
• The original ethos of the React project should be reflected upon to ensure it remains relevant in addressing key issues.