React Native实战：用JavaScript打造原生移动应用

5星 · 超过95%的资源需积分: 10 160 浏览量更新于2024-07-21 4 收藏 4.67MB PDF 举报

《利用JavaScript构建原生移动应用：学习React Native实战指南》是一本由Bonnie Eisenman编著的实用书籍，专为Web开发者和前端软件工程师设计，帮助他们掌握如何使用React Native技术开发高质量的移动应用。React Native的独特之处在于它将React.js的优势带入移动开发，通过真正的原生渲染，提供接近于原生应用的速度、外观和体验。本书的核心内容包括： 1. **介绍**（Chapter 1）：首先介绍了React Native的工作原理，阐述了虚拟DOM在React中的作用以及React Native如何实现“原生”效果。作者强调了React Native的优势，如跨平台开发能力、利用现有前端技能、以及对开发工具的整合。 2. **入门**（Chapter 2）：指导读者设置开发环境，安装React Native，并创建和运行第一个应用程序。章节中还讲解了如何将应用上传到设备进行测试。此外，通过探索示例代码，读者可以逐步熟悉React Native的基本操作。 3. **组件与移动端设计**（Chapter 3）：深入探讨如何使用平台原生UI元素来构建用户界面，利用Flexbox进行布局和自定义样式。这部分内容是理解如何将网页思维转化为移动应用的关键。 4. **风格和平台API**（Chapter 4）：详细说明如何有效地使用平台特定的设计模式，同时讨论了如何利用JavaScript访问主机平台API，如地理定位和本地存储功能。 5. **React Native生命周期管理**：解释React Native应用从启动到销毁的完整生命周期，这对于理解和优化应用性能至关重要。 6. **视图操作与样式处理**：讲解如何在React Native中高效地工作，包括如何处理视图层次结构和应用样式规则，尤其是通过JSX语法与React Native的集成。 7. **总结与比较**：对比了React Native与传统Web开发的异同，以及在移动应用开发中的适用场景。通过阅读本书，读者不仅能学习到如何编写高质量的原生移动应用，还能提升跨平台开发的能力，为在iOS和其他移动平台上使用React Native奠定坚实的基础。无论是对Web开发者转型还是希望扩展技能的软件工程师，这本书都是一份宝贵的资源。

Of course, while you will not be able to reuse all of your code, working in React

Native means that you can share plenty of it. Business logic and higher-level abstrac‐

tions within your application can be recycled across platforms, as we will discuss in

detail later. Netflix, for instance, has a React application that runs on literally hun‐

dreds of different platforms, and can expand quickly to new devices thanks in part to

code reuse. And the Facebook Ads Manager application for Android shares 87% of its

codebase with the iOS version, as noted in the React Europe 2015 keynote.

This also means that developers who are already comfortable working on any given

platform can still benefit from using React Native. For instance, an iOS developer

equipped with knowledge of React Native can write mobile applications that can then

be adapted easily for Android.

It’s also worth mentioning a perhaps less-obvious bonus: you will be using React for

the “write anywhere” part of this equation. React has gained popularity rapidly, and

for good reason. It is fast, and flexbile; the component-based approach implicitly

encourages you to write clean, modular code that can scale to accommodate complex

applications. The facets of React that are most appreciated by the community apply

equally well to React Native.

Leveraging the native platform

React Native gives you the benefits of native development, and allows you to take

advantage of whatever platform you are developing for. This includes UI elements

and animations, as well as platform-specific APIs, such as geolocation or the camera

roll.

We can contrast this with existing cross-platform mobile solutions. Many of them

allow you to develop inside of thinly-disguised browser components, which then re-

implement pieces of the native UI. However, these applications often feel a little “off.”

It is usually impossible to fully replicate native UI elements, and as a result, aspects of

your application such as animations and styling can feel clunky or just less-than-

natural. React Native lets you neatly circumvent this problem.

Compared with traditional mobile application development, React Native does not

have quite the same access to its host platform. There is a slight layer of added com‐

plexity to using APIs not yet supported by the React Native core, for instance, and

synchronous APIs in particular pose a challenge.

Developer tools

The React Native team has baked strong developer tools and meaningful error mes‐

sages into the framework, so that working with robust tools is a natural part of your

development experience. As a result, React Native is able to remove many of the pain

points associated with mobile development.

14 | Chapter 1: Introduction

All of these small perks add up to saving you and your fellow developers time and

