Service Workers, push notifications and such are still supported.
And I believe you can install PWA:s on Firefox for Android?
Service Workers, push notifications and such are still supported.
And I believe you can install PWA:s on Firefox for Android?
Which is fine. The Single-Site Browser experience, putting an icon on the desktop that opens a browser with no url bar, extensions, back button, or any of the other features of the browser, isn't actually good. There's a better way to approach web apps with notifications and offline support.
I would consider being able to install the app to the homescreen part of having a "native app-like user experience". And installing to homescreen is listed as part of PWA on that MDN page.
There's some more relevant discussion on this bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1407202
For now you can supply --ssb on the command line - but I suppose that will go away, if the feature discussed in op is axed (it's not entirely clear to me if axing the pefrence/feature flag includes axing the command line flag - but it seems so).
At any rate - most desktop os' should allow shortcuts to urls - so should support "installing" apps.
That's just part of it though. What about hiding browser chrome, or making sure it opens as a new window instead of a new tab, or having seperate window preferences (such as size and location) for it? And I believe one goal of PWA is that "installed" apps have additional permissions, such as being able to use keyboard shortcuts that are normally reserved.
Pretty much: Have a Service Worker and/or a Web Manifest and you are well on your way to claim to have a PWA
> If there is some hard data somewhere we've missed that shows we would gain more market share by implementing [SSB] than other projects then that would sure be useful though!
This is a rare opportunity for everyone on HN disappointed about this removal (myself included) to put together a convincing argument with data about how important PWA desktop integration could be. The pessimist in me thinks there's just going to be more derision and complaints without action though. Hoping to be proven wrong.
So the “mobile Firefox” there isn’t really a mobile Firefox just the desktop browser used in a mobile context? Or does Mozilla support such platforms in any official way?
Even the Android Firefox app just got fairly recently rebuilt, mobile isn’t really Mozilla’s strong game after they shut down Firefox OS (which though strangely lives on as KaiOS)
Also: Both Android and Jolla are also Linux based
AFAIK the kernel plays practically no role in how a browser works.
On your comment though: I think maybe MacOS Big Sur disagrees with you: https://twitter.com/voxpelli/status/1343323353294262272?s=21 Not sure if kernel level or other level, but it sure has made eg VS Code pretty slow for some people ;)
And I thought some of the comments in the Bug Tracker were quite hostile.
It would be nice to not have 80+ slightly different chrome installs on a desktop for all the apps these days.
Shipping just the app code and using the runtime (edge or chrome i guess, would've been nice to have firefox as a modern xulrunner successor) on the end users machine makes more sense to me.
"WebApp Manager" uses the Chrome/Chromium/FF installed on your machine and creates a separate browser profile for each "WebApp" you configure and launches the "app" or "site-specific browser" in a new window. Details: [2][3]
Works well for simple sites where you're mostly visiting links in the same site, like Youtube.
[1] https://youtu.be/UCzL8P3WDd4?t=407
[1] https://github.com/linuxmint/webapp-manager/blob/4a879d11ef2...
also chakra that could've been close to that is deprecated.
basically if nobody provides an up to date hostruntime package, it will be the same case as it is now.
It's why I liked Microsoft's HTA (HTML Application) approach:
https://docs.microsoft.com/en-us/previous-versions/ms536496(...
https://docs.microsoft.com/en-us/previous-versions/ms536495(...
https://en.wikipedia.org/wiki/HTML_Application
It had lots of potential but never really took off. Looking at Sciter[0] as a lightweight Electron alternative (and a modern HTA replacement).
Especially considering that old versions of Chromium are likely to have more security vulnerabilities.
On the iOS platform, Apple essentially forbids the use of any browser engine other than the WebKit/Nitro engine provided by the OS itself. From the user's point of view this has the advantage of guaranteeing the absence of old and vulnerable browser engines on their system (provided they're up to date with iOS updates, and of course provided Apple hold up their end and maintain their software well).
As AnIdiotOnTheNet points out, this requires app vendors to stay on top of testing their app as the iOS browser engine is updated by Apple.
I understand people don't care about supporting multiple version of the runtime, but there should be a way to reduce the cruft of multiple bundled Chromiums on systems that might have storage constraints (thanks Apple and soldered SSDs)
(don't get me wrong: this is a wonderful technical feat, but it still is a substantial tradeoff from a native binary).
Chrome already supports it. You can install eg Twitter or GitHub Codespaces locally and they will appear as apps on your desktop system.
Chrome supports it on windows.
Certainly can't work on mobile platforms where everything is sandboxed.
IMO, the UX was horrible. I tried to keep Slack as a pinned Firefox tab, but it was far too easy to accidentally move over to a different website, at which point I stopped getting notifications. I also felt like I had to constantly keep my web browser open—I can't say why that's substantially different than having to keep a Slack application open, but for some reason, the separate dock icon helps me to mentally compartmentalize.
When I finally switched to a standalone Slack app, it felt much nicer.
I've been on Linux for a while now and have not come across the word shareware in a long time. Odd the it makes me feel nostalgic and (oddly) hopeful (that is: a business model that doesn't rely on tracking, ads or some nebulous behind the scenes actions to monetize you).
Nice, straightforward, simple business transaction. Software sales (especially shareware) is really tough. Wish the author some success for his efforts.
It'll check for updates on launch, performing a single HTTP request, but if you really like you can disable that with an environment variable on first launch and a configuration option going forward.
We need more software like this, honestly. I hate how we as users have to depend on enormous multinational entities to get back the privacy we once had. I happily paid for my Ripcord license and I'd recommend it to anyone else who cares about the same things I do :)
This is precisely why Firefox should support adding websites as desktop apps.
Electron is Chromium. Anyone who installs Slack as a desktop app is using Chromium. The more people who use Chromium, the less incentive Slack has to make their website compatible with anything which isn't than Chromium, which is presumably why you can't, for instance, make Slack calls in a browser other than Chrome or Edge.
If the purpose of Firefox is to give Mozilla a say in the direction of the web, they should be supporting and encouraging users to install websites as "apps" through Firefox.
Granted, I could always have that tab in a separate window, but that groups it with other Firefox windows, making it harder to navigate to when compared to PWA.