Web Application Project: Diary and Photo Storage using JavaScript

This project report details the development of a web application using JavaScript and local storage for diary and photo storage. It highlights the differences between a prototype and the final product, emphasizing the prototype's static nature and limited functionality compared to the dynamic and interactive final application. The report also addresses crucial privacy and security issues inherent in web applications, such as cross-site scripting and SQL injection, and suggests using a real database like MySQL to enhance data integrity and user privacy. The conclusion underscores the value of prototypes in representing the final product and the importance of employing databases for secure web application development, ultimately aiming to build user trust by protecting their data. References to relevant sources are included to support the analysis.

Introduction
A web application is an application that can be accessed by user through the internet. Th application has
the ability to store user input data. The user can view the stored data, update when he/she want to
make changes od delete data when he/she does not need it. In this project we will be using JavaScript
and local storage to create a simple web application that has the capability of storing users’ diaries and
photo.
Difference between the prototype and the finished
website application
There is a big difference between the prototype and the finished product. The prototype is an early
representation of a product. It can be in form of model, product design or a software (Bulfin, 2017 ). The
prototype can have working functionalities, in our case, the prototype was fed with some static data.
The data was immutable meaning it could not change. When we tried to update the data, there was no
changes. Another big difference between the prototype and the finished product is deletion of data.
When we tried to delete data on the prototype, the data could not be deleted. Inserting image was
automated on the prototype. There was only one image that the user could insert.
In contrary, our final application has fully working functions. User can insert their own data. They could
delete the data and they can even update existing data. In final application user can choose the image
they want to upload. The finished product is a dynamic website meaning user can interact with while
the prototype is static does not not allow user to interact with.
privacy and security issues of the web application
privacy is the process of maintaining data integrity, meaning we need to hide the information of our
user to third parties. In web application users we provide their information as an organization its our
duty to protect that data.
Many web applications are exposed to security risk. Exploiters can use the weakness of the web
application to steal or manipulate data. There are two most common security issue in web application.
They are cross-site Scripting and SQL injection. SQL injections allows user to get access to the web
application databases. The user can use the information she/he gained to exploit your website. With
cross-site scripting the user intercepts the data sent by user (Michael, 2017). He can use the data to gain
access to user accounts.
In the diary’s web application, we lack the privacy of data. The data are stored in our local machine. Any
user with the access of the application have the ability to change data or even delete data. To avoid this
kind of risk, its advisable we store data to a real database. There is different type of database but the
most used one is MySQL database.
We can store the diaries information to MySQL database and grant users’ privileges, meaning not all
users will have the ability to change or access the data in our database. This is the best way of avoiding
security risk and it can maintain data integrity.

Conclusion
It clear that a prototype can not be relied but it can be used to represent how the final product will look.
It is good to come up with a prototype before coming up with a final product. When building a web
application it is advised we use a real database. The database has some way of securing data from
attackers With a database we can keep the privacy of the data which increase users trust.
References
Bulfin, D., 2017 . Prototype to Final Product. How to Preserve the Soul of Your Design.. [Online]
Available at: https://boltgroup.com/prototype-to-final-product
[Accessed 16 March 2020].
Michael, W., 2017. Potential Privacy and Security Issues. [Online]
Available at: https://iapp.org/news/a/2006-09-web-watch-potential-privacy-and-security-issues-in-
outsourcing/