Newer Post

How X-Teamers Unleashed Their Potential in 2015

Older Post

10 Habits of Every Successful Remote Worker

How To Get Started With Android Programming

Android programming has undergone many changes over the years, both in tooling we use and features available on the platform. Today, typical development environment and applications we are able to create are anything like they used to be. Long gone is Eclipse IDE replaced by Android Studio, virtual device emulators are getting faster and more feature rich, and lastly, the amount of knowledge sources and third-party helper libraries is finally at point where you can easily pick up Android development basics in few hours of work.

This tutorial will teach you how to setup and run Android project using Android Studio on OS X (Windows and Linux is not much different). It will be a starter project for all other tutorials. Basic concepts of Android and its development process will not be explained in every following tutorial, so please refer to this post as needed.


Android programming is primarily done in Java 1.6 programming language -- at least intermediate knowledge is necessary to fully understand concepts specific to Android that will be introduced throughout the tutorials.

Development tools and code libraries are ever-changing and no tutorial post can stay up-to-date with that. Every library version that our project depends on will be provided here -- in case of any trouble, please set your dependencies to exact versions as listed in tutorial, to prevent any breaking changes in never versions.

What you'll need:

At the time of writing, Android Studio 2.0 is available in Preview Version and current stable version is 1.5.1.

Please consult above links for installation instructions specific to your operating system. Java is needed to run Android Studio and compile Android source code (Open JDK is also fine). Nowadays Android Studio comes bundled with everything you need, which is IDE itself, Android SDK, build tools and emulator system images.

1. Setup Android Studio

If you have fresh installation of Android Studio, you need to perform a little setup. Thankfully, new versions of AS guide you through the whole process and default values are sane and useful.

Import previous settings

In case you have previous version of AS already installed, you can choose to import settings. Following section assumes, you don't.

If you had Android SDK already installed on your machine, you should see this information:

It does what it says, follow the instructions to repair or update your current SDK files.

Configure Android Studio

Let's review and change some of the default settings, choosing the Custom Install Type option.

In the next step, you should choose Darcula theme, which is modern and easier on the eyes than the default one. All tutorial screenshots will be created using this theme.

Download SDK, Android platform and Virtual Device files

The following components are essential to your development process:

  • Android SDK -- base Software Development Kit, meaning custom API libraries that interact with Android devices on application's behalf1
  • Android Platform -- Android operating system in a specific version (23 in the screenshot) that allows you to run applications compiled using SDK and have access to features introduced in that version
  • Android Virtual Device -- also called an emulator -- piece of software that emulates real hardware with Android installed operating system. This allows you to run and test your applications without having physical device

Notice that in our example, setup wizard is going to download only necessary components, because some are already available on the machine.

Emulator needs to know how many memory it can allocate, the rule of thumb is more memory is better than less so we'll pick 4GB, but 2GB or less is also fine.

Review screen allows you to have final look at install settings.

After finishing, the installation begins. You can see what particular packages are being downloaded.

2. Create new project

Welcome screen shows current software version (AS 1.5.1 in the example) and few basic options to get you started. Click the highlighted option in order to create new project. Recent project list is empty, because we have no other projects.

As you can see, in addition to creating new project, you can open and import an existing one, check out from version control, and import Android code sample.

In New Project window fill out the input boxes as you wish. Example application's name is Playground. Android projects follow Java convention and keep source code organized within packages. Main package canonical name for our application is io.github.adamjodlowski.playground and this value is extremely important for various reasons. Three of them would be:

  • application main package name distinguishes it from other applications on Google Play Store
  • it's associated with your application that lives alongside others on Android device, allows for efficient and secure communication between your own application components and external ones -- for instance, for purpose of exchanging data between them
  • is necessary to properly configure your application via Android Manifest which we'll come back to later on

Because of Android's design and flexible configuration possibilities, it's present on wide range of form factors and manufacturer brands. Let's leave this option default, choosing Phone and Tablet variant with Minimum SDK set to 15. Because of this decision, our application will be compatible with every Android device operating operating system in version 4.0.3 (Ice Cream Sandwitch) and later. This is reasonable decision these days, as you can see, we are given additional rationale coming from IDE and Google Play Store.

