Appcelerator Titanium SDK ↔ Node.js Build Tool – Interoperability Question: Alloy or Native UI

Goal

Establish a repeatable build environment for Appcelerator Titanium projects that integrates the Titanium SDK, Node.js runtime, and Titanium CLI while deciding on the UI development strategy.

Constraints & Uncertainty

The Titanium CLI requires Node.js ≥12 and pulls platform SDK binaries (Android SDK, Xcode) during each build. These binaries are not bundled, so their installation paths can vary and affect reproducibility. The UI layer can be built either with the Alloy MVC framework, which introduces a compile step and runtime overhead, or with native Titanium UI components that demand more boilerplate but avoid the extra build step.

Unresolved Decision

Which UI approach provides the best balance between maintainability, build performance, and runtime efficiency in a containerized, repeatable pipeline?

Specific Questions

1. How does the Titanium CLI orchestrate platform‑specific SDKs and Node.js modules to produce a consistent build output across different host environments?
2. What impact does the choice between Alloy’s declarative XML/JS and native Titanium components have on build time, bundle size, and runtime overhead in a Docker‑based build?
3. Which strategy minimizes the risk of build failures due to platform SDK path changes or Node.js version incompatibilities?