Talk:Web application

Rewrite

Good job on the rewrite and merging from "browser-based". However, I am a bit concerned about the following sentence:

Because of their architectural similarities to traditional client-server applications, with a somewhat "thick" client, there is some dispute over whether to call systems of this sort "web applications"; an alternative term is "rich internet application".

It would be a good idea to provide a source for this dispute. Flash and Java applets are indeed applications delivered over the web, with code updates made only on the server-side (with the rare exception that a plug-in or JRE needs to be upgraded to a particular version, but this applies to any web applications that may utilize their resources). With no need for traditional client distribution, I don't see how they can be seen differently from a web application. One could compare the web browser to common plug-ins and the JRE (which merely make the thin client a little thicker), as being tantamount to OS fixtures, as they are so ubiquitous.

I am not looking for a back-and-forth argument here and these will be the last words I say on the matter. But I will be looking for a source. Thanks. — Stevie is the man! ^{Talk | Work} 21:43, Jun 18, 2005 (UTC)

That sentence was based on conversations I've had with people who either work or teach in the field, so I don't have any print or web source to cite. Their argument was that a well-designed client-server system can update a thick client transparently over the internet in much the same way as you'd update a cached Java applet (what MS is trying to do with Windows Update), the difference between a browser-executed app and an OS-executed app is arbitrary (see DoJ vs. MS), and some of those "applets" get pretty darn chubby. The disinction's getting blurrier; I was trying to acknowledge that, instead of simply asserting my own position (that a browser-executed Flash app is just as much a web app as anything done with HTML & Javascript). In retrospect, "disgreement" would be better than "dispute", because no one in any of these conversations lost their temper. :) Tverbeek 23:40, 18 Jun 2005 (UTC)

It appears that a potential rewording lies in the words you use to your response here. Clarity is a Good Thing (TM). — Stevie is the man! ^{Talk | Work} 00:15, Jun 19, 2005 (UTC)

wikipedia as example

I would think readers unfamiliar with the subject would find it interesting to be reminded that wikipedia itself is an example of a web app. Is there any reason why it's not mentioned here as a particularly relevant illustration (and in the Application Service Providers article)? ["wiki" is mentioned very briefly in a passing list near the top, but doesn't really make the point with any impact.]

Distinct from Hybrid Web App

I think the "Redirect From: Hybrid App" is incorrect. To be clear, I think this webapps page is fine in and of itself.

Currently (March 1 2023) the Hybrid app article is a simple redirect to here, Web app.

Rationale: While hybrid apps are built WITH web app technologies, sometimes only in part. They ALSO include native (local device) adapters to render those webapps using local resources. Typically (circa 2023, in my personal experience as a vet software engineer) Hybrid apps are found on personal computing devices, and generally include an HTML renderer/JS runtime/native-API (not specified by W3C standards) binding layer - whereas web apps are typically found on dedicated servers and their JS / rendered content conform strictly to Web standards.

So Hybrid apps are a kind of web app, however they are distinct in that they are not necessarily intended to operate on the internet, and do provide added APIs Ncr100 (talk) 16:58, 1 March 2023 (UTC)

I agree. A redirect to Mobile_app#Hybrid_app would be a better destination. PaulT2022 (talk) 18:18, 1 March 2023 (UTC)

Semi-protected edit request on 1 December 2023

Change "Traditional PC applications consist only of 1 tier, which resides on the client machine, but web applications lend themselves to a multi-tiered approach by nature." to "Traditional PC applications are typically single-tiered, residing solely on the client machine. In contrast, web applications inherently facilitate a multi-tiered architecture." Travis-g-reid (talk) 01:10, 1 December 2023 (UTC)

 Done Lewcm Talk to me! 09:30, 8 December 2023 (UTC)

"Webware" listed at Redirects for discussion

The redirect Webware has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2024 January 26 § Webware until a consensus is reached. Shhhnotsoloud (talk) 12:01, 26 January 2024 (UTC)

Edit request

Please add to the intro:

Web applications are collectively known as webware.

References

This will support the incoming redirect Webware properly.

-- 65.92.247.66 (talk) 05:19, 17 February 2024 (UTC)