Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
React and React Native

You're reading from   React and React Native Build cross-platform JavaScript apps with native power for mobile, web and desktop

Arrow left icon
Product type Paperback
Published in Mar 2017
Publisher Packt
ISBN-13 9781786465658
Length 500 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Adam Boduch Adam Boduch
Author Profile Icon Adam Boduch
Adam Boduch
Arrow right icon
View More author details
Toc

Table of Contents (27) Chapters Close

Preface 1. Why React? 2. Rendering with JSX FREE CHAPTER 3. Understanding Properties and State 4. Event Handling – The React Way 5. Crafting Reusable Components 6. The React Component Lifecycle 7. Validating Component Properties 8. Extending Components 9. Handling Navigation with Routes 10. Server-Side React Components 11. Mobile-First React Components 12. Why React Native? 13. Kickstarting React Native Projects 14. Building Responsive Layouts with Flexbox 15. Navigating Between Screens 16. Rendering Item Lists 17. Showing Progress 18. Geolocation and Maps 19. Collecting User Input 20. Alerts, Notifications, and Confirmation 21. Responding to User Gestures 22. Controlling Image Display 23. Going Offline 24. Handling Application State 25. Why Relay and GraphQL? 26. Building a Relay React App

Unified information architecture

Let's take a moment to recap the ingredients of our application architecture so far:

  • React Web: Applications that run in web browsers
  • React Native: Applications that run natively on mobile platforms
  • Flux: Patterns for scalable data in React applications

Remember, React is just an abstraction that sits on top of a render target. The two main render targets are browsers and mobile native. This list will likely grow, so it's up to us to design our architecture in a way that doesn't exclude future possibilities. The challenge is that you're not porting a web application to a native mobile application; they're different applications, but they serve the same purpose.

Having said that, is there a way that we can still have some kind of unified information architecture based on ideas from Flux that can be used by these different applications? The best answer I can come up with, unfortunately, is: sort of. You don't want to let the different...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image