Daily notes for people who still ship with ActionScript, AIR and Animate.
Release checklists, code patterns, migration advice and a small job board, written for developers and animators who work with the Flash platform and its successors.
Latest notes
How to write a job post that Flash and AIR developers will answer
Be specific about the stack, the codebase and the future. Experienced developers want to know what they will maintain and what they will build.
Five timeline habits that keep Animate files tidy
Naming, folders, frame labels, registration points and one place for code. Small habits that save hours on shared projects.
A release checklist for AIR mobile apps
Certificates, version numbers, icons, permissions and device testing: the boring items that block a store submission.
What an AIR native extension actually does
Native extensions are the bridge between ActionScript and platform code. Here is how the pieces fit, in plain terms.
Object pooling in ActionScript 3, step by step
Reuse bullets, particles and list rows instead of creating them every frame. A small generic pool with a complete example.
Moving a legacy SWF project to a modern runtime
A practical decision path: inventory what you have, pick between emulate, port or rebuild, and test before you promise a date.
The runtime landscape at a glance
Where Flash-era projects can run today: emulation, the AIR runtime, open-source ports and HTML5 export, compared in one short read.