Dynamic Feature Deployment for iOS Apps: NJCS Architecture and Implementation

iOS app review and release cycles create a delay between feature completion and user availability; when urgent fixes are needed, a full re‑submission is too slow.

Dynamic feature deployment refers to updating app content or business logic on an already released iOS app without issuing a new version, enabling rapid bug fixes and A/B testing.

Advantages include bypassing App Store review, no version release, and the ability to target specific user groups; disadvantages involve potential conflicts with Apple’s guidelines that forbid hidden or undocumented functionality.

Common approaches on the market include Web Apps, Hybrid Apps, React Native, and Weex, each offering varying degrees of native integration and performance.

The article introduces NJCS, a lightweight dynamic deployment solution built on Objective‑C Runtime and JScore that does not depend on any front‑end framework, making it friendly to native iOS developers.

NJCS is organized into four layers: the JS business layer (defines UI components and logic), the JS core layer (class definitions, inheritance, data parsing), the Native core layer (unpacks data, executes operations such as type parsing, UI management, networking, database access, multithreading), and the Native presentation layer (renders results). Data flows from the JS business layer to the JS core, then to the Native core, and finally to the presentation layer.

Example code shows how JavaScript obtains a native class and creates a label: var UILabel = GetNativeClass("NJCSUILabel"); var labelInstance = UILabel.alloc().init(); labelInstance.setText("Hello world, it is NJCS.");

Implementation challenges include invoking native methods from JavaScript, handling native components with delegates (e.g., UIWebView, UITableView), and ensuring security. NJCS secures the system by verifying the source of JS files through asymmetric encryption and MD5 checks, and by restricting access to sensitive native classes via a registration pool that throws exceptions for unauthorized requests.

The article concludes with a brief summary of the design and mentions forthcoming detailed theoretical articles on iOS dynamic feature deployment.