madvertise Android SDK

Intro

The madvertise Android SDK lets you monetize your Android apps via advertising. Basically, the code sends http requests to the madvertise ad server and displays banner ads in various formats. You will receive 100 % of click generated revenues, as we commited in our developer fund.

Preparations

• Install Eclipse
• Install Android SDK and the ADT Eclipse Plugin
• Install Git
• Sign up at madvertise
  • If you don’t have already an account, please sign up.
  • Create an app and copy the token, it will identify the requests send to our ad-server.
  • The Sample SDK comes with its own token. You can use it during development and for testing.

• All code was tested with the latest Eclipse 3.7.1 (Build id: M20110909-1335) and ADT 12.0.0.v201106281929-138431

• The required Android SDK version is 7 (2.1).

Sample App

The SDK comes with a very simple example, how to integrate the SDK in your APP. You can find it at [PROJECT_ROOT]/example/simple/.
Please make sure to add the madvertiseSDK to the build path settings accordingly to your development environment.

For Eclipse with installed ADT Plugin follow these steps.

Using the SDK

For the impatient

• Clone this repository:
  

    $ git clone [email protected]:madvertise/madvertise-android-sdk.git

• Import the SDK project located at [PROJECT_ROOT]/madvertiseSDK/ to your workspace

• Add the SDK to your project build path as described here

• Embed the MadvertiseView as shown in the sample app

• Make sure to add the madvertise_site_token to your AndroidManifest.xml, that you get when creating an app on our plattform.

Step by Step

Once you have installed everything, open Eclipse and import (File | Import | General | Existing Projects into Workspace ...) the Madvertise SDK for Android Project in your Workspace.

With the SDK project created, you can create your app. Create a new Android Project in your workspace from File | New | Project..., using the defaults and populating the require fields.

After your app project is created, you will need to add a reference to the Madvertise SDK for Android Project. Open the properties window for our app (File | Properties), select the Android item from the list, press the Add… button in the Library area and selecting the Madvertise SDK for Android Project created above.

Edit your AndroidManifest.xml file

1. Add internet (required) and location (optional) permissions
2. Add meta data called madvertise_site_token
3. Finally, your manifest file should look something like this

Prepare view configuration

1. Add a ressource file attrs.xml to the res/values folder of your android project
2. Copy the code to the file

Include the view that displays advertising banners

1. Add new namespace mad to your layout xml file
2. Add the MadvertiseView to your layout structure and configure it
3. The layout file should look similiar to this

Contributing

1. Fork it.
2. Create a branch (`git checkout -b my_markup`)
3. Commit your changes (`git commit -am “Added Awesome Feature”`)
4. Push to the branch (`git push origin my_feature`)
5. Create an Issue with a link to your branch
6. Enjoy a refreshing Diet Coke and wait

About

madvertise is a mobile ad network, that enables developers to monetize their apps via advertising. Banners of various sizes can be placed on mobile websites or directly in applications. The latter is usually done with a SDK in form of a compiled library, that sends requests to an ad-server and display the mobile ad. So far, so good.

But apps are different, developers are, and so are the requirements and wishes, that developers have in order to include advertising in their apps. Additionally, it feels kind of strange, to use foreign librarys in your own code, without being able to actually have a look at the sources.

This is why madvertise decided to make all SDKs public as open source projects. We simply could not handle all the (we admit, pretty good) feature requests and suggestions that developers make. Well, we believe nobody can and that’s why we want to share the code with the whole community and enhanced it together. You can adapt the library much more quicker to whatever fits best for you.

Change Log