@mathix maybe you can make it clear on the website that this doesn't create app/play store apps, as most people probably think about them when they read "turn any website into an app".
From the github readme[0]:
> FTWA uses the --app='https://app.example' parameter with Chromium-based browsers to launch a website in "app mode".
> [...]
> When choosing linux as target OS, FTWA generate a shell script that will create a .desktop file and it's icons.
* The Firefox (BETA) entry does not work on default Ubuntu installs, where Firefox is a Snap. Yes, snap bad, bla bla bla, but it still remains one of the most likely way Firefox will be installed on Ubuntu. This comes from the fact that your script attempts to locate the profile folder in ~/.mozilla/firefox, whereas snaps stores them in ~/snap/firefox/common/.mozilla/firefox/.
* New profiles unfortunately don't share logins on Firefox, which means your app is disconnected at first. Not a big deal, but could maybe be changed by copying some things from the default profile ?
* Firefox does not display _any_ titlebar when ran in this way.
Love the idea. There's many times where I'd like something to have a bit more "privilege" on my toolbar than what a regular tab (even pinned) gets.
Since Mozilla has started to provide an official Debian-style repository there is no reason to use snap on Ubuntu any more. Well, except if some users don't know or don't care to switch.
Thank you, I just followed these [1] instructions and couldn't be happier getting rid of the snap!!! Before upgrading I was running a binary release from firefox, but running mozilla apt repo is much preferred!
>there is no reason to use snap on Ubuntu any more. Well, except if some users don't know or don't care to switch.
Also known as "90% of your users". Defaults stick, and there's nothing bad enough about snaps that i'd waste time of my day adding the debian repo, trying to switch my profiles over, etc.
One aspect is that the server side is not free software. So only Canonical can reasonably host a repo of snaps.
That was enough for me not to look into the technical merits of the clientside implementation. The few experiences I had with snap was that programs were starting slowly (Firefox) and e.g. GPU acceleration did not work (vlc). Not sure how good the sandboxing is. But I run my Firefox sandboxed by firejail and the overhead can not be felt in daily usage.
Ubuntu has replaced the deb version of Firefox with Snaps a few times on my computer.
On at least 3 occasions, I became aware of this when I would open Firefox and nothing would happen, except a message that "Firefox is already running". The only resolution was to install the deb Firefox package.
A couple months ago, I needed to do a fresh install since my system got borked during the upgrade to 24.04 LTS. As usual, the Firefox snap package was installed, so I decided to give it a try.
To its credit, it actually works this time. However, it will not save images on right click or open Zoom meeting links in the desktop client. I am fairly certain this problem would disappear if I switched back to the deb package, but it's not a big enough hassle for me to bother. I can live with some workarounds for now.
Overall, I don't mind snaps, but the Firefox snap has been far more trouble than it's worth.
- Yes I could create a second firefox preset for snap installs
- I would prefer not to touch such sensible files, but will give instructions on how to do it manually
I had written a similar program (but very barebone compared with what you've made), with Firefox only. The way I dealt with profile, is to specify the full path of the profile, rather than a name. This way, I don't have to know where Firefox is searching for profiles, and I can keep all the additional profiles in a separate directory, so they don't mix with normal profiles and don't clog up profile manager.
I just switched to Firefox and struggled with this exact functionality. The posted site ships a script for curl|sh that creates a new firefox profile with a custom userChrome.css.
I ended up writing a firefox extension to open up URLs in a new "popup" window[1]: https://addons.mozilla.org/en-US/firefox/addon/web-app-maker.... I just checked it on Windows (usually using linux) and the popup window type does not allow the maximize button to work. Oh well...
There's an excellent extension that makes this pretty simple to manage. Additionally the windows it creates have some pwa specific settings, like how links should be handled.
For people who want a "separate window" on Chrome osX (at least), you can go on the website, click on the "..." next to your profile picture, then "Cast, save and share" > "Install website as app"
It does the same, but runs as a "separate app" so that cmd+Q only exits the app
Yes, it's pretty much the same for macOS I guess. On linux it's pretty different, I was using .desktop files over PWAs for years because of their bad UI on Linux.
So I did this, turned out it's not only just Firefox without the browser UI, but it also bricked my actual Firefox browser and now it doesn't connect to the internet.
I would like to have the complete opposite. Turn any app into a website so that I don't need to download them, and can just access them through my browser.
1. Does this make the apps show up as separate windows in Alt+Tab and a Dock etc? (FWIW I use GNOME + Dash to dock + Wayland)
2. Let's say you have a mail app and you click a link. Does that link open in the separate default browser?
I remember trying these command line options for Brave/Chrome, but I couldn't find a way where both of the above were working and thus they didn't feel like proper apps. I've only been using this for something like Apple Music, where I never click on any link that takes me outside. For everything else, like mail and notes, I've been using pinned tabs, but that feels suboptimal too.
2. This could do the trick for you https://askubuntu.com/a/251738/1163389 make it point to the desktop file that ftwa created in this folder: ~/.local/share/applications
This was just a side project, I was using .desktop files to launch some websites and thought it was still pretty unknown by most people. So I created this website.
Why did you build this with a server? Since you suggest folks introspect the script anyway, you could simply generate it in the browser and have the user download it. Then you could run this at zero-cost.
This is really cool! Any chance of adding support for the Arc browser? Right now, Chrome allows for some websites (WhatsApp, Spotify, YouTube Music) to be made into "apps" already via PWAs. Arc - which is based on chromium, for some mysterious reason, chooses to not support PWAs so this would be extremely useful for Arc!
@mathix maybe you can make it clear on the website that this doesn't create app/play store apps, as most people probably think about them when they read "turn any website into an app".
From the github readme[0]:
> FTWA uses the --app='https://app.example' parameter with Chromium-based browsers to launch a website in "app mode".
> [...]
> When choosing linux as target OS, FTWA generate a shell script that will create a .desktop file and it's icons.
[0]: https://github.com/mathix420/free-the-web-apps?tab=readme-ov...