04-18-2012 01:57 PM
Another reason of course is that non technical user just don't want to be bothered by the kind of "you do not have the latest bla bla bla" kind of notifications with whatever easy made upgrade options.
04-18-2012 02:21 PM
04-18-2012 03:07 PM - edited 04-18-2012 03:09 PM
It all depends what kind of application you develop and for what market / users. I develop specialised business apps for a limited market. However, it is a market of non technical users who just want to plug and play. They are likely not bothering about the latest AIR on their devices, let alone bothering about AIR at all. The few mb added with the captive runtime are nothing. The market is target is users with the latest gadgets and high speced. Memory and bandwidth is not a concern. Problems with not being able to use the latest software (sdk) is!
04-19-2012 03:28 AM
Embedding runtime in each app. is not the most effcient for sure, but it's clearly the way-to-go to avoid a lot of issues, and to be up-to-date by definition, which is the key to get benefits of the "buzzed" functionalities.
(Plus it's about extra 10 Mo for each app.? ... not really a big deal to me.)
04-19-2012 04:03 AM
Allowing captive runtime would not only wast precious bandwidth (just think of the extra costs of App World), it would also prevent RIM from performing optimisations to the AIR runtime for the PlayBook hardware.
04-19-2012 04:38 AM - edited 04-19-2012 04:39 AM
I may miss something but I don't understand why you call "precious bandwidth" a 10Mo extra for a one shot app. download. The bandwidth is mainly consumed by video (talking about HD?) or frequent data transfer. No?
04-19-2012 04:53 AM
I would prefere AIR over Cascades, because its a crossplatform technology and i can easily switch to another platform if BB10 is not successful. If BB10 devices sell well, i will try cascades. There is a big demand for crossplatform technologies and AIR is imho the best one so far. So RIM should continue to push AIR and update to 3.2. asap.
04-19-2012 05:58 AM
Indeed, I too don't understand this bandwidth argument. Most 3d games come at 100+ MB. One of my main apps is 1.5 MB with captive runtime 10.5 MB. That is a pretty small app in comparison. This bandwidth argument is nonsense.
The argument of RIM being able to optimise the SDK for their devices is OK, however, if you do not need top performance (my apps are business data centric, no complex graphics), the alternative of using a non optimised captive runtime is a reasonable choice.
04-19-2012 01:56 PM
It's not an extra 9 mb that passes once, but depending on your success up to thousands of times. Data traffic is not free and every saved bit is worth some effort.