Diner2Door

Database designs provide the blueprints of how the data is going to be stored in a system.  Database design is a vital component of any app, and it determines what data to be stored and how the different data elements interact. A proper database affects the overall performance of an application. We're using a Firebase Database for our app. We prefer Firebase over SQLite since this is a multi-user app and FireBase is preferred over SQLite for Multi-User Apps.  Google Firebase is Google-backed application development software that allows developers to develop Android, IOS, and Web apps. It can be used for user authentication and to host a real-time database. The database design for our app is given below. The root node of our Database is Users, which branches into two children i.e. Customer and Vendor. We store all the information corresponding to the customer using the Customer's Mobile Number as the Key, and for vendor, we store all the information using the OutletName as the k

App architecture is a consistent plan that needs to be made before the development process starts.  App architecture offers a road map for how the various application components must be set up and connected. It defines how the UI, database and background tasks interact to make the required job possible. We have used MVC(Model View Control) architecture to build our app.  MVC is known for handling multiple views and huge volumes of data effectively. There are three  components in MVC: Model : The model contains data about the application. All the information which must be stored or displayed and access specifications are mentioned here.  model.java serves as our model class. View : View forms the UI part of the app. Views displays model data to the users and allow them to modify the data. The Layouts form the view.  Controller : The controller handles user requests and controls user navigation within the app. It processes user input. The Activities and the Fragments form the Controller.

Here we talk about the Vendor's side of the app:  The Vendor Homepage contains a fragment that displays the corresponding layout of the item clicked in the sidebar. As soon as the vendor is logged in OutletMenu Fragment is called which displays the menu of the vendor's outlet, where the vendor and add, update and delete items from his menu. Based on the customer's requirements and usability, we have developed an exclusive set of fragments and an activity. OutletMenu: This fragment will be called default after the vendor is logged in. It displays the menu of the vendor's outlet. It contains a recycler view, which populates itself using outletMenu_adapter by querying the Menu corresponding to the vendor's outlet in the Database using Firebase UI. The vendor also has the option to edit and delete items from the existing menu. When the vendor clicks on the edit option, a Dialog using DialogPlus class is built and the current values are retrieved from the databases an

Here, we talk about the Customer's side of the app: The customer Homepage contains a fragment that displays the corresponding layout of the item clicked in the sidebar. As soon as the customer is logged in OutletList Fragment is called which displays the list of outlets present, where clicking on a particular outlet, will take them to the particular menu of the outlet. We've used Firebase UI in all fragments. Firebase UI is a class provided by Firebase SDK to make a query in the database to fetch appropriate data. Based on the customer's requirements and usability, we have developed an exclusive set of fragments. OutletList: This fragment will be called after the user is logged in. It will consist of a list of eateries that are open at any given time. It contains a recycler view, which populates itself using outletList_adapter by querying the List of Vendors in the Database using Firebase UI.  OutletMenu: On selecting one of the outlets, this fragment is called which di

This page talks about the standard features of both Vendor and Customer: When the application is launched, Main Activity sends an intent to the Splash Activity, which displays the App Logo for 2000 milliseconds, from where the control comes back to the Main Activity.  The app splash screen is the brief introductory screen that appears as the app loads after the user has just opened the app. Registration:   New users can register by entering their information. Their account gets created upon submitting the registration form.  The new user fills out their e-mail ID, mobile number, and Password. They will select the type of user in a spinner. If the type of user is a vendor, they have to add a URL of the picture of their food outlet. Then on clicking register, a new account is created. Login: Users can log in using their Username. The user is directed to the Login Activity for authentication. The User first selects what type of user (i.e., Customer or Vendor) in the Spinner on the Login p

We will be detailing the software, languages and frameworks used to build the app: Android Studio:  It is the official integrated development environment(IDE) for Android application development. It incorporates various code editing and developer tools for a smooth and user-friendly user experience. It also has various options to run and debug code. Android Studio uses a build automation tool known as Gradle for compiling, linking and packaging the code. We had learnt to use Android Studio as a part of our course. Java : Java is a general purpose programming language which provides object oriented programming concepts like encapsulation and inheritance. We used Java for Backend programming. XML : XML stands for eXtensible Markup Language. It is generally used to develop web pages and web applications. XML has advantages like letting the user make their own descriptive tags based on his/her needs. We used XML for frontend programming.                                                     

There are a good number of food outlets in BITS Pilani Hyderabad Campus and they are very popular among students. This in turn results in high waiting time for customers. Also, this leads to decreased revenue for outlets since people choose not to utilize the outlets due to the long waiting time. Our Solution? Diner2Door is an app created to solve this problem. The users can order from their favorite outlets using our app from the convenience of their own rooms. We made two separate pages for both the vendor and the customer where the vendor can change the menu based on availability and the customer can choose their favorite outlet and order food from their rooms.