Skip to main content

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

Popular posts from this blog

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 ...

Using Code Completion

Code completion is an invaluable tool that shows you contextual options for completing the piece of code that you are trying to write. For example, in the editor tab for the MainActivity.js file, locate the line that reads.          setContentView(R.layout.activity_main); Place your cursor after this line and press the Enter Key . On the new line , type the letter R , and then type a period, as shown here:          R. Android Studio Code Completion should display a list of values that you could use to try to complete the code statement. Figure shows what this list might look like . this is important if you are not entirely sure of the spelling of a method call or how to identify the different method signatures. NOTE if the code completion window does not open , press Ctrl + Space to force it to open. This is the same key combination used in some other IDEs for their versions of the code complet...

Now in Android

Android Studio 4.2 discharged to steady channel   Android Studio 4.2 is now available in the stable release channel. Read the blog for detailed information on what’s new, including a new tool to help migrate your project to the latest Android Gradle Plugin version. We’ve also enhanced lots of stuff such as Database Inspector , System Trace , SafeArgs support, Apply Changes, and the new project wizard. As always, download here and file issues here .           Hilt is stable and ready for production Manuel Vivo wrote about the stable release of Hilt , Android Jetpack’s recommended dependency injection (DI) solution for Android apps. Hilt is a simpler, more opinionated way to leverage the power of the Dagger DI library, eliminating boilerplate and reducing errors. It provides direct injection support for popular Jetpack libraries such as ViewModel, WorkManager, Navigation, and Compose. ( DI Basics , Documentation )   Google Play updates ...