Don't Panic: React Native Fundamentals

React Native is a way to describe a mobile interface with React and JavaScript, then render it through native platform UI. That is the useful bit. You write a screen as components instead of maintaining two unrelated descriptions of the same button, field, and list. It is not a spell that makes Android and iOS agree about everything. It is a shared starting point, which is much more honest and far more useful.

The thing to keep in your head is the component tree. A parent component contains children. View groups them, Text shows words, TextInput accepts keyboard input, Pressable notices presses, and Image shows images. Props are values a parent supplies when something renders. State is the small pocket of data that changes after an interaction. There is no tiny committee inside the phone deciding this for you: change state, and React Native updates the interface that follows from it.

Layout is Flexbox, with a few manners of its own. Children flow in a column unless you choose otherwise, and flexShrink begins at zero. That second detail has surprised enough web developers to deserve a chair at the meeting. For a long repeated collection, FlatList or SectionList renders the rows that are currently visible instead of treating a long screen as an endurance event.

Then comes platform-specific code, which sounds alarming but usually means one sober question: do both platforms need the same behavior? If yes, keep the component shared. If one small value differs, use the Platform module. If the implementation genuinely differs, use Android and iOS files. Sharing code is valuable because it avoids duplicate work, not because users should receive an interface that ignores their platform.

Read the Intro when you want the full model and its limits. Use Slides for the relationships between components, state, layout, and the platform boundary. Keep the Cheatsheet nearby while building a screen. The Practice reference and Exercise turn that map into a testable preferences screen. React Native supplies the foundation. The remaining decisions are still yours, because software has yet to invent a framework that politely makes them disappear.

Don't Panic: React Native Fundamentals

Relevant careers