Google recently reiterated that, when Android Q launches, they’ll start enforcing a requirement for all Android apps using native code to provide a 64-bit version as they phase out 32-bit support. As you’d expect, this has far-reaching implications for app developers, depending on the languages and libraries they use – particularly for Unity and Adobe AIR developers. Continue reading Android’s 64-bit requirement puts pressure on Adobe
One of the most problematic constraints when developing applications for resource constrained devices, such as mobile or Set Top Box is ‘video memory’.
You often will not have control over how much video memory is allocated to your application, or what the fallback behaviour is when your application uses too much. Continue reading Sneaky tricks for developing on small devices: ‘Bitmap Folding’
YouView is a Smart TV service in the UK, a spin-off of a BBC RnD project which runs on Set Top Boxes and certain Smart TVs. I worked on the core UI for years and thought I’d share some insights into best practices when building applications for such resource constrained devices.
A couple of years ago, I created an object pooling utility for a games project I was building in AS3. Since then, I’ve used it quite a few times, in order to speed up apps and improve resource management, easing the load on the garbage collector by reusing objects instead of recreating them. Continue reading Loan Shark – fast object pooling utility
I had a conversation yesterday with a friend and colleague about how his company should standardise their development environment for all Flashers – be they contract or perm, junior to senior.