02Geek HTML5 and JavaScript, TypeScript, React, Flash, ActionScript online School
Previous VideoNext Video

AIR

Adobe Air allows designers and developers by providing a consistent and flexible development environment for the delivery of applications across devices and platforms. It supports Android, Blackberry , tablet OS and iOS mobile operating. Our of the box it comes with support for GeoLocation,Accelerometer, Camera, Multitouch/Gesture support screen orientation, microphone, GPU acceleration, SQLite DB and more... How ever it doesn't support many things such as Native widgets, Access to contacts and has limited SMS support. In this video Chris will walk through the pluses and minuses and walk through the steps needed to start building an Android Application.

Video Transcript

00:00So Adobe Air has been around for some time.
00:04Initially the desktop had migrated over into the mobile space.
00:08So right now it currently supports Android,
00:12the Blackberry tablet OS, and the iOS mobile operating system.
00:16Those are the mobile spaces it currently supports.
00:20So let's talk about what it can do. Well, out of
00:24the box, it gives you access to the geolocation,
00:28if the phone supports it. Access the accelerometer
00:32if the phone supports it. Access actually to the cameras now.
00:36That was added in version 3, the earlier versions,
00:40252627 did not have support
00:44for multiple cameras. So if your device did have two cameras,
00:48it only supported what was called the primary camera.
00:52It has support for multi-touch and gesture.
00:56Those are actually two different things. Multi-touch allows
01:00the acknowledgement of touching
01:04in two places simultaneously.
01:08And that will be based on whatever the device supports.
01:12Some devices support F-10, some devices support only two.
01:16Something to be aware of as you develop your
01:20application, some of the lower end Android
01:24phones that do support Air are only two
01:28the input device modes.
01:32While some support, theoretically, have to, one thing I think is the limits.
01:36Additional to multi-touch,
01:40within Air itself, it has the ability to understand
01:44gesture. So if you've used a smart phone, you probably have used a swipe gesture,
01:48you've used the potential zoom, you've probably used a rotate gesture.
01:52Out of the box, you can flip into gesture mode
01:56and listen for, explicitly, those gestures the same way you would listen
02:00for a mouse click or a touch tap. So there's no need
02:04for you to try to figure out all the complicated math of saying, oh, did I swipe?
02:08What is a swipe? That's out of the box.
02:12It understands screen orientation.
02:16So that is handled, therefore, for that event within
02:20standard event listener, access to the microphone.
02:24One way these smart phones work
02:28is they all have GPUs in them.
02:32And the GPU, if you don't know what that is, is the graphics
02:36processor unit. So it can offload a lot of the
02:40graphics, have you looked, and actually talk more about this later, onto the GPU
02:44chip, leaving the CPU chip able to do some other stuff.
02:48That's actually one of the secrets of the smoothness of the IOS platform
02:52is a lot of the GPU offloading
02:56is actually done for you. There's not a lot of
03:00explicit work that you have to do. So that's why
03:04a lot of things scroll so smoothly over IOS is they're all being
03:08rendered and managed over on the GPU side and not the
03:12CPU side. Just like the desktop, we have a SQLite database
03:17which is great for storing your information
03:21in a nice, precise fashion. And then there's some more that we'll get to.
03:25There are some negatives with the Air for Mobile situation.
03:29You do not have access to native widgets.
03:33So if you're going to have a scrolling list, whether it be
03:37you're building this in Flash or with a Flux framework,
03:41you do not have access to the true native
03:45scrolling list. With Flash, you're writing your own
03:49scrolling. You do not have access
03:53to the IOS buttons, the IOS tabs, the Android tabs.
03:57Every UI component you have to build.
04:01I mean, there's other libraries out there, but you do not have
04:05direct access into the phones in a UI. So if
04:09your application needs to look very native, Air for Mobile
04:13is probably not your right choice. You're probably, you don't want
04:17to look at something like native development or something like
04:21possibly Titanium Accelerator, which does expose the native controls.
04:25You are sandboxed
04:29from some other things on the phone. Contacts for one. So if you're
04:33trying to build something that could access into contacts or even
04:37from that go into some SMS, some text messaging capability,
04:41a lot of that is very, very limited. So these are some
04:45real decisions you have to make in choosing your platform
04:49and your technology. Now, if you're doing a game, native widgets
04:53probably not important. Access to contacts, probably not important for a game.
04:57But, you know, if you're doing something else,
05:01that might be something critical. So just suck to be aware of.

Ready to Level Up Your Skills?

Join thousands of learners on 02GEEK and start your journey to becoming a coding expert today!

Enroll Now for Free!