Chris Risner . Com

Sadly, we’ve come to the end of the 31 Days of Android.  If you’ve been paying attention so far, you should be capable of making some fairly sophisticated applications.  Now it’s finally time to take the roast out of the oven and move your apps into the Android Marketplace.  You certainly don’t have to do this.  Due to Android’s loose restrictions on installing new app’s, you could distribute your app yourself or even use one of the competing app stores.  To my knowledge though, the Android Marketplace is the best place to put your applications and the one app store most highly used among Android owners.  There isn’t any sample code today as there isn’t anything you need to add on the code side once your application is ready, though there are some things you may need to change.

Cleaning your Project and Building for Release

The first thing you should do is turn remove any calls to Log as well as turning off debugging.  Debugging can be turned off in your manifest file by either removing the android:debuggable attribute or setting it to false.  Any debug calls to startMethodTracing or stopMethodTracing should also be remove.  Next, make sure that you’re not including any unnecessary files.  These may be class files inside src that you used at one point and aren’t anymore, drawables or layouts in the res folder that aren’t needed, or jars in the lib folder that you’re not including.  If you include them in your release, it will increase the size of your installable unnecessarily.  Lastly, make sure your manifest file only specifies permissions your app actually needs.  Some users are picky about what their apps can do and if you leave in permissions that don’t make sense for your app, you may lose out on installs.  If you are using external resources (i.e. web services, web sites, databases, etc) you may also want to make sure you’re using the correct production resources.

Making a Private Key

In order to send your application to the Marketplace it needs to be signed by a private key.  Furthermore, whenever you want to make updates to your application in the Marketplace, it NEEDS to be signed by the same private key.  If you lose your private key, you lose your ability to update your app.  This is critical to remember.  After you follow the steps below to create a private key, copy it to a usb drive, and put that drive in a safe, inside of a firerpoof safe, in a bank vault. 

keytool is an executable available in the JDK that is used to generate a private key.  On my windows computer, this is located at c:\program files (x86)\Java\jdk1.6.0_25\bin\keytool.exe.   The command to create your key is as follows:

keytool –genkey –v –keystore my-app-release-key.keystore –alias my_alias –keyalg RSA –keysize 2048 –validity 10000

This will generate a key that is 2048 bits and will last for 10,000 days (27 years) using the RSA algorithm.  Once you’ve ran that, you’ll be asked to enter a keystore password.  It is highly advised that you use a strong password here.  You’ll also be asked for your name, organization, department, city, state, and country code.  When that is done, you’ll be prompted to enter a password for the alias.  It’s again advised that you use a strong password here.  If you run this command FROM the JDK directory, you may get an “Access is denied” error.  The solution is to either run it from another directory or put a path in your command to another directory for the .keystore.  Here, I’ve created the keystore in a directory named Java on the C drive:

keytool –genkey –v –keystore c:\Java\my-app-release-key.keystore –alias my_alias –keyalg RSA –keysize 2048 –validity 10000

Building an APK in Eclipse

Now that you’ve generated your key and cleaned your application, you’re ready to produce a signed.  Open your project in Eclipse and right click on the project in the Package Explorer.  Under Android Tools select Export Signed Application Package:

In the next window, the project should already be entered.  Click Next and you’ll then need to browse to the location of your keystore file and enter your keystore password.  Then you need to select the alias you created and enter the password you set for that.  Lastly, you’ll need to enter a Destination APK file.  This won’t require you to put “.apk” at the end of your file but make sure you do:

After a moment the window should close and you should see your .apk file in the directory you chose.   Congrats, you’re done in Eclipse (until your next update).

Creating an Android Market Publisher Account

Before you can add any applications to the Android Marketplace, you need to create a developer profile and pay the registration fee.  The developer profile determines how you appear in the market and allowes you to enter a name, email address, web site, and phone number.  The registration fee is a one time $25.00 fee that is paid using Google Checkout.  When that is done and you’ve agreed to the terms of service, you should be presented with an “Upload Application” button.  Tap that to continue on with the process. 

Uploading and Setting Up your Application

Immediately after hitting “Upload Application” you’ll need to pick and upload the .apk.  This is required as the first step in adding your application.  Once you’ve selected it, you’ll get a summary of the package name, app name, version name and code, as well as the permissions and features listed in the manifest:

