android tutorials

Android Fragment is a part of an activity that represents multiple screens inside a single activity. There may be many fragments inside an activity. Android fragment is affected by an activity lifecycle as it resides under an activity. The fragment is a sub-activity.  The fragment includes some important things. Such as;  It contains its layout and it has self behaviour with its own lifecycle. It is useful for multiple activities. While running activity, it can add or remove any of the fragments.  It includes different fragments in a single activity.  Furthermore, a Fragment lifecycle is added to its host activity lifecycle. While the activity stops, all remaining fragments will stop working.  To more information visit: android app development course . Understanding Fragments Fragments are a combination of an XML layout file and a Java class such as Activity. The fragments use a support library to support back all the Android versions. These are easy to reuse in activities as they incl

It is unlikely that you need to install Android SDK. That's why the name-Software Development Kit is right. It's designed for people who write Android apps and need support from a computer to work with Android. But those tools can also be useful for folks who want to do some more advanced things. Stuff like installing software manually, or rooting your phone. Fastboot and ADB are essential to the Android program if you're into hacking. Moreover, Google offers this to anyone free of charge. To more information visit: android development course Software development kit SDK stands for Software Development Kit, a collection of required software tools. SDK essentially helps Android update tools and recent Android updates. Every time a new version of Android is released, a corresponding SDK is released along with it. The developers will add this SDK to the computers. What is an SDK manager? A Software Development Kit is a set of tools available for Android app develop

In this lesson, we will discuss Android App Project Package Structure (Android Studio) Here, in this tutorial we'll discuss about the project structure of an Android Application. Earlier a lot of Android Applications were developed on Eclipse IDE, but now-a-days one can only develop an Android Application using Android Studio, else Google will not allow the application to be made public or even reject the application from Google Play Store. For those who have apps which were developed using Eclipse and now plan to shift the code to Android Studio, this lesson will help you to understand the structure of both the developments tools. First we will understand the project structure of Eclipse IDE(If you are a beginner, you can skip this part). For that we will assume that you have a basic "Hello World!" Android Application created in Eclipse IDE. Both Eclipse and Android Studio require same steps to create an Application Project, only minor differences are there. To learn and

You have already studied about what Spinners are and how they work. So let's checkout an example and learn how we can implement it in our Android App. For spinners concept visit: spinners in android In this tutorial, we are going to create an application that works with two Spinners, which are inder-dependent. The main layout of the application will contain our  one TextView  and  two spinners  as its child component views. So we need to customize the layout(shown in below image) where one Spinner is placed below the TextView and the other spinner is below the first spinner. As the options inside the second Spinner will depend on what we select in the first Spinner, hence initially the second spinner will be hidden and it will only appear when user has selected one option from the first spinner. The second spinner has the property  isVisible  equals to  GONE , which means it exists in the layout but it will not be visible(or it will be hidden). Hence, in the image below, it looks l