ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Stop rendering hundreds of Titanium rows in a ScrollView. Use Alloy Collections with Ti.UI.ListView to recycle list items and reduce memory on mobile devices.
Alloy gives Titanium apps MVC structure with zero runtime cost, but data binding is one-way by default, platform files resolve at compile time, and debugging means reading generated code. Includes a complete Book list example with model, view, controller, TSS styling, and verification steps.
Architecture notes for persisting Alloy models to SQLite in Titanium, including schema boundaries, encryption, migrations, and UI-thread checks.
Learn how to scaffold an Alloy‑based Titanium project, add a model‑view‑controller trio, and verify live data binding between model properties and UI labels.
Appcelerator Alloy MVC shares UI logic across iOS and Android while keeping platform-specific chrome in separate view files. This blog walks through a contact list example with shared models, declarative XML views, TSS styling, and platform overrides — plus debugging trade-offs.
Learn how to keep a single Alloy controller while tailoring layouts for each OS using .ios.xml/.android.xml files and TSS selectors, with a concrete example and verification steps.
Learn when to use Alloy's MVC structure for standard screens and when to drop to raw Titanium SDK for performance‑critical or highly customized UI in Appcelerator projects.
Step‑by‑step guide to create a Backbone‑based model, bind it to an Alloy TableView, fetch remote data, and verify live updates without a full rebuild.
Learn how to bind a Backbone collection to a Titanium Alloy ListView so the UI updates automatically when the data changes.
appcelerator
sqlite
titaniumsdk