project_number

project_id

storage_bucket

mobilesdk_app_id

package_name

Make sure "com.example.educative.hello" is the package name while registering the project

oauth_client_id

current_key

services_client_id

Gain insights into creating efficient Android apps. Learn about layouts, UI components, lifecycle management, and Firebase integration. Delve into practical coding challenges and quizzes to solidify your skills.

educative-android.tar.gz

Android

This course covers various aspects of building Android applications, focusing on creating robust and efficient apps. The course is divided into several modules, accompanied by quizzes and coding challenges that will test your understanding of the course.

You’ll start with an overview, which introduces the Android platform and its key features. Then, you will learn the various Android layouts and UI components—how to create and use different layouts, fragments, and custom views. Moreover, you’ll practically learn about activity and lifecycle management, and how to handle images and work with RecyclerViews.

Next, the course covers Android UI components such as bottom navigation bars, alert dialogs, and web views. You’ll learn about intents, notifications, threading, services, app permissions, user location, and Firebase services—including authentication, real-time databases, storage, and cloud messaging.

By the end of the course, you will be able to create functional and well-performing Android applications.

Android Development Masterclass

Accessing a user’s call history, messages, location, camera, microphone, and so on is categorized as dangerous permissions. If our application requires any dangerous permissions, adding them to the `AndroidManifest.xml` file isn’t sufficient. We need to explicitly ask for the user’s consent to use the permission.

Let’s learn about the workflow for requesting and using runtime permissions.


## Runtime permissions workflow

As a best practice, we should request runtime permissions just before performing a restricted action. It's not advisable to request permissions in advance. For example, let's assume our application requires external storage access for saving images. It would be a bad user experience to request external storage permission as soon as the app starts up. We should request these permissions when we actually need to save an image. The flowchart below shows the workflow for requesting runtime permissions. 

# Runtime permissions workflow

As a best practice, we should request runtime permissions just before performing a restricted action. It's not advisable to request permissions in advance. For example, let's assume our application requires external storage access for saving images. It would be a bad user experience to request external storage permission as soon as the app starts up. We should request these permissions when we actually need to save an image. The flowchart below shows the workflow for requesting runtime permissions. 

Learn how to request runtime permissions for performing restricted actions in Android.

Overview

Android Layouts and UI Components

Android UI Components

Intents, Notifications, Threading & Services

App Permissions & User Location

Utilizing Firebase Services in Android

Assessment 1: Android Core Concepts

Lifecycle Aware Components

Android Jetpack Components

Data Persistence

Assessment 2: Jetpack Components and Persistence

Networking

Dependency Injection

Performance & Optimization

Android App Testing

Assessment 3: Networking, Performance, and Testing

Conclusion

Appendix

Workflow for Requesting Runtime Permissions

Runtime permissions workflow