Android

Today we worked on Location Manager and Notification Manager and linked the two to create a mini application that would show you the notification of your current location after you shake your phone (using sensors). This class provides access to the system location services. These services allow applications to obtain periodic updates of the device's geographical location, or to fire an application-specified  Intent  when the device enters the proximity of a given geographical location.

Today we worked with graphics and images and learned about drawable .When you need to display static images in your app, you can use the  drawable  class and its sub classes to draw shapes and images. A  drawable  is a general abstraction for  something that can be drawn . The various subclasses help with specific image scenarios, and you can extend them to define your own drawable objects that behave in unique ways.

Today we worked on firebase applications and also learnt how to push code in GitHub repository and save it for future use. Firebase  is a mobile platform that helps you quickly develop high-quality apps, grow your user base, and earn more money. Firebase is made up of complementary features that you can mix-and-match to fit your needs, with  Google Analytics for Firebase  at the core. You can explore and integrate Firebase services in your app directly from Android Studio using the  Assistant  window.

Today we practiced firebase by implementing it in various dummy applications. Firebase  is a mobile platform that helps you quickly develop high-quality apps, grow your user base, and earn more money. Firebase is made up of complementary features that you can mix-and-match to fit your needs, with  Google Analytics for Firebase  at the core. You can explore and integrate Firebase services in your app directly from Android Studio using the  Assistant  window   

Today we learnt about Firebase. Firebase is a mobile platform that helps you quickly develop high-quality apps, grow your user base, and earn more money. Firebase is made up of complementary features that you can mix-and-match to fit your needs, with  Google Analytics for Firebase  at the core. You can explore and integrate Firebase services in your app directly from Android Studio using the  Assistant  window. First make sure you have installed Google Repository version 26 or higher, using the following steps: Click  Tools > SDK Manager . Click the  SDK Tools  tab. Check the  Google Repository checkbox, and click  OK . Click  OK  to install. Click  Background  to complete the installation in the background, or wait for the installation to complete and click  Finish . You can now open and use the  Assistant  window in Android Studio by following these steps: Click  Tools > Fire...

Worked on UI , dealt with complexity of layouts and worked user friendly approach. The user interface for an Android app is built using a hierarchy of  layouts  ( ViewGroup  objects) and  widgets ( View  objects). Layouts are containers that control how their child views are positioned on the screen. Widgets are UI components such as buttons and text boxes.

Today we sorted the functionality and implemented the working of different activities together.

Today we started working on UI of our application and we developed sin up and login forms and customized it's design. The user interface for an Android app is built using a hierarchy of  layouts  ( ViewGroup  objects) and  widgets ( View  objects). Layouts are containers that control how their child views are positioned on the screen. Widgets are UI components such as buttons and text boxes.

The Android multimedia framework includes support for playing variety of common media types, so that you can easily integrate audio, video and images into your applications. You can play audio or video from media files stored in your application's resources (raw resources), from standalone files in the filesystem, or from a data stream arriving over a network connection, all using MediaPlayer  APIs.

Today we worked on fragments. A  fragment  is an independent Android component which can be used by an activity. A fragment encapsulates functionality so that it is easier to reuse within activities and layouts. A fragment runs in the context of an activity, but has its own life cycle and typically its own user interface. It is also possible to define fragments without an user interface, i.e., headless fragments. Android devices exists in a variety of screen sizes and densities. Fragments simplify the reuse of components in different layouts and their logic. You can build single-pane layouts for handsets (phones) and multi-pane layouts for tablets. You can also use fragments also to support different layout for landscape and portrait orientation on a smartphone. As it is possible to dynamically add and remove fragments from an activity. The usage of fragments allows to design very flexible user interfaces.

