Live data from Hacker News

Fastpotify

fastpotify.rocks

481–490 of 584 posts

Re: Fastpotify

#481
post #238

Spotify is, without doubt, the worst piece of software that I still use on a daily basis. It's incredibly buggy, incredibly slow, and the UI has so many "usability inconsistencies". I find the Android app particularly bad, just a couple of examples: - Under a playlist you get a list of suggested songs, the UI element looks like a "regular song", but unlike every other "song" element the user has been trained to recog…

It truly has been one of the worst UX experiences and poorly made apps that ever made it to mainstream. I remember a decade or so ago there being a bunch of buzz about them in software dev because they were a microservice node.js/react stack or something with each UI element or portion of back-end having a separate dev team. I can vividly remember thinking "oh that's probably why when I change song sometimes the albu…

> each UI element or portion of back-end having a separate dev team

Really takes shipping your org chart to another level

Re: Fastpotify

#482
post #455

Earlier quoted context omitted.

I think you're being pedantic to the point of losing all credibility. And you're gatekeeping in the worst possible way. Your argument that using an LLM means you didn't "make" a thing could just as easily be used to say that if you used a framework or a library, you also didn't "make" a thing, because you didn't write all the code yourself and you didn't understand everything. Would you say the authors of YT-DLP didn…

People do care - lots of people do. Maybe you don’t, and maybe the argument the other poster made wasn’t fair, but you make just as spurious claims when you say „who cares how you made it or how long it took?”

Really? You care about some stranger's work and how they created it?

Pro tip: you shouldn't.

Care about your work if you want, but "caring" about how someone else makes things and how they talk about it is just being a judgemental busybody and again, gatekeeping.

As for my comment, I stand by it.

If I made something genuinely useful, then it should not matter if it took me 5 minutes or 5 days to make it.

You'll never convince me that more time spent making something (all other factors being equal - yes, quality matters) gives it more value or credibility.

Re: Fastpotify

#483

Earlier quoted context omitted.

It truly has been one of the worst UX experiences and poorly made apps that ever made it to mainstream. I remember a decade or so ago there being a bunch of buzz about them in software dev because they were a microservice node.js/react stack or something with each UI element or portion of back-end having a separate dev team. I can vividly remember thinking "oh that's probably why when I change song sometimes the albu…

I worked for a startup in 2019 which was really pushing the "Spotify model" of team structure. Apparently it's all about self-organising teams and having no leadership. The fact the technology output of the Spotify model - the Spotify app - seemed to be kind of crap didn't seem to matter. I think the main output of the Spotify team structure was blog posts promoting the Spotify team structure.

The Spotify model is basically just Amazon’s team-owned KPIs and independence, put into a UI so you can really see how much their app is conways law.

This is why all the sections of Amazon.com are barely coherent. AWS does this too but it’s more naturally split and text works better than stateful rich media.

Re: Fastpotify

#484
post #238

Spotify is, without doubt, the worst piece of software that I still use on a daily basis. It's incredibly buggy, incredibly slow, and the UI has so many "usability inconsistencies". I find the Android app particularly bad, just a couple of examples: - Under a playlist you get a list of suggested songs, the UI element looks like a "regular song", but unlike every other "song" element the user has been trained to recog…

i'd love it if spotify split into two companies: - an enterprise platform that just provided a an API to access/play songs and direct the payment to the correct rightsholders - a consumer app that built on top of that to provide the 'spotify' we all have let a whole ecosystem of music streaming apps take off that cater to different niches of listeners. each app would be able to differentiation themselves with their U…

Rights holders would never allow it. It would be too easy for their enterprise customer to underreport plays.

Re: Fastpotify

#485
post #429

Earlier quoted context omitted.

Yes, a project maintained and built over longer time has a bigger chance of staying relevant, than someone's weekend fun they will abandon once the dopamine hit of "making something" wears off.

Isn't software written by hand more likely to be abandoned due to the extremely costly nature of keeping its development going? Abandonware definitely existed prior to vibe coding. As long as it's open source, now you can pick it up and keep vibe-developing it if you care to, for very little money/effort.

Possibly, but sunk costs fallacy often means it's possible to rely on the maintainer to stick around. I think we all know how disposable LLM-generated code can be. If I wanted to vibe code my own thing, I'd do it my way rather than fork an abandoned project.