energy, allowing you to focus on the more interesting parts of your work and be more

productive overall.

Using existing platform knowledge

For developers already accustomed to writing traditional native applications on a

given platform, moving to React Native does not obsolete your platform-specific

knowledge. Far from it; there are a number of circumstances in which this knowledge

becomes critical. Occasionally, you will discover that the React Native “bridge” for a

given platform does not yet support host platform APIs or features that you will need.

For instance, being comfortable working with Objective-C enables you to jump in

and add to the React Native “bridge” when necessary, thereby extending React

Native’s support for iOS.

Community support will likely play a large factor in how React Native evolves on new

platforms. Developers who are able to contribute back to the platform by building out

the bridge will be better equipped to explore using React Native on new platforms, as

well as lay the groundwork for its success.

Risks and Drawbacks

The largest risk that comes with using React Native is related to its maturity level. As

a young project, React Native will inevitably contain its share of bugs and unopti‐

mized implementations. This risk is somewhat offset by its community. Facebook,

after all, is using React Native in production, and the community contributions have

been proceeding at a good tempo. Nevertheless, working with bleeding-edge technol‐

ogy does mean that you can expect a few paper cuts along the way.

Similarly, by using React Native, you are relying heavily on a library that is not neces‐

sarily endorsed by the host platform you are working on. Because the Native team

may not be able to coordinate with Apple, for instance, we can imagine that new iOS

releases could require a scramble to get the React Native library up to speed. For most

platforms, however, this should be a relatively minor concern.

The other major drawback is what happens when you encounter a limitation in React

Native. Say that you want to to add support for a host platform API not yet built into

the React Native core library. If you are a developer who is only comfortable in Java‐

script, there is a nontrivial learning curve to add this support yourself. We will

address exactly this scenario later in the book, and I will demonstrate how to expose

Objective-C interfaces to your Javascript code.

16 | Chapter 1: Introduction

Summary

React Native has much to offer for any developer, but a lot will depend on your indi‐

vidual situation. If you are already comfortable working with React, the value propo‐

sition of React Native is clear: it gives you a low-investment way to transfer your skills

and write for multiple platforms, without the usual drawbacks of cross-platform

development frameworks. Even for developers who are comfortable building tradi‐

tional native mobile applications, there is a lot of appeal here, too. On the other hand,

if total platform stability is a must for you, React Native might not be the best choice.

That being said, with React Native applications doing quite well in the iOS App Store

already, this is a less risky proposition than you might think. Facebook, at least, is bet‐

ting heavily on the React Native approach to mobile development. Though the main

Facebook mobile applications are still written traditionally, you can see React Native

succeeding in the wild by downloading Facebook’s Groups app for iOS, which fea‐

tures a blend of React Native and Objective-C code; or the Ads Manager for iOS,

which is a 100% React Native application.

Hopefully all of this has left you excited to begin working with React Native! In the

next section, we will tackle the information you will need to know in order to work

with React Native as opposed to React in the browser.

Native VS React for Web

While React Native is very similar to React for the web, it comes with own considera‐

tions, quirks, and behaviors. In this section, we will take a look at some of these dif‐

ferences, in order to set you up for getting your hands dirty with building iOS

applications in the next chapter. Our focus will be on using React Native for iOS, but

the best practices we will be covering can apply equally well to React Native on other

platforms as well.

The React Native Lifecycle

If you are accustomed to working in React, the React lifecycle should be familiar to

you. When React runs in the browser, the render lifecycle begins by mounting your

React components:

Figure 1-4. Mounting components in React

After that, React handles the rendering and re-rendering of your component as nec‐

essary.

Native VS React for Web | 17

剩余103页未读，继续阅读

ramissue

粉丝: 354
资源: 1487

React Native实战：用JavaScript打造原生移动应用

React.js与React Native代码精华集

React项目实战：React.js与React Native资源库深度解析

React Native 0.28.0 RC.0 版本更新概览

Learning React Native - Building Native Mobile Apps with JavaScript 2nd Edition

Learning React Native Building Native Mobile Apps with JavaScript(2nd) epub

Learning React Native Building Native Mobile Apps with JavaScript(2nd) azw3

Learning React Native Building Native Mobile Apps with JavaScript(2nd) 无水印pdf

Learning React Native Building Native Mobile Apps with JavaScript 2nd Ed (MOBI)

React Native – Building Mobile Apps with JavaScript azw3

Learning React Native 英文版

最新资源