Food Consumption App: A Review And Project Proposal Essay.

Architecture of the proposed app

Give the reviews on the project of Web Development App.

The mobile app proposed to be developed is to keep the history of food consumptions of the user. The app will be developed on Android platform because we want this app to be used by more people and according to 2017 comparative study Android users are more than 80 percent worldwide with contrast to iPhone, windows, blackberry and other users (Katariya, 2017). The app focuses on intaking the user’s food consumption which can be later shared or sent to the users through dropbox, google drive, and email. This app will have a simple User Interface which will be easily accessible and visible to the users as shown in User Interface section of this proposal.

This app will have a possibility of many further additional upgrades after it is successful launched in the market. This app can further advanced for plotting the users diet history and healthy or unhealthy foods and diets by using data mining from all the user’s data history. This is also one of the reasons why the database in app will have a soft delete feature.Architecture of the proposed app

The proposed app, History of Food Consumption will be developed for Android platforms using Android Studio. The app will be able to add all the food information of the user. After the user opens the app the app will have the list of the Food history in the homepage. Then the user can add a new food by entering the food type, description, date and time. After the user saves the information the data will be saved in the database. The added food will then be listed at the homepage and the user can click on the particular food list to either edit the information or delete it.

MySQL database will be used as the database for the proposed app. The database will have a soft delete feature enabled in them so that the user can undo the deleted food list if he/she desired to do so. User will also be able to share/send the database instance through dropbox, google drive, and email.

The proposed app of History of Food Consumption will have three layers namely: Presentation Layer, Business Layer and Data Layer which are the most common layers for app (Pisuwala, 2018).

Presentation Layer: All the view and User Interface for this app will be focused in this layer. This is the layer where only the appearance of the app and easier to use will be focused rather than other code and other technical issues.

Business Layer: In this layer what type of features and functionalities should be provided to client will be analyzed and finalized.

Data Layer: This layer focuses on where to store data and how to manipulate them to get a meaningful result.

Nowadays, Android can run on different types of devices including phones, televisions and tablets. Hence, the developed app will have a range of many potential audiences for the app (Android, 2018). So, the device capability of the app may determine whether the user can use them on all platforms.

Device Capability Requirements

This app will use the keyboard of the user’s device to get the information of the user’s food consumption. This app will not require any camera, microphone, or other information of the user.

The app will Use memory efficiently so that it can avoid long-running processes. Hence, the app will only need about 1GB RAM and around 20 MB storage in the device to be able to install. The minimum version for the app to function properly will be Version 5.0 (Lollipop) and above.

1. Use Case

2. Use Case of Add Food

Use Case Description

When a User

Wants to add a food

They can click the add button and add the food with the option of Breakfast, Lunch, Dinner, Snack, or Junk food with Description, date and time.

So that the food with their description will be added to the database

Use Case Diagram

Figure 1: Use Case Diagram of Add Food

ii.Use Case of Edit Food

Use Case Description

When a User

Wants to edit a food

They can click the particular food from the list

So that they can change the food details

Use Case Diagram

Figure 2: Use Case Diagram of Edit Food

iii.Use Case of Delete Food

Use Case Description

When a User

Wants to delete a food

They can click on the food from the list and delete it

Use Case Diagram

Figure 3: Use Case Diagram of Delete food

Use Case Description

When a User

Wants to share/send the database instance through Dropbox, Google Drive, and email

They can click on the share button and choose through which they want to share those data.

Use Case Diagram

Figure 4: Use Case Diagram of Share/Send Food lists

Use Case Description

When a User

Wants to view the foods

The user can view the foods according to the day selected or by default, the current day

Use Case Diagram

Figure 5: Use Case Diagram of View foods

Figure 6: Class Diagram of History of Food Consumption app

Figure 7: User Interface of Home Page of History of Food Consumption app

This is the wireframe of the main home page of the Food Consumption app. All the added foods will be listed according to the date selected at the top. By default, current date is selected. The Add button is used to add the food details which will be listed in the home page after added properly. At the end all the added information can be shared/sent to the user using dropbox, google drive, and email.

Figure 8: User Interface of Add Food Page of History of Food Consumption app

This is the add food page. This is triggered after clicking add button on homepage. User can select whether he/she wants to add Breakfast, Lunch, Dinner, Snack and/or Junk Foods. Then after adding the date and time of the food consumption he/she can save the food details that they consumed.

Figure 9: User Interface of Edit and Delete of History of Food Consumption app

The user can edit and/or delete the food details that they entered while adding. They can change the food and update it. If they do not want to update, then they can just delete the food by using Del button at the top right corner of the app.

Architecture of the proposed app

The history of the food consumption applicalication is one of the most interesting that have ever been made. The work of the application is to keep attack of the food that is being consumed by the user. The application is launched in the android is because of the factor that the majority of the population in the world uses the android operating system in daily life (Vepsäläinen, 2016). The features a simple user interface which will let the users to use the app as an ease. Further the application uses the technology of the database so that it becomes easier for the user to include and delete entries from a table.

