This is the talk page for discussing improvements to the Progressive web app article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
This article is rated B-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||
|
Firefox Nightly has decent support for service workers too. Might we worth mentioning that.
Firefox Nightly is a moving target, as the name implies. What features it has, change from one day to another. Eventually, all the browsers should support this, in a consistent way.OsamaBinLogin (talk) 17:36, 20 August 2017 (UTC)
Links to CanIUse and Is Service Worker Ready? are better than listing support for features by browser.
Correct me if i'm wrong but has the term "Progressive web app" been hijacked?
A progressive web application for me used to mean an application that provides more features depending on whether it was supported by the user's device / browser. i.e progressive enhancement.
We have always had progressive web applications by implementing new features when supported / possible.
For example, detecting whether the user's device has a camera and providing a feature that uses it.
It still applies to providing the ability for an application to have a native app look and feel but developing web applications specifically for native-like experiences is not the definition of a "progressive web app" in my books.
Maybe I should be using the term "Progressively Enhanced Web App" instead?
In either case my two cents would be that the definition of a 'Progressive Web App' is not limited to supporting native experiences. — Preceding unsigned comment added by 216.191.98.58 (talk) 19:36, 20 May 2016 (UTC)
Yes, progressive enhancement is the term I've seen. — Preceding unsigned comment added by 2601:647:4C01:B39A:9596:7E7E:1022:8AAE (talk) 08:44, 22 July 2017 (UTC)
yeah, it's been hijacked. It has a general meaning, like you say, a web app that's progressive, using the latest features, any given year's features.
Rich Internet Applications (RIA) is an older name for a standalone app that's internally implemented using "web" technology - although really they seemed to use proprietary platforms like Shockwave Flash or Silverlight that are typically used in web pages.
HTML5 includes features that start to work towards having standalone apps implemented but as of this writing (aug 2017) they're not ready for prime time. That is what they're talking about in this article. I'll try to make some corrections. OsamaBinLogin (talk) 17:36, 20 August 2017 (UTC)
No, it hasn't hijacked the term. "Progressive web app" is a new term, coined in 2015 and gained momentum in 2016. It is related, but not the same as "Progressive enhancement" which are sites that improve certain aspects given that the browser supports the required technology. If the browser doesn't, the site will still have the features, but in cruder manner. The first example I can think of is Gmail which you can use with javascript turned off unlike many sites the require javascript or they will not do anything at all. And PWA is more than just looking like a web app. It's technology that allows the web app to, amongst other things,
--139.112.164.36 (talk) 07:53, 22 August 2017 (UTC)
What does the green background mean on some of the apps in the 2 lists near the bottom? Nick (talk) 00:04, 13 October 2017 (UTC)
"Since around 2005 web development technologies have shifted from static to dynamic web pages driven by server (PHP, ASP.NET) or client side ( Ajax[1] ) tools, and responsive web design.[2]"
Where does 2005 come from? Even in the linked article by Ethan Marcotte I can't see a clear statement about when such "shift" occurred. I can't think of any mainstream website in the late 90s which didn't heavily rely on server-side scripting.
Kijuhy (talk) 14:27, 4 January 2019 (UTC)
I removed the table of benchmark scores for the following reasons:
1. There are too many PWAs online to list all of them in the article 2. WP:N The PWAs in the list do not meet requirement of Notability because they lack any independent coverage 3. WP:NOR The whole list is not verifiable because it is original research 4. The benchmark scores fluctuate a lot widely as tests are changed, added, or removed. The results are not verifiable. 5. The whole table is not useful to anyone for all the aforementioned reasons.
The page might benefit from a list of notable businesses and services that offer PWA. — Preceding unsigned comment added by Anton.bersh (talk • contribs) 18:36, 11 April 2019 (UTC)
It would be beneficial to include the term "apps" in the lede. While web applications are not the only form of apps, for the general reader there is usually not an understanding that web and native applications are the "apps" that they are most familiar with.
I propose the following (changes in bold) for the lede to make this relationship clear without confusing the technical specifics:
Progressive web applications (PWAs) are web pages or websites that function as web applications, with an experience identical to a native application on a mobile device. Functionality includes working offline, push notifications, and device hardware access. While both PWAs and native applications can function as mobile apps, with PWAs there is no requirement for developers or users to go through digital distribution systems like the App Store or Google Play.
- Seazzy (talk) 14:21, 23 May 2019 (UTC)
The article needs some editing to fix factual errors. E.g., it states "At the launch of the iPhone in 2007, Steve Jobs announced that web apps, written using Web 2.0 and AJAX (later known as HTML5), would be the standard format for iPhone apps," however (1) Web 2.0 is not a technology, rather an idea that web should be more "social" and focus on user-generated content and (2) AJAX is a architecture of building pages that can update without full page reload and (3) HTML5 is an actual standard/technology.Anton.bersh (talk) 17:41, 23 May 2019 (UTC)
The technologies section has a number of subcategories that both have no citations and have only one or two sentences describing their relevance. I propose condensing them under an "Other technologies" subcategory. These would include: PouchDB, RxDB, GunDB, Hood.ie and any subsequent technologies that have some relevance but do not warrant a full subsection.
I would also recommend removing the web worker subsection entirely, as the service worker is a type of web worker that is a PWA requirement. - Seazzy (talk) 20:40, 10 June 2019 (UTC)
Would it be useful to add Template:HTML to the article? I'm not well versed in template usage, but if it's possible to add new technologies to the template, PWAs would probably deserve a spot. Does anyone want to take this task on? -Seazzy (talk) 15:13, 11 June 2019 (UTC)
The article mentions “served via HTTPS” as a characteristic.
For nearly a decade, HTTPS is actually the default of many websites, no matter whether progressive web applications or ordinary HTML websites.
I am not implying that the point should be removed from the article, I am just noting that it is not a special distinction. -Handroid7 (talk) 12:58, 20 August 2019 (UTC)
Discord lacks a PWA (progressive web app), yet is mentioned in the “Example” section of the article. I think it should be removed Fmpgri (talk) 08:53, 26 August 2019 (UTC)
Previously[1] article contained a list of random wrappers around Indexed Database API. I removed it as per "Wikipedia is not a directory"[2]. This list was not supported by any third-party sources (it just linked to libraries' own web pages) and wouldn't be useful to anyone because it contained a rather random selection of libraries.
[1] https://en.wikipedia.org/w/index.php?title=Progressive_web_application&type=revision&diff=968118201&oldid=964630558 [2] https://en.wikipedia.org/wiki/Wikipedia:What_Wikipedia_is_not#Wikipedia_is_not_a_directory --Anton.bersh (talk) 11:35, 17 July 2020 (UTC)
Can we add a link to the W3C working group: https://www.w3.org/2019/webapps/ I think it's important to show where the official specifications are for making all these things work together. GlenPeterson (talk) 19:54, 30 October 2020 (UTC)
As per this Bugzilla comment here > https://bugzilla.mozilla.org/show_bug.cgi?id=1682593#c8, and this bug here > https://bugzilla.mozilla.org/show_bug.cgi?id=1407202. Mozilla has offically ended support for PWAs in Firefox Desktop.
Am I allowed to do relevant edits to the article to state this?
2404:E80:81D7:0:2483:3FB8:171F:D2B2 (talk) 07:33, 27 January 2021 (UTC)
If Firefox does allegedly not support progressive web applications, how come Twitter's site works according to my testing?
Maybe polyfills should be mentioned?
Devon the webdev (talk) 22:00, 30 June 2021 (UTC)
Why does this page still exist? It promotes the spread of spam and malware and should be merged with either of those pages. -- 143.178.44.253 (talk) 00:12, 1 September 2021 (UTC)
Apparently my edit has been removed because of this source. What was wrong about it? It does not promote any company, but just describes technical things.
Is it even necessary to add a source to the statement that progressive web apps increase outreach? It is obvious considering no installation is needed, as stated at the beginning of the article, therefore one less barrier.
Gentritgerlach (talk) 21:38, 15 September 2021 (UTC)
"As of 2021, PWA features are supported to varying degrees" For SW development, a table referring to 2021 in 2024 seems badly outdated. MJost (talk) 08:51, 10 April 2024 (UTC)