Provided you’re happy, hit Save.  Next, you’ll be able to upload assets and specify listing details.  Some of this is required and MUST be added before you can save.  These required things include:  Screenshots, a High Resolution Application Icon, a Title, a Description, a Category, and a Content Rating.  If you’re just trying to get your app into the Marketplace and you don’t care about getting featured or presenting your app as being professional, go ahead and just fill out the info so you can get to the Save point.  If you do desire to have your app be featured and you want people to get to your app in the Marketplace, pay a lot of attention to what you use for images and make sure they are in the correct format.  Furthermore, don’t treat the optional images and promotional video as optional.  Google really looks at these things when deciding what applications to feature.

Saving your Package Name and Publishing

Once you’ve filled out the necessary details you can Save your application.  Once you’ve done that, you now reserve the package name and no one else can use it.  This means that you own that package name (unless Google decides you’ve violated their terms of service and erases you from history).  No one else can use it and only you can update it and you can only update it with APKs signed by the same private key you created earlier (again, its very important that you don’t lose your private key file).  You aren’t required to publish your app right away so if you’re concerned with reserving the package name, fill out this form early on with dummy data and a dummy .apk.  Once you’re happy with everything, you can Publish your app. 

Once you’ve published it will take a few minutes for your app to show up on the Marketplace and a good deal longer for the app to show up when searching for it (I presume it has to propagate to a lot of servers).  In the mean time, you should be able to access your app and send people to it with a URL that looks like this https://market.android.com/details?id=com.package.name.

Updating your Application

Now that you’ve published your application, let’s talk about how to update it.  Once you have a new version of your .apk (make sure you’ve updated the VersionCode and VersionName in your manifest file) and log into the developer portal.  You should see a list of all your applications.  Click on the name of the application you want to upload (it should appear as a hyperlink).  The first page you will see is a Product Details page that has all of the screenshots and app details on it.  At the top of the page are two tabs for Product Details and APK files.  Clicking on APK files will show you the current and active version of your app.  Beneath that should be a button to Upload APK.  After clicking that and uploading, you should now see the new version beneath the active one.  To the right of that there should be a link to Activate your new apk.  Once you’ve uploaded, it’s VERY important that you click the Save button at the top right of the page.  If you don’t, your new apk will not be published.

Congratulations, you’re finally ready to start putting your applications out for people to use.  Good night, and good luck.

We’re getting quite close to the end of the 31 Days of Android so it’s time to talk about how to make some money with your apps.  There are several ways to make money with your applications.  You could just charge for the sale of your app.  Many developers do this and put out a free version with limited features to get users interested in paying for the full version.  Another way to make money is through in-app purchases.  This seems to be more common in games where you can charge users to get special perks or abilities for their in-game character.  Another way to make money, and the focus of today’s article, is in-app advertisements.  One quick note is that you NEED your project to target Android 3.2 or later.  While previous projects targeted 2.2, the sample code today targets 4.0.  You can download the starter code we’ll use today here.

Creating an AdMob Account

For today’s talk we’re going to use AdMob.  AdMob is an advertising network owned by Google.  There is no requirement to use AdMob in Android and there are other alternatives that you could implement yourself.  Step one is to go to www.admob.com and sign up for an account.  If you’re making an account for yourself, you’ll need to put your social security number in (remember the idea is that they’re going to pay you money so they need your info).  If you’re entering it for a business, you’ll have to enter some information specific to your business (i.e. a Tax Identification Number).  After that you can choose to have money put into a bank account or directly into your PayPal account.  Once that is done you have to add a new site / app.  Here you can choose between an Android App, iPad App, iPhone App, Smartphone Web, or a Windows Phone 7 App (this supports more than just Android).  Choose Android App and then you’ll need to enter your app’s name and package.  Once you’ve created your app, you should be taken to a page that lists your Publisher ID as well as give you a link to the Publisher Code.  Download the code and keep track of the Publisher ID as you’ll need it later. 

Adding the AddMob Library to your Project

