Implement Pull‑to‑Refresh in a Titanium Alloy TableView
Add a built‑in RefreshControl to a TableView, bind data, and handle the refresh callback so the spinner appears on pull and hides after data reloads.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Add a built‑in RefreshControl to a TableView, bind data, and handle the refresh callback so the spinner appears on pull and hides after data reloads.
Learn when to use Ti.App.Properties versus Ti.Database for local data in Titanium SDK apps, with a comparison table, trade‑offs, and ready‑to‑copy code examples.
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 optimize the Titanium Bridge to prevent UI lag. Discover why frequent JS‑to‑Native calls cause "jank" and how to implement throttling and native extensions for better performance.
The goal is to determine the correct CLI response when a project’s tiapp.xml pins an SDK version that is not present after an upgrade. Constraints include the side‑by‑side installation model, the distinction between the global default SDK and the per‑project pin, the possibility of a partially extracted SDK that appears in the list but is unusable, and the v
A persistent discrepancy exists between Titanium SDK development and production builds for code that depends on JavaScript symbol identity. The precise goal is to determine how applications relying on function name introspection, parameter inspection, or computed require() paths can maintain consistent behavior across both build configurations. Production bu
When storing timestamps via Ti.App.Properties.setString() , the ISO string produced by JSON.stringify(new Date()) is always UTC (ending in Z ). If the device timezone changes between write and read — for example, the user travels or the system applies a DST transition — parsing the stored string with new Date(storedString) yields a different local offset tha
Cross-platform redirect behavior Since Titanium SDK 7.0 migrated iOS to NSURLSession and SDK 8.0 migrated Android to OkHttp, both backends enable HTTP keep-alive by default and follow redirects automatically. However, the handling of request headers — particularly Authorization — on cross-origin redirects differs between the underlying platform stacks. NSURL
Goal Ensuring a truly fullscreen experience on both iOS and Android within Titanium SDK. Current State In SDK 5.0 the fullscreen property was removed from Ti.UI.Window for iOS, while it remains on Android. Setting fullscreen:true on iOS has no effect; the status bar and navigation bar persist unless additional native calls are made. Android’s behaviour can b