Launching Your First Android Application

With all tools and the SDK downloaded and installed , it is now time to start your engine.As in most programming blog, the first example uses the ubiquitous Hello World application. This will give you a detailed look at various components that make up an Android project. This is also the easiest Android project you will ever make.

Believe it or not , the Hello Wold Application is already finished. By default , when you create a new application in Android Studio , it creates a Hello World application. Let's launch this application and , in the process , also launch the Android emulator to see how everything works.

1. Select Run -> Run app from the Android Studio menu bar. You should see the Select Deployment Target dialog as shown.

2. Select the Nexus 5X API 25 ( feel free to select the Nexus 5x API 25 , which is the Jelly Bean emulator that you created in the Try It Out for the last section),and click Next.

NOTE :- note that if there's ever a time when you have not already created the emulator, you can create an emulator at this point.

3. It can up to five minutes , and sometimes longer(depending on the hardware specs of your desktop) for the emulator to start and fully load. During this time (the first time you launch the emulator) the application might time out. If a message pops up in Android Studio telling you that application timed out waiting for the ADB(Android Debugging Bridge) to start , or another similar message , just wait for the emulator to fully load , and then once again select Run -> Run app from the Android Studio bar.

With the emulator fully loaded and started , Android Studio can install your Hello World application. The application will display as shown

This was a very example for how to create and launch your first Android applications. However, what this example has really done for is introduce you, on a general scale , to most of the major skills you will fine tune throughout this blog.

Comments

Creating Android Virtual Devices (AVDs)

The next step is to create an Android Virtual Device (AVD) you can use for testing your Android application. An AVD is an emulator instance that enables you to model an actual device. Each AVD consists of a hardware profile ; a mapping to a system image ; and emulated storage,such as a secure digital (SD) card.One important thing to remember about emulators is that they are not perfect. There are some applications , such as games (which are GPU heavy ) or application that use sensors such as the GPS or accelerometer. Theses types of application cannot be simulated with the same speed or consistency within an emulator as they can when running on an actual device. However , the emulator is good for doing some generalized testing of your applications. You can create as many AVDs as you want to test your applications with different configurations. This testing is important to confirm the behavior of you application when it is run on different devices with varying capabilities. Use ...

Applying Styles and Themes to an Activity

By default , an activity is themed to the default Android theme. However , there been a push in recent year to adopt a new theme known as Material . The Material theme has a much more modern and clean look to it. There are two versions of the Material theme available to Android developers : Material Light and Material Dark , Either of these themes can be applied from the AndroidManifest.xml To apply one of the Material themes to an activity , simply modify the <Application> element in the AndroidManifest.xml file by changing the default android:theme attribute. (Please be sure to change all instances of "com.android" to whatever package name your project is using.) <?xml version="1.0" encoding="utf-8"?> <manifest xmls:android="http://schemas.android.com/apk/res/android" xmlns:tools="http://schemas.android.com/tools" package="com.android.activity101"> <application ...

Debugging Your Application

After you have built an application , you need to be able to debug it and see what is going on inside your code . One of the handiest ways to be able to see inside your code it through the use of break points. Breakpoints allow you to pause the execution of your code at specific location and see what is going on (or what is going wrong). Let's take a look at how to use breakpoints in Android Studio. Setting Breakpoints Breakpoints are mechanism by which you can tell Android Studio to temporarily pause execution of your code , which allows you to examine the condition of your application . This means that you can check on the values of variables in your application while you are debugging it. Also , you can check whether certain lines of code are being executed as expected - or at all. To tell Android Studio that you want to examine a specific line of code during debugging , you must set breakpoint at the line. Click the margin of the editor tab next to line of code you want...

Android

Search This Blog