what's wrong with the web app

In my experience web apps are almost always worse than native apps unless the native app is just a wrapper around a web app.

▲

mathiaspoint 3 days ago | parent | next [-]

The native Spotify app is just a wrapper around the web app though.

	▲	bigstrat2003 3 days ago \| parent \| next [-]
		Even for apps where that is true, sometimes the wrapper adds some features that it doesn't have running in a browser tab. For example, the Discord electron app can get hotkeys when it's not focused (useful for push to talk/mute when playing a game), but not when you run it in a browser.
	▲	lproven 2 days ago \| parent \| prev \| next [-]
		> a wrapper around the web app All Electron apps are.
	▲	sneak 3 days ago \| parent \| prev [-]
		This is decidedly untrue.

▲

makeitdouble 2 days ago | parent | prev [-]

It is generally true regarding the intent of the platform owner (the app is supposed to be better, they'll put efforts into it).

The funny part being, you might still want the web version to apply extensions on it. Youtube for instance is a lot better with the auto-dub features and title translations off, but it won't be possible in the native app as Google is actively forcing those on us. I don't use Spotify, but would advise looking it it.

	▲	umbra07 2 days ago \| parent [-]
		Spicetify offers a much better experience than web+extensions. And of course, you can use alternate, lightweight clients based on 'librespot' instead.

▲

olyjohn 3 days ago | parent | prev | next [-]

It doesn't show up as a separate task. I have to go to Firefox and find the window. It's not as easy as an alt-tab and gets lost in all my other web apps that are in my browser.

	▲	blibble 2 days ago \| parent \| next [-]
		Chrome+Firefox support pulling tabs out as individual apps, with a separate window icon + launcher well, Firefox did, until Mozilla (of course) removed it Chrome still supports it
	▲	makeitdouble 2 days ago \| parent \| prev [-]
		Secunding blibble's comment, the wrapper mode works fine in Chrome, and links will open in the standard Chrome instance so there is little downsides UX wise. Extensions aren't as accessible if you use them a lot, and of course you're stuck with Chrome though.

▲

rossdavidh 3 days ago | parent | prev | next [-]

to be honest I don't know, I don't use Spotify much, but apparently for my wife it was a dealbreaker so I gritted my teeth and dived in, but then as I recall it was actually not hard to install at all. HOWEVER, IIRC, it involved typing something into a terminal¸ and for a lot of people that is also a complete dealbreaker for whatever reason.

▲

akimbostrawman a day ago | parent | next [-]

You don't need to type anything into a terminal with gnome and KDE software center supporting snaps and flatpaks which make installing proprietary software as easy as anything else.

▲

asoneth 2 days ago | parent | prev | next [-]

> for a lot of people that is also a complete dealbreaker for whatever reason

Seems like a perfectly reasonable dealbreaker to me. Terminal commands are a raw UI that is neither intuitive nor discoverable -- someone must either read documentation (man pages, tutorials, blog posts, etc) to learn the behavior and syntax or they must blindly copy strings from a trusted source.

There's a reason most stories of nontechnical people using software like Linux always seem to include an expert friend, family member, or IT person in the background.

▲

umbra07 2 days ago | parent | next [-]

Of course, it's not 'intuitive', but I firmly believe that the actual process of using just about any CLI package manager is easier to use than a GUI-installer approach. By "easier" I mean more streamlined, and a more standardized process. Every single time I install a piece of software on my machine with my package manager, I do it exactly the same way, with literally zero different steps taken. The same cannot be said for GUI-based installers. Surely the former would be a better experience for most home PC users?

	▲	asoneth 2 days ago \| parent [-]
		I think it depends on how you define "easier". Once someone learns how to use the requisite terminal commands and does so frequently enough that they do not forget them, I agree that it is significantly faster and more consistent. > Surely the former would be a better experience for most home PC users? Our experiences with home PC users must be qualitatively different. I have trouble getting the PC users I help to remember the name of their web browser or to understand the difference between a webpage and an application. And of the few people I know who might be able to learn how to use the terminal, none have the slightest interest in devoting time to doing so -- they would prefer to use their computer time doing actual work or playing computer games than wasting it learning how to do computer admin tasks more efficiently. The prospect of teaching anyone but a fraction of a fraction of a percent of PC users to successfully run terminal commands seems so removed from the realm of possibility I have trouble imagining it. Maybe I could see it catching on with an LLM as an intermediary to actually structure the commands?

▲

rossdavidh 2 days ago | parent | prev [-]

You're not wrong, but in this case I believe all I had to do was copy the line of text and paste it into a terminal (it's a while ago so I might be misremembering). But, given that is what people are doing, it does raise the question of whether requiring them to copy and paste is actually any more secure than allowing click-to-install...