Today we learnt about Forward Passing and Backward Passing using intent and intent bundle. In forward pass  you just need to use the putExtra Method to pass the data across multiple program screens. The putExtra method accepts many kinds of data, such as String, int, float, byte etc etc .. we can use intent bundle like: Intent intent = new Intent ( this , OtherActivity . class ); intent . putExtra ( OtherActivity . KEY_EXTRA , yourDataObject ); startActivity ( intent ); Bakward Passing: Activity 1 : Intent i = new Intent ( this , Activity2 . class ); startActivityForResult ( i , 1 ); Activity 2: Intent intent = new Intent (); intent . putExtra ( "editTextValue" , "value_here" ) setResult ( RESULT_OK , intent ); finish ();

Today we practiced on content provider.We worked on retrieve ,delete and update operations.

Today we worked on content provider (The data base of android app). Content providers can help an application manage access to data stored by itself, stored by other apps, and provide a way to share data with other apps. They encapsulate the data, and provide mechanisms for defining data security. Content providers are the standard interface that connects data in one process with code running in another process. Use content providers if you plan to share data. If you don’t plan to share data, you may still use them because they provide a nice abstraction, but you don’t have to. This abstraction allows you to make modifications to your application data storage implementation without affecting other existing applications that rely on access to your data. In this scenario only your content provider is affected and not the applications that access it.  

Today we worked on Broadcast Receiver and other services. Android apps can send or receive broadcast messages from the Android system and other Android apps . These broadcasts are sent when an event of interest occurs. For example, the Android system sends broadcasts when various system events occur, such as when the system boots up or the device starts charging. Apps can also send custom broadcasts, for example, to notify other apps of something that they might be interested in (for example, some new data has been downloaded).

Today we learnt about android menus. By default, every Activity supports an options menu of actions or options. You can add items to this menu and handle clicks on your additions. The easiest way of adding menu items is inflating an XML file into the menu  via MenuInflator. Different menu types support different features: Context menus : Do not support item shortcuts and item icons. Options menus : The  icon menus  do not support item check marks and only show the item's condensed title. The  expanded menus  (only available if six or more menu items are visible, reached via the 'More' item in the icon menu) do not show item icons, and item check marks are discouraged. Sub menus : Do not support item icons, or nested sub menus.

Today we worked with Fragments and different kinds of views, also how we can create an application for a website, using web view.A common scenario in which using webview is helpful is when you want to provide information in your app that you might need to update, such as an end-user agreement or a user guide. Within your Android app, you can create an activity that contains a  webview , then use that to display your document that's hosted online. Another scenario in which  webview   can help is if your app provides data to the user that always requires an Internet connection to retrieve data, such as email. In this case, you might find that it's easier to build a  webview   in your Android app that shows a web page with all the user data, rather than performing a network request, then parsing the data and rendering it in an Android layout. Instead, you can design a web page that's tailored for Android devices and then implement a  we...

Today we learnt to work with sensors and notification manager.Sensors are used  on the device to add rich location and motion capabilities to your app, from GPS or network location to accelerometer, gyroscope, temperature, barometer, and more. Most Android-powered devices have built-in sensors that measure motion, orientation, and various environmental conditions. These sensors are capable of providing raw data with high precision and accuracy, and are useful if you want to monitor three-dimensional device movement or positioning, or you want to monitor changes in the ambient environment near a device. For example, a game might track readings from a device's gravity sensor to infer complex user gestures and motions, such as tilt, shake, rotation, or swing. Likewise, a weather application might use a device's temperature sensor and humidity sensor to calculate and report the dewpoint, or a travel application might use the geomagnetic field sensor and accelerometer to report a c...

Today we worked on Layouts. A layout defines the structure for a user interface in your app, such as in an activity . All elements in the layout are built using a hierarchy of view  and view group  objects. Various layouts like grid layout, linear layout ,constraint layout etc were used to frame simple prototypes. Also, we learnt and worked on the working of "toast text".

Today we learnt about  the manifest file and the various kinds of permissions that an app can ask the user also we built various prototypes using text views, buttons, edit text etc.