Typically with any third party libraries, I will drop them into a Libs folder in my project’s directory prior to adding it to the project.  After you do that, right click on your project in Eclipse and go to Properties.  Choose the Java Build Path section from the left of the window and then the Libraries tab from the top of the window.  Choose Add JARs, expand DayThirty/libs and choose GoogleAdMobAdsSDK-#.#.#.jar.  When your done the properties window should look like this:

Manifest File Changes

There are a few different manifest file changes you need to make.  First you need to add permissions for INTERNET and ACCESS_NETWORK_STATE:

<uses-permission android:name="android.permission.INTERNET"/>

<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>

These are necessary because you’re displaying ads that the device has to fetch from the internet.  Second, you need to add a new Activity into the xml with the other activities:

<activity android:name="com.google.ads.AdActivity"

android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize"/>

If you try to run your application without putting this in your manifest, your ad will actually say:

You must have AdActivity declared in AndroidManifest.xml with configChanges.

Adding the Publisher ID

You don’t have to have your Publisher ID in your strings resource file but’s not a bad idea to put it there.  Open your res/values/strings.xml and add “admob_id” in with the Publisher ID you got from the AdMob website:

<string name="admob_id">a14eef56ac6acfb </string>

Adding an Ad to your Layout

Now you can open your res/layout/main.xml layout to add an AD in.  Go ahead and drop a com.google.ads.AdView element in above the TextView at the top:

<com.google.ads.AdView

xmlns:googleads="http://schemas.android.com/apk/lib/com.google.ads"

android:id="@+id/ad"

android:layout_width="fill_parent"

android:layout_height="wrap_content"

googleads:adSize="BANNER"

googleads:adUnitId="@string/admob_id" />

Here you’re using the admob_id you put in your strings file just a moment ago.  The last step you need to take is to load an AdRequest into your AdView.

Loading the AdView with Ads and Using Test Mode

Open the src/com.daythirty/DayThirtyActivity.java class and go to the bottom of the onCreate method.  You need to do two things here:  load the ads and add your device and emulator to test mode.  While in development, it’s important that you add your devices and emulator to test mode so that you aren’t affecting your impressions inappropriately.  Thankfully this is done very easy.  For each device you just need to get it’s serial number which can be pulled from DDMS or from the device selection screen when running your app.  When you’re done, your code should look like this:

AdRequest request = new AdRequest();

request.addTestDevice(AdRequest.TEST_EMULATOR);

request.addTestDevice("015ED03511005018");

AdView ad = (AdView) findViewById(R.id.ad);

ad.loadAd(request);

Here I’ve added my device’s serial number as a test device as well as the emulator.  Then the same request is used to load the ads into your AdView.  Now when you run your app, you should see an ad at the top (it may take a couple minutes to show up when you run for the first time):

Note that when your app first loads the Ad won’t be loaded yet and the TextView will be all the way at the top of the screen.  Once the Ad loads, the rest of your UI elements will be pushed down.  It’s worth keeping this in mind when you decide on the placement of your Ads.

Different AD Sizes

In the AD you’ve put into your project, you’ve set the size to be BANNER.  This Ad size is 320 x 50.  In portrait mode, the Ad should stretch across the screen.  However, if you rotate to landscape, the Ad will be centered and only take up part of the screen:

There are other Ad sizes which are banner specific.  IAB_MRECT is a medium rectangle and is sized at 300 x 250.  IAB_BANNER is a full size banner and is 468 x 60.  IAB_LEADERBOARD is 728 x 90.

Passing Targeted Information to Ads

As you might imagine, there is a lot of information that could be used to deliver more targeted Ads to your users.  This is done using several methods on the AdRequest object.  This is a list of the current methods:

• setBirthday - Set the user's birthday.
• setGender - Specifies if the user is male or female.
• setLocation - Specify the user's current location
• setKeywords - Pass in keywords for specific ads (like "Technology")
• setExtras - I'm not really sure.
• setPlusOneOptOut - Has something to do with plus oneing things.

As noted, I’m not exactly sure what the last two methods are used for but the rest of these methods should enable you to present some pretty targeted Ads to your users.  Do think about user privacy before you try to implement any of these.  Some users are ok with this sort of information being passed around and others are very not ok with it.

Using what you’ve learned today, you should be able to put Ads in your applications and put them in the right place so they will look good.  You can download the final code from today here.