] The way BlackBerry implemented long running background processes is the right way to do it. Separate the business logic from the UI and make sure the background process is using as little resources as possible. I think the actual issue isn't the implementation of long running background processes, but just the fact the BlackBerry is forcing many developers to use this complex approach where they actually want something completely different. 99% of background use cases are event driven. Many apps just want to do something once in a while, like at a certain time (think alarm apps), in certain intervals (weather apps, wallpaper apps) or when messages come in (think LED apps, call blockers etc).They have laid the foundation for this but failed on executing. They only provide a handful (actually 2) event triggers. So now many developers have to adopt the (rightfully) restricted and complex process of long running background processes, a paradigm that actually doesn't fit their use case, just to implement what is missing in event driven triggers. I understand how this is creating the frustration.
] COMMENT on bb dev blog
Hey Alex, developer here, working on building the next big thing, i want to bring it to the blackberry 10 platform but have no experience with developing with this Cascades you speak of. This video looks like exactly what i could use to get started. Apologies for my blindness but i cant find the link anywhere on the page.