Skip to main content

Posts

Showing posts from October, 2018

Day 52

Today we implemented distance between two points and sharing information between driver and rider. The  Google Maps Directions API  is a web service that Google provides us to get information about a route. A route is getting from an initial location to a specific destination. This web service provides us with information for different transport modes, waypoints and traveling times.

Day 51

Today we implemented distance between two points and sharing information between driver and rider. The  Google Maps Directions API  is a web service that Google provides us to get information about a route. A route is getting from an initial location to a specific destination. This web service provides us with information for different transport modes, waypoints and traveling times.

Day 50

Today we worked on find driver for request. At a high level, you use Volley by creating a  RequestQueue  and passing it  Request  objects. The  RequestQueue manages worker threads for running the network operations, reading from and writing to the cache, and parsing responses. Requests do the parsing of raw responses and Volley takes care of dispatching the parsed response back to the main thread for delivery.

Day 49

Today we made a pickup request logic and find driver for request logic . At a high level, you use Volley by creating a  RequestQueue  and passing it  Request  objects. The  RequestQueue manages worker threads for running the network operations, reading from and writing to the cache, and parsing responses. Requests do the parsing of raw responses and Volley takes care of dispatching the parsed response back to the main thread for delivery.

Day 48

Today we tried to get our updated location and save our updated location using Google maps API. The  Google Maps Directions API  is a web service that Google provides us to get information about a route. A route is getting from an initial location to a specific destination. This web service provides us with information for different transport modes, waypoints and traveling times.

Day 47

Today we connected Google maps to our application.  The  Google Maps Directions API  is a web service that Google provides us to get information about a route. A route is getting from an initial location to a specific destination. This web service provides us with information for different transport modes, waypoints and traveling times.

Day 46

Connected Fire base to the application and saved data from application to fire base. Also applied validation for avoiding storage of  redundant data in fire base. 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. 

Day 45

Connected Fire base to the application and saved data from application to fire base. Also applied validation for avoiding storage of  redundant data in fire base. 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 

Day 44

We worked on the Rider registration and Login today using 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 

Day 43

We worked on the Rider registration and Login today using 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 

Day 42

We worked on the Rider registration and Login today using 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 

Day 41

We worked on the Rider registration and Login today using 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 

Day 40

We worked on problem analysis and finalized a topic for our project. We gathered system requirements from people and started working on UI. Requirements gathering is also popularly known as requirements elicitation. The primary objective of the requirement gathering task is to collect the requirements from the stake - holders. A stakeholder is a source of requirements and is usually a person, or a group of persons who either directly or indirectly are concerned with the software. Procedures adopted while requirements gathering during the project were: • Interview: We interviewed people from different residential areas and gathered their requirements. • Scenario Analysis: The different use cases and functionality of the app were discussed. It includes   discussion on Main panel and followed by transaction history . • Task Analysis: The technologies to be used in Frontend and Backend were discussed. • Studying Documentation: The documentation of various cloud tec...

Day 39

We implemented reminder API and notification and SMS feature in our application. A reminder consists of: When to show the reminder, expressed as minutes before the event start time The delivery method to use (see  Delivery mechanisms ) Reminders can be specified for whole calendars and for individual events. Users can set  default reminders  for each of their calendars; these defaults apply to all events within that calendar. However, users can also override these defaults for individual events, replacing them with a different set of reminders.

Day 38

We worked on RecyclerView today. The   RecyclerView   widget is a more advanced and flexible version of   ListView . In the  RecyclerView  model, several different components work together to display your data. The overall container for your user interface is a  RecyclerView  object that you add to your layout. The  RecyclerView  fills itself with views provided by a  layout manager  that you provide. You can use one of our standard layout managers (such as  LinearLayoutManager  or  GridLayoutManager ), or implement your own. The views in the list are represented by  view holder  objects. These objects are instances of a class you define by extending  RecyclerView.ViewHolder . Each view holder is in charge of displaying a single item with a view. For example, if your list shows music collection, each view holder might represent a single album. The  RecyclerView  creates only as many view ...

Day 37

We worked on location and proximity sensors and implemented in mini application. The Android platform provides two sensors that let you determine the position of a device: the geomagnetic field sensor and the accelerometer. The Android platform also provides a sensor that lets you determine how close the face of a device is to an object (known as the  proximity sensor ). The geomagnetic field sensor and the proximity sensor are hardware-based. Most handset and tablet manufacturers include a geomagnetic field sensor. Likewise, handset manufacturers usually include a proximity sensor to determine when a handset is being held close to a user's face (for example, during a phone call). For determining a device's orientation, you can use the readings from the device's accelerometer and the geomagnetic field sensor.