Learn how to use Appcelerator Titanium's Alloy framework to handle platform-specific UI differences without cluttering your JavaScript logic with conditional statements.
Learn how to move performance‑critical code from Titanium’s JavaScript layer into a custom native module to reduce bridge overhead and improve app responsiveness.
Learn how to use the Alloy MVC framework in Appcelerator Titanium to decouple UI markup, styling, and business logic for more maintainable cross-platform apps.
Native Toolchain Integration Appcelerator Titanium relies on a bridge layer to map JavaScript API calls to native platform implementations. The build process utilizes platform-specific toolchains, such as Xcode for iOS and Gradle for Android, to compile these binaries based on the settings defined in ti.app and ti.app-config . When integrating custom native
Symptom When building a Titanium project with the CLI, the build process frequently picks the most recently installed SDK even though the project’s tiapp.xml specifies a different <sdk-version> . This leads to build failures on CI pipelines that expect a stable, pinned SDK. Constraints & Uncertainties The SDK Manager can install multiple SDKs, but
Titanium SDK 5.0.0 Ant Deprecation: Timeline Unresolved The 5.0.0 release made Gradle the default Android build tool, marking Ant support as deprecated. Projects still using Ant must run a migration script to generate Gradle build files, but the script does not cover custom Ant targets or non‑standard configurations. Unresolved Decision The SDK documentation