Kotlin Tutorial

https://www.journaldev.com/19467/kotlin-let-run-also-apply-with

MVVM stands for Model View ViewModel and it is a design pattern that is used to build 
softwares. MVVM helps us to separate the Business Logic of our Application from the Views or UI.

Model : This is responsible for handling the data in the application. Model cannot directly interact with Views, but it interacts with ViewModels and then Views with the help of observables. (Sounds confusing right? Don’t worry in the course we will cover every step in detail).

View: This is the User Interface of our Application. It should not contain any application logic.

ViewModel: It is basically a link between Model and View.The ViewModel class is designed to store and manage UI-related data in a lifecycle conscious way. The ViewModel class allows data to survive configuration changes such as screen rotations. 
Architecture Components provides ViewModel helper class for the UI controller that is responsible for preparing data for the UI. ViewModel objects are automatically retained during configuration changes so that data they hold is immediately available to the next activity or fragment instance. For example, if you need to display a list of users in your app, make sure to assign responsibility to acquire and keep the list of users to a ViewModel, instead of an activity or fragment.

LifeCylerOwener and LifeCylerobserver

Advantages of using MVVM

Now let’s talk about what are the advantages of using MVVM in your android project.

• If you use MVVM it will help you structuring your code in a nice way so that it is easy to understand for a new developer.
• Using MVVM makes your project maintainable as everything is well organized and making changes are very easy.
• Testability is easy with MVVM because all modules are independent and testable.
• MVVM enhances the re-usability of the code.

     

       Coroutines

https://proandroiddev.com/how-to-make-sense-of-kotlin-coroutines-b666c7151b93

Flutter important links

For TextFields -https://medium.com/flutter-community/a-deep-dive-into-flutter-textfields-f0e676aaab7a

Awesom Libs= https://github.com/Solido/awesome-flutter

Basic Layout= https://medium.com/flutter-community/flutter-layout-cheat-sheet-5363348d037e

Lear Dart Slider= https://docs.google.com/presentation/d/1ARs-PljHk_p7iKkx65kfo_JF4NychABLiZHOQMCa1yw/edit#slide=id.g41d6fa5cab_1_77

Basic Question

What is Inent

An Intent is basically a message to say you did or want something to happen. Depending on the intent, apps or the OS might be listening for it and will react accordingly.

Intents are a way of telling to Android what you want to do. In other words, you describe your intention. Intents can be used to signal to the Android system that a certain event has occurred. Other components in Android can register to this event via an intent filter.

Following are 2 types of intents

1.Explicit Intents

used to call a specific component. When you know which component you want to launch and you do not want to give the user free control over which component to use. For example, you have an application that has 2 activities. Activity A and activity B. You want to launch activity B from activity A. In this case you define an explicit intent targeting activityB and then use it to directly call it.

2.Implicit Intents

used when you have an idea of what you want to do, but you do not know which component should be launched. Or if you want to give the user an option to choose between a list of components to use. If these Intents are send to the Android system it searches for all components which are registered for the specific action and the data type. If only one component is found, Android starts the component directly. For example, you have an application that uses the camera to take photos. One of the features of your application is that you give the user the possibility to send the photos he has taken. You do not know what kind of application the user has that can send photos, and you also want to give the user an option to choose which external application to use if he has more than one. In this case you would not use an explicit intent. Instead you should use an implicit intent that has its action set to ACTION_SEND and its data extra set to the URI of the photo.

Explicit Android Intent is the Intent in which you explicitly define the component that needs to be called by Android System.

 Intent MoveToNext = new Intent (getApplicationContext(), SecondActivity.class);

Implicit Android Intent

Implicit Android Intents is the intent where instead of defining the exact components, you define the action you want to perform.

                              Fragment

A Fragment represents a behavior or a portion of user interface in an Activity. You can combine multiple fragments in a single activity to build a multi-pane UI and reuse a fragment in multiple activities. You can think of a fragment as a modular section of an activity, which has its own lifecycle, receives its own input events, and which you can add or remove while the activity is running (sort of like a "sub activity" that you can reuse in different activities).

Service

A Service is an application component that can perform long-running operations in the background, and it does not provide a user interface. Another application component can start a service, and it continues to run in the background even if the user switches to another application. Additionally, a component can bind to a service to interact with it and even perform interprocess communication (IPC). For example, a service can handle network transactions, play music, perform file I/O, or interact with a content provider, all from the background.

These are the three different types of services:

Foreground

A foreground service performs some operation that is noticeable to the user. For example, an audio app would use a foreground service to play an audio track. Foreground services must display a status bar icon. Foreground services continue running even when the user isn't interacting with the app.

Background

A background service performs an operation that isn't directly noticed by the user. For example, if an app used a service to compact its storage, that would usually be a background service.