Screen organization
Thinking in terms of screens is easy in web applications because you have a URL that points to each screen. Put differently, URLs make thinking about screen organization natural and easy. Take the URLs away and suddenly screen organization becomes more difficult.
Imagine trying to build screen transitions in a mobile application without the page abstraction that we take for granted in web interfaces. You would have to build your own abstraction that ensures that each component for each screen is rendered, and subsequently removed once the user moves away from the page. Not ideal.
But, you really want to work with some kind of page because that's what you're used to working with when building React applications for the web, right? In the following section, we'll cover the terminology used in React Native that helps make this happen. The real challenge is simply coming up with the correct screens. It's challenging because there aren't URLs in the traditional sense. However...