Giter VIP home page Giter VIP logo

basic-to-advance-android-development-in-java's Introduction

Android Development Basics Repository

Welcome to my Android Development Basics repository! This repository contains the code and resources for various practical exercises and projects related to Android development. These exercises cover fundamental concepts and topics in Android app development using Java.

Table of Contents

  1. Overview
  2. Topics Covered
  3. Folder Structure
  4. How to Use
  5. Contributing

Overview

This repository serves as a collection of practical exercises and projects completed as part of my journey in learning Android development basics. Each folder contains a separate project or exercise focusing on specific topics.

Topics Covered

The exercises and projects in this repository cover a wide range of Android development topics, including but not limited to:

  • User Interface (UI) Development
  • Data Storage and Persistence
  • Networking and Web Services
  • Background Processing
  • Permissions and Security
  • Location and Maps
  • Notifications
  • Sensors and Device Interaction
  • Multimedia
  • Android Jetpack Components
  • Firebase Integration
  • Testing and Debugging
  • App Deployment and Distribution
  • Advanced Topics

Folder Structure

The repository is organized into folders based on the topics covered. Each folder contains a separate project or exercise along with relevant resources and documentation.

Here's the updated folder structure:

  • UI_Development: Projects related to UI development.
  • Data_Storage: Projects related to data storage and persistence.
  • Networking: Projects related to networking and web services.
  • Background_Processing: Projects related to background processing.
  • Permissions_Security: Projects related to permissions and security.
  • Location_and_Maps: Projects related to location-based services and maps.
  • Notifications: Projects related to notifications.
  • Sensors_Device_Interaction: Projects related to sensors and device interaction.
  • Multimedia: Projects related to multimedia (audio, video).
  • Jetpack_Components: Projects related to Android Jetpack components.
  • Firebase_Integration: Projects related to Firebase integration.
  • Testing_Debugging: Projects related to testing and debugging.
  • App_Deployment: Projects related to app deployment and distribution.
  • Advanced_Topics: Projects covering advanced Android development topics.

How to Use

To use the projects and exercises in this repository:

  1. Clone or download the repository to your local machine.
  2. Open the desired project folder in Android Studio.
  3. Review the project structure, source code, and any accompanying documentation.
  4. Run the project on an emulator or physical device to see it in action.
  5. Explore and experiment with the code to deepen your understanding of Android development concepts.

Contributing

Contributions to this repository are welcome! If you'd like to contribute an exercise, project, or improvement, please follow these steps:

  1. Fork the repository.
  2. Create a new branch (git checkout -b feature/your-branch-name).
  3. Make your changes and commit them (git commit -am 'Add new exercise').
  4. Push your changes to your forked repository (git push origin feature/your-branch-name).
  5. Create a new Pull Request.

Topics


Common Coding Programs

Data Structure Coding Programs

  • Sorting

    • BubbleSort
    • InsertionSort
    • SelectionSort
    • QuickSort
    • MergeSort
      • Question: Why is quicksort preferred over merge sort for sorting arrays?
        • Quicksort does not require any extra storage whereas merge sort requires O(n) space allocation. Allocating/de-allocating memory space can increase the run time.
      • Question: Why is merge sort preferred over quicksort for sorting linked lists?
        • There is a difference in linked lists due to memory allocation. In linked lists we can insert items in the middle in O(n) space and time. There is no extra memory allocation required.

  • Searching

    • Binary Search
    • Rotated Binary Search
    • Ternary Search
      • Question: Why is binary search preferred over ternary search?
        • When dividing an array by k ( 2(binary) or 3(ternary)), it reduces the array size to 1/k. But it increases the no of comparisons by k.

  • Runtime Complexity Table:

