NativeScript iOS Daily: The Runtime Goes Web-Standard
The iOS runtime picked up a wave of standard web globals this cycle — AbortController, requestAnimationFrame, native timers, and a new lazy-loading foundation for TextEncoder and friends — all aimed at closing the gap with web and Android behavior.
Duration: PT2M24S
Episode overview
This episode is a short developer briefing from NativeScript iOS Daily.
It explains recent repository work in plain language.
- Show: NativeScript iOS Daily
- Published: 2026-08-25T13:17:00Z
- Audio duration: PT2M24S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's August 25th, 2026, and this is NativeScript iOS Daily.
The clear signal today: the runtime is converging hard on standard web APIs, and doing it in a way that's built for scale rather than one-off additions.
Start with PR 447, from Eduardo Speroni, which adds AbortController and AbortSignal as globals across every isolate — main thread and workers alike. It's modeled directly on Node's internal implementation, right down to throwing a type error if you try to construct an AbortSignal directly. This gives developers the…
Next, PR 446 adds requestAnimationFrame and cancelAnimationFrame, backed by CADisplayLink, with explicit Android parity in the frame-callback behavior. That matters for anyone writing animation code that's meant to behave the same on both platforms.
Then there's commit 9399899, which exposes setTimeout, setInterval, clearTimeout, and clearInterval directly under their standard names instead of the old double-underscore-NS-prefixed versions. The test app's NSTimer-based polyfill for setTimeout has been retired — tests now run on native timers, with NSTimer…
The forward-looking piece is PR 448, still open: it introduces a lazy-global tier, using…