Cross-Platform on Time Friend

Recommended Order for Developing Taro Multi-Platform Applications

Wed, 16 Dec 2020 22:17:36 +0000

Developing Taro Multi-Platform Applications with Minimal Cost

All mini-programs, quick apps, React Native apps, etc. in our company are now being developed using Taro.

If you only need to support one platform, developing with Taro is no problem at all.

However, if you want to develop once and have it run normally on all platforms, you need to pay attention to many details.

Each platform has its own challenges.

Development Difficulty Ranking

Huawei Quick App > Quick App > React Native > Swan Mini-Program > WeChat Mini-Program > H5

How to Optimize Bundle Size for Quick Apps Developed with Taro

Tue, 15 Dec 2020 22:17:36 +0000

Quick App Duplicate Bundling Issue

When developing quick apps with Taro, there’s one issue that absolutely cannot be ignored: bundle size.

Due to the bundling characteristics of quick apps (below version 1080), if a third-party library is repeatedly used across multiple pages, that library’s code will be bundled into each page, causing the same code to exist in multiple pages.

Because quick app version 1080 is not yet widely deployed. If you rashly upgrade your quick app’s minimum platform version to 1080, you will lose a large number of users on lower versions.

Making Taro UI Support React Native

Thu, 27 Aug 2020 22:17:36 +0000

The Dilemma of Taro UI Not Supporting RN

Taro UI documentation mentioned early on that it might support RN, but it’s been over a year, and due to manpower issues in the Taro UI team, it hasn’t been compatible with RN yet.

Business is urgent, we can’t wait for that day. Do it yourself and you’ll have everything you need.

Problems with Traditional Taro Component Packaging on RN

Generally, after a component library is packaged, the dist/index.js file will look like this.

Taro Cross-Platform Development - Multi-Business Module Management React Native (Final)

Tue, 25 Aug 2020 22:17:36 +0000

React Native Hot Update Solution

RN business is becoming increasingly large, and more teams are collaborating. RN’s dynamic capabilities must be put on the agenda. For RN hot updates, the first problem is code splitting.

RN’s base library is very large, plus we depend on many third-party libraries. This code must be separated during code splitting. Business packages should be relatively pure, containing only business code. This ensures business packages are smaller, ensuring speed during hot updates.

Taro Cross-Platform Development - Multi-Business Module Management React Native (Part 2)

Sun, 23 Aug 2020 22:17:36 +0000

Implement a Simple Module Management Tool to Solve the Problem of Slow npm Pulling of Business Modules

Using npm to pull git repositories, the speed is actually acceptable. The main slowness is during postinstall when npm pulls git repositories, it needs to rebuild project code. Another point is that business modules also have dependencies, and npm install also needs to pull the same dependencies again.

These two steps can actually be omitted. The solution is to implement a simple module management tool to replace npm’s handling of loading business modules.

Taro Cross-Platform Development - Multi-Business Module Management React Native (Part 1)

Fri, 21 Aug 2020 22:17:36 +0000

How Can Native RN Projects and Taro Coexist?

Our team started practicing native React Native projects early on, for a long time,

All business modules were developed and maintained in one project. Over time, this project became a behemoth.

Plus later we introduced RN projects based on Taro development. To ensure native and Taro RN coexistence,

Whether it’s native RN projects or Taro projects, the main export index file format in package.json files is consistent.

Taro Cross-Platform Development - Dependency Management Issues

Thu, 20 Aug 2020 22:17:36 +0000

Currently, the platforms we reach through Taro include:

WeChat Mini Program
QQ Mini Program
Baidu Mini Program
React Native
H5
Quick App

To quickly allow business to reach all platforms, each of our business modules is independent.

They are compatible with different platforms according to business needs, and then assembled into a complete project during build time.

To meet the above needs and enable flexible development, each business module can be independently developed and run, without depending on the main project.

Taro Cross-Platform Development - Thoughts and Measures on the New Era of Cross-Platform Development

Tue, 16 Jun 2020 22:17:36 +0000

New Era

The emergence of cross-platform frameworks has transitioned front-end browser compatibility to a new era of client platform compatibility.

For startups, this type of framework can quickly test and reduce human and time costs.

Why Choose Taro

It’s not that Taro solution is particularly excellent. At the current time point, all current cross-platform frameworks are still in the improvement stage. The most complete platforms might be mini programs and H5.