How to Deploy New Features in iOS Apps Without Releasing a New Version

Preface This article discusses dynamic deployment solutions that allow new content or business flows to be added to an already released iOS app without a new version release, a need driven by Apple’s long review cycles and strict restrictions.

Dynamic deployment essentially combines H5, Lua, JavaScript, and Objective‑C/Swift in various ways. The following five architecture patterns are commonly referenced:

Layered Architecture

Event‑Driven Architecture

Microkernel Architecture

Microservices Architecture

Space‑Based Architecture

Below are the practical options evaluated.

Web App

A Web App is an H5 page accessed via the mobile browser, optimized for mobile UI.

Advantages

Avoids Apple’s review process and associated costs.

Updates take effect instantly, like a website.

No need for native engineers; many frameworks exist.

Disadvantages

Heavy reliance on network connectivity.

Performance and smoothness are inferior to native.

Local persistence is difficult; usually requires server‑side account storage.

Complex to implement real‑time response, remote notifications, and sensor usage.

Security concerns because the H5 page is fully exposed to users.

Summary Web Apps are suitable for early‑stage startups needing rapid iteration, but they serve mainly as a transitional or fallback solution.

Hybrid App

Hybrid frameworks combine H5 with native code or use a JS Bridge for data exchange.

Advantages

Retains all Web App benefits while also supporting native features.

Can access local data and device sensors.

Disadvantages

Still dependent on network connectivity.

User experience may suffer compared to pure native.

Security issues persist.

Large data exchanges (e.g., transferring processed images to H5) are difficult.

Summary Hybrid solutions work well for content‑heavy apps with limited native interaction, such as the Taobao app’s marketing activities.

React‑Native

React‑Native renders native views but allows JavaScript to generate them via a bridge.

Advantages

Fast response, only slightly slower than pure native and much faster than WebView.

Supports a degree of dynamic deployment.

Disadvantages

Views must be provided by native code; adding new view types requires native implementation and bridge exposure.

Dynamic deployment of both view and its event handling is limited.

Summary React‑Native solves the problem of writing iOS views without Objective‑C/Swift, but its ability to dynamically deploy new functionality is limited.

Lua Patch

Based on the Wax framework, Lua Patch uses Lua scripts to replace Objective‑C methods at runtime.

Advantages

Allows method replacement via downloaded scripts.

High execution efficiency.

Disadvantages

Adding new features is complex.

Easy to introduce bugs; small mistakes can become serious issues.

Summary Lua Patch is useful for hot‑fixing bugs but is not ideal for adding new features.

Javascript Patch

Works similarly to Lua Patch but uses JavaScript; JSPatch is a popular library.

Advantages

Shares Lua Patch’s benefits.

No need to bundle an interpreter; iOS already provides a JavaScript engine (iOS 7+).

Disadvantages

Same drawbacks as Lua Patch.

Summary JSPatch is preferred because it leverages the built‑in JavaScript engine and has a larger developer pool.

JSON‑Described View

This approach uses JSON to describe view elements, positions, and properties, which a local interpreter then renders.

Advantages

Enables free view generation and dynamic deployment.

Disadvantages

Performance issues observed in practice.

Event handling must be predefined in native code.

Summary Suitable for skinning or fixed‑event views, but not for fully dynamic interactions.

Architecture Requirements for Dynamic Deployment

Both view and events must be dynamically deployable.

Feature completeness.

Maintainability.

Based on these, the author favors an H5‑Native solution using a JSBridge.

JSBridge‑Based Microservice Architecture

The following diagram illustrates the concept:

H5 initiates calls to native services via the bridge; native provides generic, business‑agnostic services (e.g., sensor data, API calls) while optionally exposing complete business modules when needed.

When native services are unavailable, a new app version is required, mirroring server‑to‑native API patterns.

Dynamic‑Library Microkernel Mode

The author created CTDynamicLibKit to load dynamic libraries, but iOS rejects unsigned or mismatched‑certificate frameworks, resulting in errors such as:

error:Error Domain=NSCocoaErrorDomain Code=3587 "The bundle “DynamicLibDemo” couldn’t be loaded because it is damaged or missing necessary resources."

Thus, dynamic‑library deployment is not feasible for distribution builds.

Conclusion

The article summarizes common dynamic deployment methods, presents a preferred JSBridge‑based solution, and provides implementation guidance.