The application works as the following way when the user gets to the application  the first page or the home page shows the food history, and there are options of the add food. Once the food is added it is listed in the homepage and the option for the deletion of the food is also present in the homepage along with the edit options (Zhang, Yao & Ramakrishnan, 2016). The user can store the details of the food in the local storage and also in the Google drive or the Microsoft drives.

The application will have their nessacery layers for the working of the applications namely the Presentation Layer, Business Layer and Data Layer. The user interface is the part of the presentation layer while the management is done in the business layer and the data layer of the application (Salva & Zafimiharisoa, 2015). While the requirements for the purpose of the installation of the application is quite low as the app can run on as low as the 1 GB of ram and 20mb of the internal storage. While the minimum android version that is required to for the purpose of running the application is Version 5.0 that is android lollipop. The user interface consist of t for parts namely thee add food where the user can choose for the food, write description about it including the date and time. While the second screen that the user gets is the edit food table. While the third one is the delete food table where the user gets the table for deletion of the food chart. The other pages consists of the lists like the view food options and share list options. The use of the MySQL database is one of the other major feature of the application as it can help the user to access the application in a better manner (Xia et al., 2015). Also it helps the user in the proper interaction with the different layers of the application.

Overall it can be said as a good application but there are some of the major issues that is needed to be fixed. The issues are explained in the paper further why this issues must be fixed is also justified in the paper.

In the modern world with the use of the technology it has become easier for thee hackers to access any information from anywhere if there is one single point to be exploited. In the case of the food history it must be said that there is no security feature that is implemented in the application. There is no a any option for the user to keep the data secured. Once any fraudster gets the access to the smartphone then automatically the fraudster gets the access to the users’ application data. One of the most dangerous thing is that the app is connected to the drive or the Microsoft drive and hence any one can get the access to the information present in the drives (Wijesekera et al.,2015). Also the user email address if connected with the applciaiitn may be leaked hence every personal information of the user will get leaked. This is one of the major issue that has be to be properly introduced in the application (Li et al., 2015). In order to make the account more secured there can be options for log in every time the user gets in the application so that the data in the application are safe. Further one of the other major issue is that whether the application is capable of proper handling of the cache files that are stored in then local files.  One of the other major problem is that if every time the data base is not properly updated overtime the user enters a new food or edits or deleted something (Backes, Bugiel & Derr, 2016). This may create missing data and also errors in the data base can create data redundancy. One of the other major problem is the three can be numerous number of people logging in at the same time in the application hence there must be a huge cache memory. When a number of people is logging in at the same time there must not be any lagging issue in the system

Some of the minor issues that can come up in the applications can be easily solved by the client or the admin. Some of the problems like the extra battery drainage problems, orientation problems like the application getting stuck in one mode that is portrait or landscape mode, proper ram management can be easily solved by the admiration and the creator of the application (Cai & Ryder, 2017). One of the other minor problem is same kind of the applications are present is that there are too many similar applications that are present in the store hence the user must be careful while downloading the applications. The user must clear the cache file of the application in a regular interval of time so that there are less chances of the application to get lag. Also one the other issue is that the app is free for some duration of time, this helps the creators of the application a good profit but reduces the number of the users.

References

Vepsäläinen, A. (2016). Application security: In Android application development.

Zhang, H., Yao, D. D., & Ramakrishnan, N. (2016, October). Causality-based sensemaking of network traffic for android application security. In Proceedings of the 2016 ACM Workshop on Artificial Intelligence and Security (pp. 47-58). ACM.

Salva, S., & Zafimiharisoa, S. R. (2015). APSET, an Android aPplication SEcurity Testing tool for detecting intent-based vulnerabilities. International Journal on Software Tools for Technology Transfer, 17(2), 201-221.

Xia, M., Gong, L., Lyu, Y., Qi, Z., & Liu, X. (2015, May). Effective real-time android application auditing. In Security and Privacy (SP), 2015 IEEE Symposium on (pp. 899-914). IEEE.

Wijesekera, P., Baokar, A., Hosseini, A., Egelman, S., Wagner, D., & Beznosov, K. (2015, August). Android Permissions Remystified: A Field Study on Contextual Integrity. In USENIX Security Symposium (pp. 499-514).

Backes, M., Bugiel, S., & Derr, E. (2016, October). Reliable third-party library detection in android and its security applications. In Proceedings of the 2016 ACM SIGSAC Conference on Computer and Communications Security (pp. 356-367). ACM.

Cai, H., & Ryder, B. G. (2017, September). Understanding Android application programming and security: A dynamic study. In Software Maintenance and Evolution (ICSME), 2017 IEEE International Conference on (pp. 364-375). IEEE.

Li, L., Bartel, A., Bissyandé, T. F., Klein, J., Le Traon, Y., Arzt, S., ... & McDaniel, P. (2015, May). Iccta: Detecting inter-component privacy leaks in android apps. In Proceedings of the 37th International Conference on Software Engineering-Volume 1 (pp. 280-291). IEEE Press.