What's needed is more of a nexus thing where there's evidence multiple people work together or some long track record of someone scratching a very specific itch. Or if we're all using agents to build the same thing some way for them to team up. It's a sort of proof of life thing and it's difficult to distinguish those from flashes in the pan.

Re: Fastpotify

#486
post #86

Earlier quoted context omitted.

Links to your $5M ARR FOSS? And is that Annualized Run Rate or Annual Recurring Revenue? I'm guessing the former. > One of my projects is at $5M ARR in just six months. I passed $400k in sales this month. It's an open source project. If it's the former ARR, then how are you at $5M if it took you six months to get to $400k? $5M/12 = $416,666.6666666667 Which correct me if I'm misunderstanding (I do frequently) but tha…

Presumably https://getartcraft.com/ , after some light stalking.

More details:

https://news.ycombinator.com/item?id=49500019

Re: Fastpotify

#487

Earlier quoted context omitted.

A new term I encountered is “human-stewarded”.

I like the direction, but stewarded feels just a little too awkward to type or say to catch on. Perhaps "guide coded"? But it will be really hard to dislodge vibe coded from being generally applied to this concept, I think, in part because it is a catchy little term.

I came to like "vibe coding". Finding the right vibe in the words with the agent to steer them into the direction you want.

Whether the result is slob, depends on the programmer.

Re: Fastpotify

#488

Earlier quoted context omitted.

Totally agree. They also have some stickiness going for them (at least for me). Now that I've organized my music in Spotify and have my habits in place that deal with the crummy UX, I've gotten numb to the poor UX. Case in point, I make a daily playlist for running and that UX is frequently changing and often for the worse, but I deal with it because it's a habit that costs me a few seconds maybe a minute per day. Th…

We used to have a folder full of MP3 files and call that a playlist. Lightweight, works offline, and never changes without your consent.

I'm going back. Storage on phones is so big now. You can have all your music local.

Re: Fastpotify

#489
post #238

Spotify is, without doubt, the worst piece of software that I still use on a daily basis. It's incredibly buggy, incredibly slow, and the UI has so many "usability inconsistencies". I find the Android app particularly bad, just a couple of examples: - Under a playlist you get a list of suggested songs, the UI element looks like a "regular song", but unlike every other "song" element the user has been trained to recog…

It truly has been one of the worst UX experiences and poorly made apps that ever made it to mainstream. I remember a decade or so ago there being a bunch of buzz about them in software dev because they were a microservice node.js/react stack or something with each UI element or portion of back-end having a separate dev team. I can vividly remember thinking "oh that's probably why when I change song sometimes the albu…

Right now, if you have video clips in Spotify enabled, your lockscreen controls will display 'Artist' - 'Song' - 'Video Available', instead of 'Album Name'. If you disable video all together, it just leaves that area blank instead of displaying the album title.

This has been a thing / issue since 2025. It's pretty clear the video team probably put that in to bump video interactions, then the whole team got put on something else and now this problem is blackholed. The most bizarre to me is: even Spotify's top managers must use their own product when they helicopter to home, right? So they would see this too.

Where is a Jobsian anger for user experience when it is needed. Although in that respect even Apple is in the gutter these days.

Re: Fastpotify

#490
post #238

Spotify is, without doubt, the worst piece of software that I still use on a daily basis. It's incredibly buggy, incredibly slow, and the UI has so many "usability inconsistencies". I find the Android app particularly bad, just a couple of examples: - Under a playlist you get a list of suggested songs, the UI element looks like a "regular song", but unlike every other "song" element the user has been trained to recog…

They’ve left Airplay out of their Mac app for the history of the company and I have no idea why. They have hundreds of engineers. I have airplay running on a raspberry pi since 2019.

The black and neon is truly a not-good choice for a UI. Nevertheless, they persist.

Apple Music has a much better UX. Things like “play next” when you want to play that song next but not clear your other queued up songs are little treats that Spotify took years to catch up to. Many of the other bugs—which people document for them!—go untouched for literally years.

It’s fascinating to me how companies like this ignore easy wins for their users. Have a couple engineers burn down all of those and you’ll win fans (or at least not create enemies.) Take the wins!

Post reply on HN