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

Publishing an Adobe Air Android Application

It's time for us to review the publishing options for an android application.

Video Transcript

00:00In the last video we created our Air for Android application. It's time for us to package it.
00:06To package it, what I want to do now that I already published it, it's time for us to
00:09go into our file. Well, not published it, but um, tested it. I want to go into my publish settings
00:14and then click into the settings for the Android 3.6. Or on the other hand, I could cancel that
00:21out and go again into my file and click directly into the Air 3.6 for Android settings.
00:27Once I click in that, I'm going to get into the general information of our application. For one,
00:32we could define the name of the APK file, which is the natively accepted file on Android. We could
00:38select the application name. We could call this Hello Android. We could select O2, uh, app ID.
00:46A good way to create an app ID is to start with your domain name. So we could type your com.zero
00:51to geek.hello.air.android. Alright, so we're making sure that it's a unique name. It really,
01:02you could put it in whatever name you want to put into it. This is version number one.
01:06We don't need a version label for it. We could keep, we could define the aspect ratio if we
01:11want it to be portrait, landscape, or have it set automatically. We're going to keep it for portrait.
01:17We could set our application to be full screen. Um, we could automatically orient our application
01:23or not. In this case, we're going to keep the basic configurations. And by the way,
01:27you are more than encouraged to go through and get to know the deep different parameters
01:32because in this intro to the, to the Android, um, air environment, we're not going to go into
01:36every single element and see how they work, but most of them are very intuitively done.
01:41But the most critical part is to go into the development area and where we, because
01:46remember when we said that remember the set password for the session,
01:49every application that we create is going to be automatically associated with the certificate
01:54that we created earlier. So in a couple of videos ago, we created the certificate zero to geek P 12
02:00example. So we don't, if it wasn't there, we could have opened it up again and just placed
02:05our password. Once it's inside, all that's left for us to do is to figure out how do we want to
02:10test our application? Do we want to create an emulator release where we be able to use the
02:15file locally on our computer? Do we want to do a device release? Do we want to do a debug release?
02:22And more over than that, this is where the importance of, um, you know, the air runtime
02:27that we want to work with, do we want to have the embedded version, which is the captivate,
02:31which would basically clump, clump and create a file that would basically, um, be larger than life
02:37really, because it's going to have all the different extensions that are needed for the
02:40Android application to work. Or do we want to put only the files that are of our application
02:45itself and demand the user to have Adobe air on their runtime. And that's a decision
02:50that you need to make. And once, if we do make that decision, then we could then select what
02:54store do we want to go through? Is it through the Google pay a play if the user doesn't have it
02:59or the Amazon app store? In our case, we want to create an embedded air runtime,
03:04basically meaning that captivate, which would also also have the actual build environment or
03:09the air SDK itself that 3.7 or 3.8 that we're working with. I think it was 3.7.
03:15Anyway, so that's all the stuff that we have to look out. Last but not least is we want to go
03:20well critically is we want to define the permissions. Now the permissions themselves
03:25are actually created inside of this XML file that we have here in our low app,
03:29but we don't have to manually go into them. All we have to do is to select what type of
03:34access does our application need? Let's say in our case, all it really needs is internet.
03:39It doesn't need anything else. But if that's the case, then we're just going to enable internet.
03:44Once we set our permissions, we set our general information and our development information,
03:48we really don't have to set much more than that beyond maybe just selling. Maybe we want to make
03:53sure that everyone knows that this is going to be an English application so we can mark and
03:57make sure that people are aware that what languages our application supports currently.
04:02And that's it. And that's all that's left for us. We could always add icons as well,
04:05which we'll look at that in a later video. But what we want to do is just click on that publish
04:10button. Once we click into that publish button, it will start creating our application and
04:14actually publish it out, including bundling in the airtime environment. Meaning our application
04:20is going to be much larger than that 11 K that we saw on our desktop. But actually it's going
04:26to bundle inside of it all of the runtime, which is about nine dot four megabytes or nine
04:31dot three something currently. So the application has been successfully published. And basically
04:36that means that when we go into our application, we'll see that we have our APK, which by the way,
04:40you could already drop that into your phone and be able to run that application. But notice how
04:45the file is nine four megabytes. And that's because we added in our embedded variation as
04:51well at the same time. On the other hand, if we would get the air runtime from Google play,
04:56and in our general information, create, you know, maybe a little Android to and click on
05:01that publish settings, we would then only bundle up our files and a few mandatory elements that
05:07are needed, but nothing more beyond that. So if you look into our application, we'll see that
05:11we'll have a low Android to APK, which is only 41 kilobytes. But when we run this application,
05:19it's going to demand us to have Adobe air is going to tell us, well, you need to have
05:22Adobe air if you want to run this application. Well, if we run this application, it wouldn't
05:27ask us for the Adobe APK, it wouldn't ask us for the Adobe air, excuse me. All right.
05:32So that's it. In the next video, we'll see how could we get this onto our phone.

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!