Android is being constantly developed. New platform versions (SDK from programmer's perspective) are being published, in order to fix bugs and provide additional functionalities. New devices come with current platforms, older ones are updated or stay as they were. To give an example, let's say you build your application with minimum SDK equal to 15 and have two devices with platform 23 and older one with platform 8:

  • we need to use only2 features available up to platform 15, because this is the minimum our app is said to be compliant with
  • application can be installed on device with platform version 23, but there are many features added along the way which we can't use, because we need to provide compatibility with all platforms from 15 to 23
  • application can not be installed on platform 8, because it's lower than the minimum -- API features added later are missing from the device

Feel free to lower the minimum SDK version if you're certain it's necessary for your project.

Android is backward compatible, so applications written for older platforms will work on newer ones, but default behaviors might change and affect our apps.

In this step we're going to pick Empty Activity, so the generated code is less complicated. As a matter of fact, you can add custom components at every point during development so these mini creators are really for getting to know basic types of navigation and application structure or really simple projects.

You can think of an Activity as a main building block of an application, representing one window of User Interface. Having at least one Activity in an application is not necessary, but this is almost always the case. This screen allows you to customize first (and only, for now) Activity and you can already see conventions used in Android:

  • Activities are named as such: MyNameActivity
  • layouts corresponding to activities are named: activity_MyName

Layout is an .xml file representing visual components in declarative style, most often corresponding to one Activity which contains the activity screen's application logic, in imperative code (.java file).

If everything went okay, you should now see the main Android Studio view with your main activity source file opened.

Android Studio is built on top of IntelliJ IDEA, if you're already familiar with that tool, you should feel at home.

If your IDE doesn't look similar to what's in the screenshots or if you accidentally closed important window, reset to default settings by clicking Window > Restore Default Layout in main menu bar at the top.

Switch to activity_main.xml file by clicking on the top bar with current files.

What you see by default is layout visual editor, denoted by Design bottom tab. This is how your Activity is going to look like on this particular emulated device, in this case Nexus 4 with platform 23 in portrait mode. Next to it at the bottom there is a tab Text, select it.

You should see XML representation of the same layout, in form of an activity_main.xml file. If you're not familiar with XML, you can refer to Wikipedia. Layout files consist of actual Layouts (they coordinate alignment and positions of their children) and Widgets (basic visual building blocks -- button, labels, etc.).

Edit highlighted text in TextView node, android:text property to Android Studio base project. Hopefully you can already see changes being done on the fly to preview on the right.

It looks like AS has some tips for us regarding the highlighted line of XML, hover over it and click more... next to warning message to expand it. It says we should not hardcode strings in source code, which is another convention and good practice for various reasons. Click on the yellow lightbulb on the left of problematic line and choose extract string resource.

This quick fix is one of many available in AS. Pay close attention to warnings such as that -- they can range from not optimal syntax structures to bad design choices impacting application performance. XML files are not validated like Java code by compiler, so the vast majority of work is done by lint rules defined for Android projects.

Give a meaningful name to a resource being extracted. Entry will be created in file strings.xml vital to every Android application.

Command-click (on OS X, or control-click on Windows & Linux) on @string/header which we have just extracted, or open file strings.xml from Project Explorer on the left (it's located in /app/src/main/res/values/).

What you see is one of many resource files which contains string resources. Every resource has a type (string), name (header) and value (Android Studio base project). You can open other resource files, colors.xml and styles.xml to see what they look like.

Android Studio contains a lot of useful tools, wizards and contextual editors. Entering strings.xml file gives you the option to go straight to Translations Editor that is helpful for working with translations. This is one of many examples of making programmer's life easier.

3. Edit source code

So far we've changed one TextView's text. Let's add interactive component in form of a button to our application.

Switch to activity_main.xml file and go to visual Design tab.

From the Palette section, drag and drop Button widget onto layout preview.

You've added Button View to Main Activity's layout. From the Properties section on right hand side you can directly edit all properties available to selected View. Above that there's Component Tree which shows view hierarchy and highlights where you currently are. This is a powerful visual tool, in case you prefer raw XML editing, you can still do that by switching to Text tab.

Switch to XML view, it should look similar to this:

<?xml version="1.0" encoding="utf-8"?>  
<RelativeLayout xmlns:android=""  

        android:id="@+id/textView" />

        android:text="New Button"
        android:layout_marginTop="42dp" />


We'll focus on newly added <Button> XML node. It says that there is a button widget defined with following properties, from top to bottom:

  • width and height should be just enough to fit content (in case of a Button -- its text and padding, if applicable)
  • text displayed by the button
  • crucial property id is set to button (we'll need it in a moment)
  • it should be positioned below another component in the layout with id equal to textView
  • should be aligned to it's parent left and start
  • should have top margin of 42 dp3

Those two widgets are wrapped in Relative Layout, most flexible layout used in Android. It lays out its widgets on screen based on defined properties and constraints (alignments, paddings, margins, dimensions...).

android:id="@+id/button" reads: property id from namespace android has value @+id/button which itself is a resource property (@) of type id (id) with value button. Plus sign + is applicable to id resources and means that if this particular value is not defined already, it should be added to known identifiers.

Switch to and make the onCreate method look like in the listing below. Don't forget to import needed classes and pay close attention to any warnings that might appear while you type:

package io.github.adamjodlowski.playground;

import android.os.Bundle;  
import android.view.View;  
import android.widget.Button;  
import android.widget.TextView;

public class MainActivity extends AppCompatActivity {

    TextView textView;

    protected void onCreate(Bundle savedInstanceState) {

        textView = (TextView) findViewById(;

        Button button = (Button) findViewById(;
        button.setOnClickListener(new View.OnClickListener() {
            public void onClick(View v) {
                textView.setText("It works!");

What this code does, from top to bottom:

  • imports necessary classes, you should be able to guess what some of them are
  • declares MainActivity class extending AppCompatActivity -- you'll see this often -- in order to get access to Android framework and reach outside sandbox that our application lives in, we need to extend or obtain instances of framework classes (AppCompat prefix says it comes from Support Library, backporting some of the features to older platforms)
  • declares textView field of the type TextView
  • overrides onCreate method, which is most often used to perform activity initialization
  • setContentView method takes identifier of activity's layout file in form of autogenerated layout resource identifier (it corresponds to the actual file named activity_main.xml) -- this layout will be inflated to represent visual interface of the activity
  • textView field is set to contain what is returned from findViewById method -- see what actual type is returned from that method and think why the typecasting is needed here4
  • handle to Button object is obtained and click listener is set -- it will set text on the TextView when clicked

Now you see what we need id values for -- every framework component (visual widget, resource file, etc.) needs to have an ID in order to reference it by other component.

Notice the use of anonymous inner class of type View.OnClickListener, this approach is ubiquitous in Android programming.

4. Run the application on emulator

Click the green play icon or choose Run > Run 'app' option form the main menu. You'll see chooser dialog which allows us to pick specific emulator or physical device to run our application on.

Select Launch emulator option if you don't already have one running. You should have the default Nexus 5 API 23 x86 or similar already installed. If not, click the three dot button above the OK button to go the Android Virtual Device Manager. Click on Create Virtual Device, pick any hardware profile you like.

You should always test your application on few different platform versions, form factors, language settings etc. Emulators allow us to do that at no cost of buying physical devices.

Select System Image, going with default is fine.

Last screen allows for further customization, defaults are okay.

Create AVD and rerun application choosing desired emulator from dialog. New window should appear and after quick moment of initialization, you should see emulator window.

If you don't see your application, run it again so it pops up in the foreground. In case there are any problems with building or running, you'll se warnings or errors in Android Studio bottom section.

Green popup tells us the application has been successfully installed and launched on emulator. Entire bottom section is an Android Monitor with active tab Logcat which is Android console logger window. Look for any potential problems there.

Click on the NEW BUTTON button, the text above should change to "It works!". If it does, congratulations on your first working Android Application.

5. Android Manifest & build.gradle

How is this all possible? How does Android operating system know it should run your MainActivity when you open the app? Look for a file AndroidManifest.xml in /app/src/main/ directory. It is the main Android configuration file, it should look like this:

<?xml version="1.0" encoding="utf-8"?>  
<manifest xmlns:android=""  

        <activity android:name=".MainActivity">
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />


Here we declare all main building blocks of Android applications, such as Activities. You can have as many Activities in .java files in your project as you like, but as long as you don't declare them here, they won't be usable. Example file says, that:

  • main application package is io.github.adamjodlowski.playground
  • application has one activity
  • Java class for that activity containing application logic is [io.github.adamjodlowski.playground].MainActivity[.java]
  • <intent-filter> section says, that this activity should be entry point to the entire application and should be accessible through system application launcher

Second configuration file responsible for build process and managing third party dependencies is /app/build.gradle:

apply plugin: ''

android {  
    compileSdkVersion 23
    buildToolsVersion "23.0.2"

    defaultConfig {
        applicationId "io.github.adamjodlowski.playground"
        minSdkVersion 15
        targetSdkVersion 23
        versionCode 1
        versionName "1.0"
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), ''

dependencies {  
    compile fileTree(dir: 'libs', include: ['*.jar'])
    testCompile 'junit:junit:4.12'
    compile ''

Hopefully you can guess what those properties are. One thing we didn't mention is targetSdkVersion 23 which means, that although minSdkVersion is equal to 15, new platforms running our application should not try to backport default behaviors to level 15. Instead they should provide behaviors defined for level 23, for example default visual styles of built-in system widgets (buttons, alert dialogs, etc.).

Dependencies section contains third party libraries built using Gradle Build System, you'll need to add every custom library that your app depends on there. Our MainActivity extends AppCompatActivity is possible, because we include AppCompat library in our dependencies.


In this tutorial you learned how to configure fresh installation of Android Studio, setup example project, configure and run emulator, make changes to source code and successfully run your application on Android emulator.

Source code for this tutorial can be found on GitHub.

by Adam Jodłowski

  1. Android applications are sandboxed and usually don't interact directly with underlying operating system or hardware.

  2. This is not true anymore, thanks to Support Library and feature backporting. But it is a default case if we don't use those additional tools.

  3. dp stands for Density Independent Pixels and is the default and only correct way of defining margins, sizes, etc. in Android. You can think of it as pixels relative to density of particular physical display which may vary.

  4. findViewById returns View which is superclass to TextView, Button, etc. We need to operate on more concrete type so we perform the typecasting.

We'll help you unleash.

Join the 20,000 developers who subscribe to our newsletter.

Scale your
Development team

We help you execute projects by providing trusted developers who can join your team and immediately start delivering high-quality code.

Hire Developers
code, android