A guide to React Native Development

How to work through this course

Eight modules, roughly seventy to a hundred hours of real work. You can read it in a weekend and you will not be able to build anything, because the gap between knowing React and shipping a mobile app is not knowledge - it is the two dozen small platform facts you only meet by running the thing on a phone.

Build one app, from Module 2 to the end.

Pick something small on the first day and carry it through. A reading list, a workout log, a bill splitter. Each module adds to it: Module 2 lays out a screen, Module 3 gives it a list and navigation, Module 4 connects it to an API, Module 5 adds the camera or location, Module 6 makes it feel alive, Module 8 ships it. One application you keep extending teaches you what a tutorial cannot, which is what happens when a decision you made in week one is still there in week ten.

Small matters. "An app to track the books I read" finishes. "A social network for readers" does not.

Run on a real device from the first week.

The simulator and the emulator are both faster than the phones most of your users have, and they lie in specific ways. The emulator has no real camera, perfect network conditions and your laptop's processor. Remote push notifications never arrive there at all. Install Expo Go on your own phone on day one and keep it in reach - a list that scrolls perfectly on a simulator and stutters on a three-year-old Android is the single most common surprise in this course.

Pacing

Module 1, one week. If you already write TypeScript, skim the first two topics and spend the time on the environment instead. Getting the Android emulator and expo-doctor clean before you need them is worth more than it sounds.

Modules 2 and 3, three weeks together. This is the layout and navigation muscle. Build screens, break them, rotate the device, open the keyboard, test on a phone with a notch.

Module 4, two weeks. The conceptual turn of the whole course is in here: server state is a cache, not state. Once you stop writing isLoading by hand you will not go back.

Module 5, two weeks. Device APIs are mostly reading documentation carefully. The part worth slowing down for is permissions - get the timing and the wording right and the rest is mechanical.

Module 6, one to two weeks. Enjoyable, and genuinely optional for a first app. A good app with no animation beats a janky one with plenty.

Module 7, two weeks. The New Architecture topic is worth reading even if you never write a native module, because it explains why the framework behaves the way it does. Write one module anyway, even a trivial one.

Module 8, two weeks or more. Do this properly on something small before you need it on something that matters. The first submission to either store always takes longer than planned.

Four things that cost React developers the most time

Expecting the web. There is no div, no cascade, no media query, and text has to be inside a Text. The mental model transfers; the specifics do not.

Ignoring the Android emulator until the end. Something always looks different, and finding out in week nine is worse than finding out in week two. Check both platforms at the end of every module.

Reaching for a library too early. The ecosystem is enormous and much of it is unmaintained. Check the last commit date, check it supports the New Architecture, and prefer something in the Expo SDK where one exists, because those are maintained in step with each release.

Following old tutorials. React Native has changed more in the last three years than in the previous five. Anything telling you to eject from Expo, anything about componentWillMount, anything written before the New Architecture, and much of what you will find about navigation describes a framework that no longer exists. Prefer the official documentation and check the date on everything else.

Where to look when you are stuck

The React Native documentation and the Expo documentation are both good and both current - and they are different sites, so search both. Expo's documentation is usually the more practical of the two. For a library, the GitHub issues are often more useful than the README, because the question you have is usually the question someone asked six weeks ago.

Finish something.

Most people who learn React Native never ship. It is almost never the code that stops them - it is the certificate, the screenshot sizes, the privacy policy nobody wrote, the account deletion requirement discovered at submission. Module 8 covers all of it. Do it once on an app nobody will download, and the second time will be ordinary.

react native jsi turbomodules fabric performance mobile development hybrid mobile application development