Android Interview Questions

  • What is Application?

    • The Application class in Android is the base class within an Android app that contains all other components such as activities and services. The Application class, or any subclass of the Application class, is instantiated before any other class when the process for your application/package is created.
  • What is Context?

    • A Context is a handle to the system; it provides services like resolving resources, obtaining access to databases and preferences, and so on. An Android app has activities. Context is like a handle to the environment your application is currently running in.
      Application Context: This context is tied to the lifecycle of an application. The application context can be used where you need a context whose lifecycle is separate from the current context or when you are passing a context beyond the scope of an activity.
      Activity Context: This context is available in an activity. This context is tied to the lifecycle of an activity. The activity context should be used when you are passing the context in the scope of an activity or you need the context whose lifecycle is attached to the current context.
  • What is ABI Management?

    • Different Android handsets use different CPUs, which in turn support different instruction sets. Each combination of CPU and instruction sets has its own Application Binary Interface, or ABI. The ABI defines, with great precision, how an application's machine code is supposed to interact with the system at runtime. You must specify an ABI for each CPU architecture you want your app to work with. You can checkout the full specifcations here
  • Why bytecode cannot be run in Android?

    • Android uses DVM (Dalvik Virtual Machine ) rather using JVM(Java Virtual Machine).
  • What is a BuildType in Gradle? And what can you use it for?

    • Build types define properties that Gradle uses when building and packaging your Android app.
    • A build type defines how a module is built, for example whether ProGuard is run.
    • A product flavor defines what is built, such as which resources are included in the build.
    • Gradle creates a build variant for every possible combination of your project’s product flavors and build types.
  • Explain the build process in Android:

    • First step involves compiling the resources folder (/res) using the aapt (android asset packaging tool) tool. These are compiled to a single class file called R.java. This is a class that just contains constants.
    • Second step involves the java source code being compiled to .class files by javac, and then the class files are converted to Dalvik bytecode by the "dx" tool, which is included in the sdk 'tools'. The output is classes.dex.
    • The final step involves the android apkbuilder which takes all the input and builds the apk (android packaging key) file.
  • What is the Android Application Architecture?

    • Android application architecture has the following components:
      a. Activities - Provides the window in which the app draws its UI
      b. Services − It will perform background functionalities
      c. Intent − It will perform the inter connection between activities and the data passing mechanism
      d. Resource Externalization − strings and graphics
      e. Notification − light,sound,icon,notification,dialog box,and toast
      f. Content Providers − It will share the data between applications
  • What is Manifest file and R.java file in Android?

    • Manifest: Every application must have an AndroidManifest.xml file (with precisely that name) in its root directory. The manifest presents essential information about the application to the Android system, information the system must have before it can run any of the application's code. It contains information of your package, including components of the application such as activities, services, broadcast receivers, content providers etc.
    • R.Java: It is an auto-generated file by aapt (Android Asset Packaging Tool) that contains resource IDs for all the resources of res/ directory.
  • Describe activities

    • Activities are basically containers or windows to the user interface.
  • Lifecycle of an Activity

    • OnCreate(): This is when the view is first created. This is normally where we create views, get data from bundles etc.
    • OnStart(): Called when the activity is becoming visible to the user. Followed by onResume() if the activity comes to the foreground, or onStop() if it becomes hidden.
    • OnResume(): Called when the activity will start interacting with the user. At this point your activity is at the top of the activity stack, with user input going to it.
    • OnPause(): Called as part of the activity lifecycle when an activity is going into the background, but has not (yet) been killed.
    • OnStop(): Called when you are no longer visible to the user.
    • OnDestroy(): Called when the activity is finishing
    • OnRestart(): Called after your activity has been stopped, prior to it being started again
  • What’s the difference between onCreate() and onStart()?

    • The onCreate() method is called once during the Activity lifecycle, either when the application starts, or when the Activity has been destroyed and then recreated, for example during a configuration change.
    • The onStart() method is called whenever the Activity becomes visible to the user, typically after onCreate() or onRestart().
  • Scenario in which only onDestroy is called for an activity without onPause() and onStop()?

    • If finish() is called in the OnCreate method of an activity, the system will invoke onDestroy() method directly.
  • Why would you do the setContentView() in onCreate() of Activity class?

    • As onCreate() of an Activity is called only once, this is the point where most initialization should go. It is inefficient to set the content in onResume() or onStart() (which are called multiple times) as the setContentView() is a heavy operation.
  • onSavedInstanceState() and onRestoreInstanceState() in activity?

    • OnRestoreInstanceState() - When activity is recreated after it was previously destroyed, we can recover the saved state from the Bundle that the system passes to the activity. Both the onCreate() and onRestoreInstanceState() callback methods receive the same Bundle that contains the instance state information. But because the onCreate() method is called whether the system is creating a new instance of your activity or recreating a previous one, you must check whether the state Bundle is null before you attempt to read it. If it is null, then the system is creating a new instance of the activity, instead of restoring a previous one that was destroyed.
    • onSaveInstanceState() - is a method used to store data before pausing the activity.
  • Launch modes in Android?

    • Standard: It creates a new instance of an activity in the task from which it was started. Multiple instances of the activity can be created and multiple instances can be added to the same or different tasks.
      • Example: Suppose there is an activity stack of A -> B -> C. Now if we launch B again with the launch mode as “standard”, the new stack will be A -> B -> C -> B.
    • SingleTop: It is the same as the standard, except if there is a previous instance of the activity that exists in the top of the stack, then it will not create a new instance but rather send the intent to the existing instance of the activity.
      • Example: Suppose there is an activity stack of A -> B. Now if we launch C with the launch mode as “singleTop”, the new stack will be A -> B -> C as usual.
      • Now if there is an activity stack of A -> B -> C. If we launch C again with the launch mode as “singleTop”, the new stack will still be A -> B -> C.
    • SingleTask: A new task will always be created and a new instance will be pushed to the task as the root one. So if the activity is already in the task, the intent will be redirected to onNewIntent() else a new instance will be created. At a time only one instance of activity will exist.
      • Example: Suppose there is an activity stack of A -> B -> C -> D. Now if we launch D with the launch mode as “singleTask”, the new stack will be A -> B -> C -> D as usual.
      • Now if there is an activity stack of A -> B -> C -> D. If we launch activity B again with the launch mode as “singleTask”, the new activity stack will be A -> B. Activities C and D will be destroyed.
    • SingleInstance: Same as single task but the system does not launch any activities in the same task as this activity. If new activities are launched, they are done so in a separate task.
      • Eg: Suppose there is an activity stack of A -> B -> C -> D. If we launch activity B again with the launch mode as “singleTask”, the new activity stack will be:
      • Task1 — A -> B -> C and Task2 — D
  • How does the activity respond when the user rotates the screen?

    • When the screen is rotated, the current instance of activity is destroyed a new instance of the Activity is created in the ne

basic-to-advance-android-development-in-java's People

Contributors

parthvadodariya2005 avatar

Watchers

 avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.