Web Application - Revision history

User at 22:10, 15 August 2023

2023-08-15T22:10:16Z

Show changes

User at 21:38, 15 August 2023

2023-08-15T21:38:29Z

Show changes

User at 21:18, 15 August 2023

2023-08-15T21:18:58Z

User at 00:12, 6 August 2023

2023-08-06T00:12:23Z

User at 21:11, 6 December 2022

2022-12-06T21:11:14Z

User at 14:36, 23 November 2022

2022-11-23T14:36:07Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T19:13:26Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

User at 19:09, 17 January 2020

2020-01-17T19:09:39Z

Show changes

User at 18:45, 17 January 2020

2020-01-17T18:45:31Z

User at 18:40, 17 January 2020

2020-01-17T18:40:40Z

@@ Line 1: / Line 1: @@
 == Definition of Web Application ==
-A '''Web Application''' aka web-based application is any program that is accessed over a [[Network|network]] connection using [[Hypertext Transfer Protocol (HTTP)|HTTP]], rather than existing within a [[Device|device’s]] memory. Web-based applications often run inside a [[Web Browser|web browser]]. However, web-based applications also may be client-based, where a small part of the program is downloaded to a user’s [[Desktop|desktop]], but processing is done over the [[Internet|internet]] on an external [[Server|server]]. Web-based applications are also known as web apps.<ref>Definition - What is a Web Application [https://www.techopedia.com/definition/26002/web-based-application Techopedia]</ref>
+A '''Web Application''' aka web-based application or web app, is a software program that runs on a web server and is accessed through a web browser over the Internet or an Intranet. Unlike traditional desktop applications, which are installed on a local computer, web applications are accessible from any computer or mobile device and do not need to be downloaded and installed. They are built using standard web technologies, including HTML, CSS, JavaScript, and various backend scripting languages like PHP, Python, Ruby, and Java.
@@ Line 8: / Line 10: @@
 == History of Web Applications<ref>History of Web Applications [https://en.wikipedia.org/wiki/Web_application Wikipedia]</ref> ==
-In earlier computing models like [[Client Server Model|client–server]], the processing load for the [[Application|application]] was shared between code on the [[server]] and code installed on each client locally. In other words, an application had its own pre-compiled client program which served as its user interface and had to be separately installed on each user's personal computer. An upgrade to the server-side code of the application would typically also require an upgrade to the client-side code installed on each user workstation, adding to the support cost and decreasing [[Productivity|productivity]]. In addition, both the client and server components of the application were usually tightly bound to a particular [[computer]] [[architecture]] and [[Operating System (OS)|operating system]] and porting them to others was often prohibitively expensive for all but the largest applications. (Nowadays, native apps for mobile devices are also hobbled by some or all of the foregoing issues.)
+The history of web applications is intertwined with the history of the World Wide Web. From basic, static web pages to sophisticated, interactive applications, web applications have undergone significant evolution. Below is a detailed timeline of the major milestones in the history of web applications:
-In contrast, web applications use web documents written in a [[standard]] format such as [[HTML (Hypertext Markup Language)|HTML]] and [[JavaScript]], which are supported by a variety of web browsers. Web applications can be considered as a specific variant of client–server [[software]] where the client software is downloaded to the client machine when visiting the relevant web page, using standard procedures such as HTTP. Client web software updates may happen each time the web page is visited. During the session, the web browser interprets and displays the pages, and acts as the universal client for any web application.
+'''1996:''' Microsoft introduces its browser, Internet Explorer, marking the beginning of the "browser wars" with Netscape. During this time, Microsoft also introduced its server-side script engine for dynamically generated web pages, Active Server Pages (ASP).
-In the early days of the Web, each individual web page was delivered to the client as a static document, but the sequence of pages could still provide an interactive experience, as user input was returned through web form elements embedded in the page markup. However, every significant change to the web page required a round trip back to the server to refresh the entire page.
+'''The Dot-Com Bubble and The Emergence of LAMP Stack (Late 1990s - Early 2000s)'''<br />
-In 1995, Netscape introduced a client-side scripting language called JavaScript allowing programmers to add some dynamic elements to the user interface that ran on the client side. So instead of sending [[Data|data]] to the server in order to generate an entire web page, the embedded scripts of the downloaded page can perform various tasks such as input validation or showing/hiding parts of the page.
+'''1998:''' The term "Web Application" starts to be used more commonly, indicating a shift from basic, static websites to more interactive, dynamic, and functional web platforms.
-In 1996, Macromedia introduced Flash, a vector animation player that could be added to browsers as a [[plug-in]] to embed animations on the web pages. It allowed the use of a scripting language to program interactions on the client side with no need to communicate with the server.
+'''Late 1990s:''' The LAMP (Linux, Apache, MySQL, and PHP/Perl/Python) stack emerges as a popular set of technologies for building dynamic web applications.
-In 1999, the "web application" concept was introduced in the Java language in the Servlet Specification version 2.2. At that time both JavaScript and XML had already been developed, but Ajax had still not yet been coined and the XMLHttpRequest object had only been recently introduced on Internet Explorer 5 as an [[ActiveX]] object.
+'''The Rise of AJAX and Rich Internet Applications (Mid 2000s)'''<br />
-In 2005, the term Ajax was coined, and applications like Gmail started to make their client sides more and more interactive. A web page script is able to contact the server for storing/retrieving [[data]] without downloading an entire web page.
+'''2005:''' Google Maps is released, another seminal AJAX application. Jesse James Garrett publishes an essay coining the term "AJAX", officially recognizing the technology that enables highly interactive web applications.
-In 2011, HTML5 was finalized, which provides graphic and multimedia capabilities without the need of client side plug-ins. HTML5 also enriched the semantic content of documents. The [[Application Program Interface (API)|APIs]] and [[Document Object Model (DOM)|document object model (DOM)]] are no longer afterthoughts, but are fundamental parts of the HTML5 specification. WebGL API paved the way for advanced 3D graphics based on HTML5 canvas and JavaScript language. These have significant importance in creating truly platform and browser independent rich web applications.
+'''The Era of Web 2.0 and Social Media Explosion (Late 2000s)'''<br />

← Older revision		Revision as of 00:12, 6 August 2023
Line 23:		Line 23:

	In 2011, HTML5 was finalized, which provides graphic and multimedia capabilities without the need of client side plug-ins. HTML5 also enriched the semantic content of documents. The [[Application Program Interface (API)\|APIs]] and [[Document Object Model (DOM)\|document object model (DOM)]] are no longer afterthoughts, but are fundamental parts of the HTML5 specification. WebGL API paved the way for advanced 3D graphics based on HTML5 canvas and JavaScript language. These have significant importance in creating truly platform and browser independent rich web applications.		In 2011, HTML5 was finalized, which provides graphic and multimedia capabilities without the need of client side plug-ins. HTML5 also enriched the semantic content of documents. The [[Application Program Interface (API)\|APIs]] and [[Document Object Model (DOM)\|document object model (DOM)]] are no longer afterthoughts, but are fundamental parts of the HTML5 specification. WebGL API paved the way for advanced 3D graphics based on HTML5 canvas and JavaScript language. These have significant importance in creating truly platform and browser independent rich web applications.
−
−
−	~~== The Need for Web Application<ref>Why you need a Web Application? [https://www.guru99.com/difference-web-application-website.html Guru99]</ref> ==~~
−	~~Web applications are more popular because of the following reasons:~~
−	*Compared to [[desktop]] applications, web applications are easier to maintain by as they use the same code in the entire application. There are no compatibility issues.
−	*Web applications can be used on any platform: Windows, Linux, Mac… as they all support modern browsers.
−	*Mobile App store approval not required in web applications.
−	*Released any time and in any form. No need to remind users to update their applications.
−	*Web applications can be accessed 24 hours of the day and 365 days a year from any PC.
−	*Both computer and [[Mobile Device\|mobile devices]] can be used to access the required data.
−	*Web applications are a cost-effective option for any [[Organization\|organization]]. Seat Licenses for Desktop software are expensive where SasS, are generally, pay as you go.
−	*Web-Based Apps are Internet-enabled apps that are accessed through the mobile's web browser. Therefore, you don't require to download or install them.

@@ Line 1: / Line 1: @@
 == Definition of Web Application ==
-A '''Web Application''' aka web-based application is any program that is accessed over a [[Network|network]] connection using [[Hypertext Transfer Protocol (HTTP)|HTTP]], rather than existing within a [[Device|device’s]] memory. Web-based applications often run inside a [[Web Browser|web browser]]. However, web-based applications also may be client-based, where a small part of the [[Computer Program|program]] is downloaded to a user’s [[Desktop|desktop]], but processing is done over the [[Internet|internet]] on an external [[Server|server]]. Web-based applications are also known as web apps.<ref>Definition - What is a Web Application [https://www.techopedia.com/definition/26002/web-based-application Techopedia]</ref>
+A '''Web Application''' aka web-based application is any program that is accessed over a [[Network|network]] connection using [[Hypertext Transfer Protocol (HTTP)|HTTP]], rather than existing within a [[Device|device’s]] memory. Web-based applications often run inside a [[Web Browser|web browser]]. However, web-based applications also may be client-based, where a small part of the program is downloaded to a user’s [[Desktop|desktop]], but processing is done over the [[Internet|internet]] on an external [[Server|server]]. Web-based applications are also known as web apps.<ref>Definition - What is a Web Application [https://www.techopedia.com/definition/26002/web-based-application Techopedia]</ref>
@@ Line 8: / Line 8: @@
 == History of Web Applications<ref>History of Web Applications [https://en.wikipedia.org/wiki/Web_application Wikipedia]</ref> ==
-In earlier computing models like [[Client Server Model|client–server]], the processing load for the [[Application|application]] was shared between code on the [[server]] and code installed on each client locally. In other words, an application had its own pre-compiled client program which served as its user interface and had to be separately installed on each user's personal [[Computer|computer]]. An upgrade to the server-side code of the application would typically also require an upgrade to the client-side code installed on each user workstation, adding to the support cost and decreasing [[Productivity|productivity]]. In addition, both the client and server components of the application were usually tightly bound to a particular [[computer]] [[architecture]] and [[Operating System (OS)|operating system]] and porting them to others was often prohibitively expensive for all but the largest applications. (Nowadays, native apps for mobile devices are also hobbled by some or all of the foregoing issues.)
+In earlier computing models like [[Client Server Model|client–server]], the processing load for the [[Application|application]] was shared between code on the [[server]] and code installed on each client locally. In other words, an application had its own pre-compiled client program which served as its user interface and had to be separately installed on each user's personal computer. An upgrade to the server-side code of the application would typically also require an upgrade to the client-side code installed on each user workstation, adding to the support cost and decreasing [[Productivity|productivity]]. In addition, both the client and server components of the application were usually tightly bound to a particular [[computer]] [[architecture]] and [[Operating System (OS)|operating system]] and porting them to others was often prohibitively expensive for all but the largest applications. (Nowadays, native apps for mobile devices are also hobbled by some or all of the foregoing issues.)
 In contrast, web applications use web documents written in a [[standard]] format such as [[HTML (Hypertext Markup Language)|HTML]] and [[JavaScript]], which are supported by a variety of web browsers. Web applications can be considered as a specific variant of client–server [[software]] where the client software is downloaded to the client machine when visiting the relevant web page, using standard procedures such as HTTP. Client web software updates may happen each time the web page is visited. During the session, the web browser interprets and displays the pages, and acts as the universal client for any web application.

@@ Line 126: / Line 126: @@
 [[Internet Protocol (IP)]]<br />
 [[Internet Reputation]]<br />
 [[Internet of Things (IoT)]]<br />
 [[Search Engine]]<br />

@@ Line 8: / Line 8: @@
 == History of Web Applications<ref>History of Web Applications [https://en.wikipedia.org/wiki/Web_application Wikipedia]</ref> ==
-In earlier computing models like [[Client Server Model|client–server]], the processing load for the [[Application|application]] was shared between code on the server and code installed on each client locally. In other words, an application had its own pre-compiled client program which served as its user interface and had to be separately installed on each user's personal [[Computer|computer]]. An upgrade to the server-side code of the application would typically also require an upgrade to the client-side code installed on each user workstation, adding to the support cost and decreasing [[Productivity|productivity]]. In addition, both the client and server components of the application were usually tightly bound to a particular computer architecture and [[Operating System (OS)|operating system]] and porting them to others was often prohibitively expensive for all but the largest applications. (Nowadays, native apps for mobile devices are also hobbled by some or all of the foregoing issues.)
+In earlier computing models like [[Client Server Model|client–server]], the processing load for the [[Application|application]] was shared between code on the [[server]] and code installed on each client locally. In other words, an application had its own pre-compiled client program which served as its user interface and had to be separately installed on each user's personal [[Computer|computer]]. An upgrade to the server-side code of the application would typically also require an upgrade to the client-side code installed on each user workstation, adding to the support cost and decreasing [[Productivity|productivity]]. In addition, both the client and server components of the application were usually tightly bound to a particular [[computer]] [[architecture]] and [[Operating System (OS)|operating system]] and porting them to others was often prohibitively expensive for all but the largest applications. (Nowadays, native apps for mobile devices are also hobbled by some or all of the foregoing issues.)
-In contrast, web applications use web documents written in a standard format such as [[HTML (Hypertext Markup Language)|HTML]] and [[JavaScript]], which are supported by a variety of web browsers. Web applications can be considered as a specific variant of client–server software where the client software is downloaded to the client machine when visiting the relevant web page, using standard procedures such as HTTP. Client web software updates may happen each time the web page is visited. During the session, the web browser interprets and displays the pages, and acts as the universal client for any web application.
+In contrast, web applications use web documents written in a [[standard]] format such as [[HTML (Hypertext Markup Language)|HTML]] and [[JavaScript]], which are supported by a variety of web browsers. Web applications can be considered as a specific variant of client–server [[software]] where the client software is downloaded to the client machine when visiting the relevant web page, using standard procedures such as HTTP. Client web software updates may happen each time the web page is visited. During the session, the web browser interprets and displays the pages, and acts as the universal client for any web application.
 In the early days of the Web, each individual web page was delivered to the client as a static document, but the sequence of pages could still provide an interactive experience, as user input was returned through web form elements embedded in the page markup. However, every significant change to the web page required a round trip back to the server to refresh the entire page.
@@ Line 16: / Line 16: @@
 In 1995, Netscape introduced a client-side scripting language called JavaScript allowing programmers to add some dynamic elements to the user interface that ran on the client side. So instead of sending [[Data|data]] to the server in order to generate an entire web page, the embedded scripts of the downloaded page can perform various tasks such as input validation or showing/hiding parts of the page.
-In 1996, Macromedia introduced Flash, a vector animation player that could be added to browsers as a plug-in to embed animations on the web pages. It allowed the use of a scripting language to program interactions on the client side with no need to communicate with the server.
+In 1996, Macromedia introduced Flash, a vector animation player that could be added to browsers as a [[plug-in]] to embed animations on the web pages. It allowed the use of a scripting language to program interactions on the client side with no need to communicate with the server.
-In 1999, the "web application" concept was introduced in the Java language in the Servlet Specification version 2.2. At that time both JavaScript and XML had already been developed, but Ajax had still not yet been coined and the XMLHttpRequest object had only been recently introduced on Internet Explorer 5 as an ActiveX object.
+In 1999, the "web application" concept was introduced in the Java language in the Servlet Specification version 2.2. At that time both JavaScript and XML had already been developed, but Ajax had still not yet been coined and the XMLHttpRequest object had only been recently introduced on Internet Explorer 5 as an [[ActiveX]] object.
-In 2005, the term Ajax was coined, and applications like Gmail started to make their client sides more and more interactive. A web page script is able to contact the server for storing/retrieving data without downloading an entire web page.
+In 2005, the term Ajax was coined, and applications like Gmail started to make their client sides more and more interactive. A web page script is able to contact the server for storing/retrieving [[data]] without downloading an entire web page.
 In 2011, HTML5 was finalized, which provides graphic and multimedia capabilities without the need of client side plug-ins. HTML5 also enriched the semantic content of documents. The [[Application Program Interface (API)|APIs]] and [[Document Object Model (DOM)|document object model (DOM)]] are no longer afterthoughts, but are fundamental parts of the HTML5 specification. WebGL API paved the way for advanced 3D graphics based on HTML5 canvas and JavaScript language. These have significant importance in creating truly platform and browser independent rich web applications.
@@ Line 27: / Line 27: @@
 == The Need for Web Application<ref>Why you need a Web Application? [https://www.guru99.com/difference-web-application-website.html Guru99]</ref> ==
 Web applications are more popular because of the following reasons:
-*Compared to desktop applications, web applications are easier to maintain by as they use the same code in the entire application. There are no compatibility issues.
+*Compared to [[desktop]] applications, web applications are easier to maintain by as they use the same code in the entire application. There are no compatibility issues.
 *Web applications can be used on any platform: Windows, Linux, Mac… as they all support modern browsers.
 *Mobile App store approval not required in web applications.
@@ Line 54: / Line 54: @@
 *Static Web Applications: The first thing to know a static web app is that this type of web application displays very little content and is not particularly flexible. Static Web Applications are usually developed in HTML and CSS but these are not the only platforms to develop the static app; you can use jQuery and Ajax as per your own convenience. You can also include or display animated objects, such as banners, GIFs, videos, etc. in the static app handily. Unfortunately, modifying the content of static web applications is not easy. To do this, you first have to download the HTML code, then modify it and finally send it back to the server. These changes can only be made by the webmaster or development company that planned and designed the first Application. Examples of the development of static web applications include professional portfolios or digital resumes. Similarly, a page presenting a company could also make use of this type of web application to display their contact information.
 *Dynamic Web Applications: Dynamic web applications are much more complex on a technical level. They use databases for data loading and its contents are updated each time the user accesses them. They usually have an administration panel (called CMS), where administrators can correct or modify application content, whether text or images. Different programming languages can be used for the development of dynamic web applications. PHP and ASP are the most common languages used for this purpose because they allow the structuring of contents. In this type of application, updating the content is very simple and the server does not even have to be accessed for the modifications to be made. Also, it allows you to implement an abundance of features, such as forums or databases. The project – in addition to content – can be modified to match the administrator preferences.
-*Shop Online Or E-Commerce: If the web application is an online store, its development is likely to resemble that of an m-commerce or e-commerce site. This type of application development process is more complicated because it must allow electronic payments that can be made from credit cards, PayPal or other payment methods. The developer must also create a management panel for the administrator; that will be used for the listing of new products, update them,  delete the entries, and to manage applications and payments. Your web application fits on mobile devices the same way as a mobile app does, making it possible to interact with it as if it were a native application.
+*Shop Online Or [[E-Commerce]]: If the web application is an online store, its development is likely to resemble that of an m-commerce or e-commerce site. This type of application development [[process]] is more complicated because it must allow electronic payments that can be made from credit cards, PayPal or other payment methods. The developer must also create a [[management]] panel for the administrator; that will be used for the listing of new products, update them,  delete the entries, and to manage applications and payments. Your web application fits on mobile devices the same way as a mobile app does, making it possible to interact with it as if it were a native application.
 *Portal Web App: Through the portal, we are referring to a type of application that accesses the various sections or categories through a home page. These applications can include many things: forums, chats, e-mail, browsers, areas accessed through registration, the latest content, etc.
-*Animated Web Applications: The animation is inevitably associated with Flash technology. This programming approach allows you to display content with animated effects. This type of application allows more creative and modern designs and is one of the key technologies used by designers and creative directors. The disadvantage inherent in the development of animated web applications is that this type of technology is not suitable for web positioning purposes and optimization of SEO because search engines cannot properly read the information they contain.
+*Animated Web Applications: The animation is inevitably associated with Flash technology. This programming approach allows you to display content with animated effects. This type of application allows more creative and modern designs and is one of the key technologies used by designers and creative directors. The disadvantage inherent in the development of animated web applications is that this type of technology is not suitable for web [[positioning]] purposes and optimization of SEO because search engines cannot properly read the information they contain.
-*Web Applications With A Content Management System: The content should be constantly updated when it comes to web application development so that the installation of a content management system (CMS) is a serious option to consider. The administrator can make use of this CMS to implement changes and updates alone. These content managers are intuitive and very easy to handle. Some examples of content management systems are:
+*Web Applications With A [[Content Management]] [[System]]: The content should be constantly updated when it comes to web application development so that the installation of a content management system (CMS) is a serious option to consider. The administrator can make use of this CMS to implement changes and updates alone. These content managers are intuitive and very easy to handle. Some examples of content management systems are:
 **WordPress: is undoubtedly the most widespread around content management. There is plenty of information, tutorials, and guides available on the internet that will help you customize it and understand how it works. Besides all this, it’s free.
 **Joomla: This CMS is second only behind the WordPress. It does not have as many users as the last, but has a strong community and is also very intuitive.
@@ Line 64: / Line 64: @@
 == Mobile Apps Vs. Web Apps<ref>Mobile Apps Vs. Web Apps [https://careerfoundry.com/en/blog/web-development/what-is-the-difference-between-a-mobile-app-and-a-web-app/ Career Foundry]</ref> ==
-Native [[Mobile Application|mobile apps]] are built for a specific platform, such as iOS for the Apple iPhone or Android for a Samsung device. They are downloaded and installed via an app store and have access to system resources, such as GPS and the camera function. Mobile apps live and run on the device itself. Snapchat, Instagram, Google Maps and Facebook Messenger are some examples of popular mobile apps.
+Native [[Mobile Application|mobile apps]] are built for a specific platform, such as iOS for the Apple iPhone or Android for a Samsung [[device]]. They are downloaded and installed via an app store and have access to system resources, such as GPS and the camera function. Mobile apps live and run on the device itself. Snapchat, Instagram, Google Maps and Facebook Messenger are some examples of popular mobile apps.
 Web apps, on the other hand, are accessed via the [[Web Browser|internet browser]] and will adapt to whichever device you’re viewing them on. They are not native to a particular system, and don’t need to be downloaded or installed. Due to their responsive nature, they do indeed look and function a lot like mobile apps — and this is where the confusion arises.
@@ Line 89: / Line 89: @@
 Web applications can provide the same functionality and gain the benefit of working across multiple platforms. For example, a web application can act as a word processor, storing information in the cloud and allowing you to 'download' the document onto your personal hard drive.
-If you've been using the web long enough to witness how popular web applications like Gmail or Yahoo mail clients have changed over the years, you have seen how sophisticated web applications have become. Much of that sophistication is because of AJAX, which is a programming model for creating more responsive web applications.
+If you've been using the web long enough to witness how popular web applications like Gmail or Yahoo mail clients have changed over the years, you have seen how sophisticated web applications have become. Much of that sophistication is because of AJAX, which is a programming [[model]] for creating more responsive web applications.
 G Suite (formerly Google Apps) and Microsoft Office 365 are other examples of the newest generation of web applications. Mobile applications that connect to the internet (such as your Facebook app, your Dropbox app or your online banking app) are also examples of how web applications have been designed for the ever increasingly popular use of the mobile web.

← Older revision		Revision as of 18:45, 17 January 2020
Line 1:		Line 1:
		+	== Definition of Web Application ==
	A '''Web Application''' aka web-based application is any program that is accessed over a [[Network\|network]] connection using [[Hypertext Transfer Protocol (HTTP)\|HTTP]], rather than existing within a [[Device\|device’s]] memory. Web-based applications often run inside a [[Web Browser\|web browser]]. However, web-based applications also may be client-based, where a small part of the [[Computer Program\|program]] is downloaded to a user’s [[Desktop\|desktop]], but processing is done over the [[Internet\|internet]] on an external [[Server\|server]]. Web-based applications are also known as web apps.<ref>Definition - What is a Web Application [https://www.techopedia.com/definition/26002/web-based-application Techopedia]</ref>		A '''Web Application''' aka web-based application is any program that is accessed over a [[Network\|network]] connection using [[Hypertext Transfer Protocol (HTTP)\|HTTP]], rather than existing within a [[Device\|device’s]] memory. Web-based applications often run inside a [[Web Browser\|web browser]]. However, web-based applications also may be client-based, where a small part of the [[Computer Program\|program]] is downloaded to a user’s [[Desktop\|desktop]], but processing is done over the [[Internet\|internet]] on an external [[Server\|server]]. Web-based applications are also known as web apps.<ref>Definition - What is a Web Application [https://www.techopedia.com/definition/26002/web-based-application Techopedia]</ref>
		+
		+
		+	[[File:Web_Application.gif\|500px\|Web Application]]<br />
		+	source: EduCBA

← Older revision		Revision as of 18:40, 17 January 2020
Line 43:		Line 43:
	*Web application server sends results to the web server with the requested information or processed data		*Web application server sends results to the web server with the requested information or processed data
	*Web server responds back to the client with the requested information that then appears on the user’s display		*Web server responds back to the client with the requested information that then appears on the user’s display
		+
		+
		+	== Types of Web Applications<ref>What are the Different Types of Web Applications? [https://www.clustox.com/6-different-types-of-web-application-development/ Clustox]</ref> ==
		+	This classification is based on how web apps show the content they accept. Based on this, we have up to 6 different types of web applications.
		+	*Static Web Applications: The first thing to know a static web app is that this type of web application displays very little content and is not particularly flexible. Static Web Applications are usually developed in HTML and CSS but these are not the only platforms to develop the static app; you can use jQuery and Ajax as per your own convenience. You can also include or display animated objects, such as banners, GIFs, videos, etc. in the static app handily. Unfortunately, modifying the content of static web applications is not easy. To do this, you first have to download the HTML code, then modify it and finally send it back to the server. These changes can only be made by the webmaster or development company that planned and designed the first Application. Examples of the development of static web applications include professional portfolios or digital resumes. Similarly, a page presenting a company could also make use of this type of web application to display their contact information.
		+	*Dynamic Web Applications: Dynamic web applications are much more complex on a technical level. They use databases for data loading and its contents are updated each time the user accesses them. They usually have an administration panel (called CMS), where administrators can correct or modify application content, whether text or images. Different programming languages can be used for the development of dynamic web applications. PHP and ASP are the most common languages used for this purpose because they allow the structuring of contents.
		+	In this type of application, updating the content is very simple and the server does not even have to be accessed for the modifications to be made. Also, it allows you to implement an abundance of features, such as forums or databases. The project – in addition to content – can be modified to match the administrator preferences.
		+	*Shop Online Or E-Commerce: If the web application is an online store, its development is likely to resemble that of an m-commerce or e-commerce site. This type of application development process is more complicated because it must allow electronic payments that can be made from credit cards, PayPal or other payment methods. The developer must also create a management panel for the administrator; that will be used for the listing of new products, update them, delete the entries, and to manage applications and payments. Your web application fits on mobile devices the same way as a mobile app does, making it possible to interact with it as if it were a native application.
		+	*Portal Web App: Through the portal, we are referring to a type of application that accesses the various sections or categories through a home page. These applications can include many things: forums, chats, e-mail, browsers, areas accessed through registration, the latest content, etc.
		+	*Animated Web Applications: The animation is inevitably associated with Flash technology. This programming approach allows you to display content with animated effects. This type of application allows more creative and modern designs and is one of the key technologies used by designers and creative directors. The disadvantage inherent in the development of animated web applications is that this type of technology is not suitable for web positioning purposes and optimization of SEO because search engines cannot properly read the information they contain.
		+	*Web Applications With A Content Management System: The content should be constantly updated when it comes to web application development so that the installation of a content management system (CMS) is a serious option to consider. The administrator can make use of this CMS to implement changes and updates alone. These content managers are intuitive and very easy to handle. Some examples of content management systems are:
		+	**WordPress: is undoubtedly the most widespread around content management. There is plenty of information, tutorials, and guides available on the internet that will help you customize it and understand how it works. Besides all this, it’s free.
		+	**Joomla: This CMS is second only behind the WordPress. It does not have as many users as the last, but has a strong community and is also very intuitive.
		+	**Drupal: it is a free CSM software – very adaptable and is especially recommended for building communities. This type of web applications is very common among the content pages: personal blogs, corporate blogs, professional blogs, news pages, articles, media, etc.