▲

asoneth 2 days ago | parent [-]

> whether requiring them to copy and paste is actually any more secure than allowing click-to-install...

Agreed. If your operating system requires that you occasionally search for instructions and copy-and-paste executable strings from the internet, that seems less efficient, less learnable, and less secure than any GUI I know of.

Perhaps at some point terminals will bake in an LLM as an intermediary to convert between human-readable instructions and terminal commands, and then we just have to worry about the alignment of those LLMs...

▲

lproven 2 days ago | parent [-]

There are 2 things here to note which explain why.

* Most distros offer multiple desktops. This is true of Debian, Ubuntu, Fedora, openSUSE, Arch, etc.

Point-and-click instructions are limited to only 1 desktop. Shell instructions work on all of them.

* GUI instructions can't be copied and pasted. They must be performed by the user. But most people do not know the difference between buttons and spinners and input boxes. It's very very hard to write specific instructions for people who lack the vocabulary for GUI controls.

I speak as a former docs writer.

▲

asoneth 2 days ago | parent [-]

> Point-and-click instructions are limited to only 1 desktop...

If a consumer product (computer, phone, TV, microwave, printer, radio, oven, washing machine, etc) requires reading through more than a quick start guide to access the advertised functionality, then it has failed as a consumer product.

> GUI instructions can't be copied and pasted

Training my nontechnical friends and relatives to copy, paste, and execute terminal commands they found on the internet does not strike me as a very good alternative.

▲

lproven 2 days ago | parent [-]

Your comment is correct but it's a response to an entirely different and orthogonal point which I did not propose and wouldn't try to.

As such I can answer in several different ways which try to approach the point you're making, but they can only do it by trying to nudge your comment slightly back in the direction of "how things really are".

Point 1:

Why what you're saying does not address the real situation.

The thing is that about 99% of Linux distributions are not products.

They are the collaborative efforts of many small teams of volunteers. In rare instances, a few of them are collaborative efforts of large teams of paid engineers. However most of those are server OSes where UI is not a factor.

(The real competitive criteria of paid server distros are things like "what certifications do you have?" and "how long will you provide patches for?" They're nothing to do with its technical capabilities. That's why the paid enterprise distros are much smaller, much simpler, and technologically far inferior to free ones.)

They are not products, and they are definitely not CONSUMER products.

Point 2:

How to do easy end user 3rd party apps on Linux: prohibit them.

There is an easy answer to the question of "software installation on a consumer Linux desktop." There's only one consumer Linux desktop. It's ChromeOS. And you can't install native software. There is no native software.

(Some ChromeBooks can run Android apps but they are not native.)

Note, this product outsells all free distros by, conservatively, 10-20x over.

So this is clearly not a handicap.

Point 3:

Docs are really hard and don't pay.

I've written product documentation as my paid full-time job for 4-5 years.

Nobody reads it by choice, and it's expensive to produce, which is why consumer products mostly don't come with any now. You may get a quick-start guide and most customers ignore that.

This is why the only desktop Linux with users in the hundreds of millions is so stripped-down you can't install apps on it.

Point 4:

The real context here.

Given these aren't products and aren't for consumers, what we get is sub-optimal but it really is not bad these days.

	▲	asoneth 9 hours ago \| parent [-]
		> Your comment is correct but it's a response to an entirely different and orthogonal point which I did not propose and wouldn't try to. You're right, I was mixing up threads, I apologize. Your original point seems to be that it's less effort for a Linux distribution to write documentation for shell commands than for them to create a GUI and write the same level of documentation for that GUI, right? If so, I agree, and I understand why a volunteer-driven project would take this route. However, two points: First, a properly-designed GUI should require less documentation in the first place. More importantly, I don't see how this refutes my original point that running shell commands copied from the internet is less efficient, learnable, and secure for end-users than using comparable functionality through a GUI. Again, I understand why distros take this route, I'm merely pointing out that it is less efficient, learnable, and secure. With respect to the four points in your last post I agree so I'm not sure there's much worth discussing there.

▲

lproven 2 days ago | parent | prev [-]

I wonder what OS you were trying.

For most, it would be:

1. Open the app or software store

2. Type "spotify"

3. Click "install"

If it doesn't, then it's not a distro for non-techie end-users.

▲

estimator7292 3 days ago | parent | prev [-]

It locks out a bunch of features