Skip to main content

App Features(Customer)

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.

    1. 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. 

    2. OutletMenu: On selecting one of the outlets, this fragment is called which displays the menu of the respective outlet. OutletMenu contains a recycler view, which populates itself using OutletMenu_Customer_adapter by querying the Menu of the particular Outlet using Firebase UI. The customer can choose the food item which they want and can add it to the cart.

    3. CartFragment: This fragment displays the final list of items and the Total Amount in the Cart before checkout. It also contains a quantity modifier where the user can increase, decrease or delete items from the cart, where upon the total is readjusted based on the final items in the cart. CartFragment contains a recycler view, which populates itself using CartAdapter by querying the Cart details of the particular User using Firebase UI. The customer can also check the total bill before paying. 

    4. Payment Window(Additional Feature): The payment integration was done using the Easy UPI Payment Library. Upon clicking the PlaceOrder Button, the user is redirected to the PaymentActivity, whereby after entering required UPI information, the transaction takes place successfully. After the transaction takes places successfully, it is added to the Transaction History of the Customer and the Vendor. The Transaction ID is generated using the System.currentTimeMillis().

    5. TransactionHistory_Customer: This fragment displays information regarding the previous transactions made by the user. It displays the Total Amount, TransactionID, and the Outlet from which they had purchased.  This fragment contains a recycler view, which populates itself using TransactionHistory_Customer_Adapter by querying the Transaction History details of the particular User using Firebase UI. 

    6. Customer Profile: This fragment displays the details of the customer stored by us in the Database, which includes Name, Email, and Phone Number.






Comments

Popular posts from this blog

Languages and Applications Used

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.              ...

App Features(Vendor)

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...