Question

Name and describe two different approaches to navigation in react native?

Answer 1

There are two essential approaches . We are able either include actual native iOS/Android navigational components or utilize JavaScript to make the specified activitys and components that we require.

1) native iOS/Android navigational components.

2) Navigation with JavaScript components.

1) native iOS/Android navigational components:-In an iOS application, sees are utilized to construct the UI and show substance to the client. A see controller (or the UIViewController class) is utilized to control a set of sees and permits us to put through our UI with our application information.

It'll watch out of counting a header route bar at the best of our gadget with a back button that permits us to pop the current see controller off of the current stack. With this, it keeps up the chain of command of all the screens inside the stack.

In Android, exercises are utilized to form single screens to characterize our UI. Ready to utilize errands in arrange to characterize a stack of exercises known as the back stack. The begin Action strategy can be utilized to begin a modern movement. When this happens, the movement is pushed onto the movement stack. In arrange to return to the past screen, the physical back button on each Android gadget can be squeezed in arrange to run the wrap up strategy on the action.

2) Navigation with JavaScript components:-The moment approach to including route to a Respond Native app is to utilize JavaScript to form components and route designs that see and feel like their native partners.

We are able clarify how this works by utilizing stack route as an case once more. As we said prior, this design permits us to move between screens by pushing a moment screen on beat of the past one. When we endeavor to explore in reverse, the current screen slides back out within the inverse heading or blurs out from the beat.

With the Animated API, able to utilize animated adaptations of a few built-in components such as See as well as make our possess. Able to make stack based route (as well as other route designs) by settling our screen components inside an Vivified component. Ready to then have our screens slide (or blur) in and out of our gadget when we ought to permit the client to explore all through our application. We'll ought to keep up the pecking order of screens completely in JavaScript ourselves.

portable route presents its claim set of challenges. One of the greatest is the decreased genuine bequest of the user's gadget screen compared to a desktop or portable workstation computer. We ought to make beyond any doubt there are effectively unmistakable and identifiable route components that will permit the client to move to another portion of the application when squeezed. Counting a complex route stream comes with the taken a toll of a bigger number of route components (such as menu alternatives).