Apps Getting Worse
tbray.org
tbray.org
It used to be that when you clicked on an artists page you would see all the music tracks listed. Now it's all buried deep in and you have to search through the individual albums. Even the list of albums itself is not shown on the main artist page, you have to click "See Discography" first.
The "Home" page is even worse. Where is my discover weekly playlist? Sometimes it's near the top, sometimes it's in this "Made for you" section. Sometimes you have to click "See All" next to that to find it.
I mean moving shit around when you update your software is bad enough. Spotify moves shit around every time you boot the app!
All gone. Now you get an algorithmic homepage that's constantly shifting and trying to push podcasts on you...
As companies get larger, the engineering talent reverts to the mean. The first crop of engineers, that were passionate about it, and made it a success. After they move on, they are replaced with average corp. employee, that joins Spotify as safe/boring job. Hence anything interesting gets removed, and the most boring features survive.
Ps. I was one of the involved on that feature. I didn't write it (It was done in Sweden), but I created one of the earlier demos, (and patents), and that eventually became touch to preview.
like here, where are those spotify engineers now... and how do the products they work on now, compare
Can't say much positive about Pandora or Tidal or..
Miss old Slacker days and prior.
The radio feature used to be a fantastic tool for exploration. Now it just feeds you your existing music preferences.
It's amazing how several different stations started from the same genre will narrowly converge even after explicitly disliking different subgenre-specific songs on each station. But that's been Pandora for years now; why I still revisit it time to time is beyond me.
I mean, seriously, this is basic stuff, how can they have got so far from the core product experience that they actually hide the controls of a music player.
I don't want to have to figure out what random UI element to click to see the 'skip' control.
I mean, after many years of not using their service, I recently had to spend a good half hour in front of their app, trying to figure out how to a) list all available songs of a given artist, and b) play one of them. And I couldn't do it. This task is pretty much impossible with their current design. All because, instead of treating their users as adults with agency, they really want to drip-feed them with "recommendations" from their glorified Markov chain. "What do you mean, 'browse the works of an artist'? No, have a 'radio station' of their albums instead."
For regular use the search button is right in the middle on the bottom of the app and right next to it is the button to my library
Your criticism seems a bit harsh to me.
That brush with their current app I described before happened when my wife wanted to evaluate Spotify subscription as a source of children songs. We both quickly realized that youtube-dl and manually copying MP3 files to the phone offers a much superior user experience to the Spotify app.
From breaking audio playback over bluetooth (who would possibly use spotify in the car while also using google maps! What a rare use case!) to incorrect song substitution on playlists, continuing to play audio after bt disconnect, etc. There's a 2 click guaranteed crasher in the version from a month ago on stock android on a pixel.
Clearly nobody at Spotify uses or cares about android. If I could figure out how to port ten thousand songs in a 150 playlists...
I bet that they all use macOS and their app macOS is really really shitty as well.
The "continuing to play audio after bt disconnect" is particularly obnoxious to me, and has been happening for something like 5 years now. The latest update has trouble just scrolling through my entire Library, because why would anyone have more than a few dozen followed artists!?!?! (I have a couple hundred, and the latest update forced artists, playlists, and albums all to list together into one enormous muddle in Library).
I finally bit the bullet last month and moved to YouTube Music. Migration was a pain but I find the generated playlists better and the UX less painful to use.
Maybe they are pivoting?
I guess they have determined it makes sense strategically. If I had to guess, podcasts and music listening are rival goods for a lot of their most valuable segments and they were worried about moves some of the new entrants in the market could have made. Might allow them to target new customers too. Hopefully more than the move will lose them in existing customers jumping ship.
This is in contrast to Podcasts, where nobody really owns the space, and they have a good shot at becoming the market leader.
I mean, I hate podcasts and wish they would go away from my Spotify, but I like the company and the music product, so I put up with it (for now, at least).
So I ended up buying a cheap Android phone ($190 USD for a very good phone - 8GB ram, 12gb space):
https://www.amazon.com/UMIDIGI-Unlocked-4150mAh-Capacity-Sma...
I use Firefox for YouTube with the following add-ons:
1. uBlock Origin
2. Video Background Play Fix add-on
This allows me to use YouTube as a background playback music player. And if needed, I use YouTube-dl to get the audio files and put them on the phone.
I have basically gone back to how I used to use MP3 players back in 2000s before streaming became a thing.
The desktop app is also getting worse. After a certain period of time clicking play simply has no effect, so it needs to be regularly restarted.
I don’t normally enjoy these pile-ons complaining about a product, but I have the feeling it’s coming apart at the seams
I've never understood that either. I have downloaded quite a few albums for offline listening throughout the years but now I have no way of removing them because there's no listing. From time to time I still stumble upon an album marked as downloaded so I get that one chance to remove it.
So you can listen to them without consuming potentially expensive mobile data.
From a business standpoint I find it fascinating. It's about as perfect as an example it gets of "if it ain't broke, don't fix it". Music player UI is a solved problem. At some point they should've just said "welp, don't need a UI team any more" and just never touched it again, but that would mean people admitting they don't really serve much purpose. About as pure an example of a "bullshit job" as is possible.
No it isn’t. Not even close.
Everything else is an addition, but somehow modern apps have managed to make the basic grid worse too at the same time.
Banks and finance are like the number one employer of software developers outside of pure tech companies. I might be misunderstanding your point, but a bank doing digital banking needs a huge IT staff, including software devs. Even if no new products are being developed (unlikely), they support changes to common industry systems, redevelop systems for retiring hardware/operating systems, support integrations with changing business partners, changes to regulatory requirements, etc. I’m sure some devs pulled late nights trying to support the PPP program for example.
Right now, with all the churn that only serves to update various financial numbers in databases and is generally useless for the society at large. As an end user, I view a bank as a box to keep my money so I don't have to deal with cash. That's really it. It already works for me as it is right now.
A rather popular bank in Russia is now trying its damnest to become a super-app. It's developing a voice assistant. Its mobile app has stories. A bank. Is developing a voice assistant and becoming an operating system. Where did we make the wrong turn?
And maybe, just maybe, regulatory change doesn't need to happen in the first place?
I personally like features such as savings accounts (which require a treasury department), a brokerage, lending, mortgages, wire transfers, detection of fraud, and so-on
a bank does far more than provide a safe place for your cash to sit
Edit: I realize this can be read with a pile of snark that I didn’t intend. Apologies.
> A bank doesn't need a full-time development team for example.
all of the areas I mentioned are subject to constant change, mostly from regulators
implementing the Payment Services Directive, Solvency II or MiFID II all require developers
the developers working on the app/website that you interact with are always going to be a small fraction of the developers that work for a bank
and if you think this isn't the case (in a very cut-throat industry), I would suggest you start a bank and put the rest of them out of business with your vastly reduced costs
That’s ignoring things like online bill pay, mobile banking, and roll outs of new financial products that really are innovations from the last 10-15 years.
We force companies to grow, I guess.
All of the bullcrap the banks are doing mostly serves one purpose: get you to buy more of their products at terms that are bad for you.
All the complaints I have against the UX of the banking websites and apps I use can be attributed to this: they do a shitty job on purpose, because the site/app is primarily a vector to upsell you loans, credit cards and insurance.
(All complaints except one: the bank I used for my business accounts when contracting decided to make an SPA with one of the trendy JavaScript frameworks. Well, they botched it. This failure doesn't even help them sell anything, it's just the usual webdev incompetence.)
The only reason I use MegaBank and its obnoxious but functional app is that Local Credit Union can't afford to build a decently functional app.
Because part of it being shitty is obnoxiously advertising you financial products, making it hard to perform the tasks you want with your money without being upsold something, and making it near-impossible to use your account without going through the app/webapp (or a visit to the bank, or the ATM - which is also pushing ads).
It's a really awesome setup really because they are constantly adding new and fun features, experimenting with what works best. Stuff like automatically rounding up every transaction and sending the remainder to your savings.
The ability to instantly create and delete savings "accounts" without having to register a real account number on the phone. My favorite feature is what they call 2up where you send an invite to another member of the bank and you instantly get a shared account where you can both add and withdraw money. It also adds a second card to your phone wallet which draws from the shared account. So much less work and risk than traditional shared accounts.
Some people here mention feature plateaus and completeness of the app. Obvious question is, what should the employer then do? The software is complete, from now on there's only maintenance, which is relatively less work compared to building from scratch, so as a consequence I guess developers should be paid less then? Or like you said, fired?
Obviously the manpower could be just moved to the next project, but what if we look at the worst case scenario? What comes next?
Are there at all such mechanisms that could allow for, say, a team of engineers that maintains a bunch of projects in different companies. If such a team would take a maintenance of a few complete programs, the count of them would make up the difference in pay, e.g. a few mainted apps for a lower pay equal pay for building one app from scratch.
There's 2 scenarios 1) The entire dev team truly does move on...and the operations are in charge of the production app (they're in charge, anyways). There's no code changes...just OS, database security patching etc. If there are any code changes for security (i.e. upgrading Struts because Equifax got hacked...) then the business side that owns the app gets some resources. But otherwise it really isn't touched. It does cause some contention because no dev wants to be pulled in to work on those junk. But in the last few years, we have teams who's only job is to work on this kind of stuff. They work on apps that only need a dev team for a few months.
2) A stable app is part of a team. The team doesn't work on it anymore...For example my team previously owned ~8 systems. I think like 6 were mature where it had no new features. A lot of people actually left to other teams because of that - which is an issue in itself. What good dev would hang around? And when a new app or major feature is needed...you're left with stranglers and junior engineers who need to somehow step up.
Plus I don't know about you, but my bank's website and app are a hot mess. In theory I suppose they could be feature complete, but in reality, nope.
So, just visiting Earth, or are you here to stay? :)
I've worked for banks and while there's certainly plenty of unwarranted churn the notion that they're done and the dev team can go home is ... hilarious.
Edit: addressing your comment in an adjacent thread, a box to keep your money in (or, canonically, a sock under the mattress) does not need to offer/support:
- Debit cards
- Credit bureaus. Yes, even if it's just a deposit account and no, this isn't optional.
- Know Your Customer (KYC) regulations
- Anti Money Laundering (AML) checks
That's before you get into other account types, offering credit, currency conversions and the zillion other things that sock doesn't have to do.
They could also work forever on making suggestions better. As well as new features like lossless audio coming up soon. Supporting new iOS and android versions/features. There is never a point where a piece of software is simply done because the OS changes how things work constantly.
The companies that just contract out for a tiny bit of work every few months end up with garbage software because no one really knows or understands the code so they just tack on bad patches until the system eventually crumbles. And every bank I have used does have a full time development team. The one I currently use sends out monthly emails for the new features they have released and has a road map showing what they are planning on adding.
On the other hand, the LG TV app for Spotify doesn't support gapless playback, which completely blows my mind.
Most users will though. Apple music implements that feature and charges the same amount for subscriptions. So if spotify wants to stay competitive they need a team of developers to keep up with whatever Apple and Google are doing. It's not good enough to just say "oh well the app is feature complete so we won't be working on anything new"
Nothing is ever feature complete when you have competition.
Had to buy the 4G version last time though, as Apples podcast and Music app is horrible at downloading, and Overcast was not much better.
How else will all those SVP's at your bank justify their fat salaries? They NEED more minions. Same goes for VC ecosystem. Funny how everyone has a scapegoat or a solution to this supposed software quality problem, not quite understanding the underlying financial incentives. Easy money -> rotten management -> crappy design.
With agile, practically, many times development is just in time with little regard to long term requirements or the evolution of software so it's all layers of layers of things that work. There's rarely a time for fundamental restructuring of the codebase to meet the new requirement correctly.
Once the cracks begin to show, we start thinking of software rewrite.
For a construction of buildings, the redevelopment is about once 40 years, for software, it's about 5-7 years.
Stale UI is very different from not being feature complete. vim and emacs are very stale UIs, but also as close to feature complete as I need, and thank God no-one feels the need to update them for modern UI preferences (or, rather, that those who do feel that need can do it without taking away my experience of classic vim).
My favorite regression is probably how the Windows client finally had type-to-search functionality for adding new songs to an existing playlist, and now it doesn't again. The Linux client still has it though!
This is to say nothing of their radio algorithm regression.
So, basically, the bad UI is improving their metrics. Or something. Maybe this is a case of experimentation gone wrong.
Now, similar example is Netflix. I've at times reached a point where I think I had watched everything on the platform I'd enjoy. Their UI keeps showing old stuff as new tough, different pictures for the same show, etc. This led to wasted time and frustrating engagement. (Aside: the best Netflix UI ever was a script I wrote myself when they still had a public API that just listed all movies ordered by how much they predicted I'd like it. That paired with IMDB ratings and filtered by what I've already have seen would be the holy Grail but it would be obvious when it's time to unsubscribe for a while)
Given so many metrics are either time or attention based, they probably are opposed to user experience (less time needed to achieve the task).
Or rather, they're trying to align user behaviour. Since customers have very little choice in the matter (most popular SaaS products tend to resist commodification, so there's no equivalent competitor to jump to), these metric-driven approaches often effectively become PID controllers, driving user behaviours to a desired trajectory.
I switched to Amazon Music and at the time the webapp looked pretty much just like mainstream Amazon: drab, white/orange/blue, simple. But dang, it was rock solid. I couldn't get it to error if I wanted to. I could leave the tab open for weeks and it'd play music on command without missing a beat. They have since redone the site to make it look more trendy and more Spotify-ish. This new skin brought bugs with it and it's not the reliable workhorse it used to be. It's still way better than Spotify though.
I am very sensitive to buggy software. And in my opinion, most software available today is just riddled with bugs. I completely switched away from Apple because of this for example. To me, this is the real tragedy of modern software. The bad UX, the dark patterns, the slowness, etc... None of this stuff bothers me all that much when it comes down to it. But bugs, bugs get me every time.
Most people probably blame themself of not getting it.
Or throw hands in the air of what to do about it.
And most don't know that you can make software that fits to the user needs and not the other way around.
OpenSource could have potential here, but most free software developers are not really into UX design either and seem to expect the same tech level of their audience as they have.
"To test its users’ loyalty, Facebook sometimes made its Android app crash for several hours over the course of several years. ... Users were so hooked that they “never stopped coming back,” despite the errors."
I mean, sure make money for your investors, but shouldn't you also try to fulfill your mission statement? Or is the mission statement only to make the share price go up?
So you just make it look good on financials?
So, the big question is: why? Good design is hard and often underappreciated. I don't want to convey that idea. But why do things like this happen so often? Changes that don't actually provide any more utility. Changes that remove utility. It is just so common that there has to be some reason for it. Often backend people say that it is just done to justify their existence but I don't buy this because there are plenty of good design features that can be constantly worked on and improved. Is there some psychological effect this has on users because it is once again novel? So often we don't see good design improvements but things that just come off as "change because change." Why? Help me understand.
Then next year they moved to a left-side holepunch notch, but didn't move it back. Or even offer the option. :(
Also, in my industry, if you're software is not visibly changing, people assume its dead and no longer supported, not going anywhere.
People want to feel like they are part of something that is going somewhere. Software is not a tool, its a journey into the future!
Another is they just changing their ui/ux lead and they have different views.
It can also redesigned to match style updates, useful for fashion, travel or wedding sites.
Sometimes the menu increases that a list of buttons can't accommodate anymore so it's changed to it's own page or drop-down.
Sometimes they want people to be confused and ask the changes in more general forums, generating free publications.
> Another is they just changing their ui/ux lead and they have different views.
This one specifically irritates me. Even under the assumption that that new lead is correct and the new interface is cleaner and more usable, it still needs to be weighed against the time it takes to retrain users to the new format. You have to deal with what you were given. You can't just burn Rome to the ground, rebuild it in a day, and expect everything to be fine. For the love of god, at least do testing to show that this the cost doesn't outweigh the benefits.
Bring in a new CTO/tech lead and they'll tell you the current architecture is outdated or the code is spaghetti and needs a rewrite in [insert architecture/language doing the rounds on HN]. Bring in a new project manager and they'll want to introduce [insert Agile framework du jour]. Someone has been hired for presumably a lot of money, and if they just go "meh, it's fine, we just need to tidy things up a bit here and there" people might question why they were hired for a lot of money.
Giving such downsides to not changing the UI, no cost is too high for a new UI lead.
Lacking objective numerical comparison, perhaps designers and product teams attempt to do metrics-based comparison from telemetry (we raised metric X by changing the design). That leads to an ever changing design that tries to optimise for business objectives, rather than what the user wants.
Backend code can be optimised and honed and improved with objective measurements (CPU cycles used, latency, perceived performance, download time for user), but design doesn't give these.
In saying that though, rewrites in new languages and frameworks do seem to be becoming the problem for backend - optimisation isn't seem as exciting or career advancing, I guess... Few are optimising code for performance these days though, I'd wager - everyone just assumes your user won't mind your software using 15% of their CPU when sitting idle.
Maybe it is just as simple as that metrics individuals are measured on for job performance?
Like, “How many interactions/seconds does it take our users to find X?”
It’s difficult because you have to know what “X” a user was looking for, which requires some varying degree of asking lots of users and reading those responses to be accurate.
Measuring “engagement” is far easier to orchestrate practically and organizationally, even though it produces awful software.
Engagement is such a terrible metric. I'm not saying it should be thrown out, but it is classic example of Goodhart's Law[0]. Rage is engagement. Too much reliance on engagement is what got social media into a race to the bottom. That's not the mark of a quality product.
Measuring is hard, you're right. But if you're going to use bad measurements (which often is our only choice) they shouldn't be targets. We should understand where they fail and use the information accounting for that, not ignoring it.
I think you can apply the same towards design of anything. Tastes change. While a certain design philosophy might be a godsend in 2010, it might be considered trash in 2015.
To be fair, I also think a lot of design decisions are poorly made, and a lot of businesses make poor user experiences.
Just like female jeans that have tiny pockets.
Female jean pockets being small is entirely a driver for handbags and the like. It’s a poor decision for practicality but entirely a business decision — it’s sorta a dark design pattern I guess similar to how amazon buries privacy settings
They do, but do they change as quickly as every season?...or sometimes people do those who make money off changing tastes tell you that tastes change that often?
Objectivity is an ideal we can strive towards. And several crazy and expensive designs are worn in the real world. I have seen it with my own eyes. The people who are able to afford those clothes either:
- Have bad taste (A subjective judgement which is logically wrong, since it is absolute)
- Really like that look
- Don't care what anyone thinks of them
- Want to display their high status
- Want to stand out from the crowd
It's not an ideal, it's a legend.
We'd quickly branch into 'busines formal' UX patterns that change infrequently, only splashing a company color in places but largely uniform, all the way through to 'haute couture' UX patterns like the recent 'brutalist' trend, trusting they only appear on trendier sites and dropshipping fronts.
Sounds like a conclusion drawn from a correlation to me.
I am the maintainer of Red Moon, a FLOSS screen filter app for Android. Over a period of several years, the location of the toggle has moved from a switch at the top, to a switch and a floating action button (FAB), back to just a switch, and will soon move to just a FAB.
I can provide more detail later if someone would like, but the short of it is:
1) As other features changed (permission prompts and moving the growing number of settings to their own screen), one location or the other made more sense.
2) I thought I would like the single top switch better than a single FAB, but after using it for a while, I think the switch feels more confusing than fresh (the action bar is a nonstandard location for a switch).
Overall, I would say it's because design is really hard. But not like that! It's hard because when you spend so much time close to a system, you start to overthink things, and then second-guess yourself. So you can't trust your intuition, you need to listen to users with fresh eyes. But they're also telling you 5 different, conflicting things, and if you listen to everyone you'll have a settings section 9 miles long. You can try to rely on data, but that's mostly good for reaching a local maximum, not staying cohesive. The best designers are able to keep their "fresh eyes" even after working with the system for a long time.
This seems to be addressed by one of my complaints. Was this feature not tested before pushed out to users?
I get that design is difficult. Anyone saying otherwise is biased. But it seems like a big problem is just trying something out first. Design can take months of use to realize something is bad. It seems like what should be done is: create new UI; use internally and push to everyone's version, use for a few weeks to a month; push to beta and get user feedback and pay attention to web traffic like HN and Reddit complaints about the new design; then decide if it should be pushed or not. I've seen apps that seem to follow this but just push despite bad user feedback and bad internal feedback. Going through the motions isn't enough, it has to be used as iterations.
> So you can't trust your intuition, you need to listen to users with fresh eyes. But they're also telling you 5 different, conflicting things, and if you listen to everyone you'll have a settings section 9 miles long.
A good piece of advice I heard was "listen to users for problems. Don't listen to users for solutions." Because people are actually really good at identifying problems. But most people are really terrible at solving problems (I mean if they were good at it we wouldn't have 90% of the problems we do). The addendum is to only take solution advice from experts that understand more of the nuance of what you're doing, but then to still be careful.
How do you avoid leaving the other cohorts behind?
Time, larger testing sizes, A/B testing in the main product, and not rushing things out.
If you really want your blood pressure pumped up, try the Spotify mobile app under CarPlay sometime. At this point, it lets you do basically nothing. A 1980s-era cassette deck gave you more control over the listening experience, just because its fast-forward and rewind buttons worked.
So it's basically radio+cassette player
What's not safe is providing an app that's so frustrating to use that it encourages the driver to touch and grope and scroll and drag all kinds of different things, looking for a commonplace UI affordance that, surely, has got to be there someplace, yet somehow isn't.
Or (worse) providing an app that frequently (but not always) fails to return to the same screen and playback state that was active when the engine was last shut off. That's the #1 unforgivable sin in any autosound system, and... yup... they somehow managed to pull it off.
It's as if the Spotify dev team is managed by B. F. Skinner himself, and they think we're all a bunch of lab rats.
I'm frequently disconnecting my phone, doing what I want, and then reconnecting it. This defeats the entire purpose of car play other than that my GPS is displayed in a place that is visible to me. I'm sure the play engineers have thought long and hard about how to prevent certain behaviors. But I am not confident they watched people use them in the real world. People are very good at finding ways around limitations. It's impossible to think your way through this without actually observing people. I'm not so sure it is Skinner and lab rats but "we're smart and thought about everything." I'm sure you're smart, but no one can think of everything. Thinking that makes you not smart.
Worse, there's no passenger mode for these apps and most of them don't lift restrictions when you're stopped. The lack of these features adds to people not stopping and just doing more dangerous things.
Oh, rest assured, they do. Time spent screwing around trying to get the app to do what you want is considered "engagement," and treated as a target for optimization.
The problems here are that it is SO limited that it is very difficult to accomplish a task. Beyond that, even a passenger can't navigate the app easily. You can't do anything when parked either. Even maps has this problem where it essentially forces you to use voice command but that doesn't work well so you say the same thing 5 times trying to get it right or do the above thing where you disconnect.
Car Play is one of those things where it seems like the developers thought long and hard about how to do things but didn't actually look at how people use the system in the real world.
Not me.
On the developer side, too many interrelated settings can increase the complexity of the code, making it less maintainable.
My favorite compromise is to use settings for the most common functionality tweaks, and then add script hooks to allow extensive customization of behavior. The Android app Simpletask[1] does a great job of this, imo. (There are many places where it could use polish, but it nails the overall approach).
"We need to increase x" comes down from somewhere, and then everyone attempts to find a good way to measure increase/decrease of x and then come up with a design that increases x.
I have never been in a company where a UX or UI designer had leverage to redesign anything just for the hell of it.
One reason is that UI is a fashion-driven space so as the fashion changes there is increasing pressure to rewrite everything to look like all recent apps look, even if it breaks functionality.
Another reason is that if an application has a well-polished UI that all users love.. what's the UI team going to do? How does that newly hired UI PM get to make a big impact so they get a promotion? So there's also a lot of resume-driven UI change for the sake of change.
For the second problem, a partial solution is to have shared UI teams so they can keep busy improving the products which need the most improvement and leave alone the ones that are already good. Of course, hard to do in a smaller company that might only have one product.
For the fashion problem, no good solution. Ignoring fashion entirely works for software that targets technical people but for mass-market applications, no good solution.
A product experience is nuanced, part of a journey, with learning curves, preferences and problems. Much of this is completely ignored in the measurement of the success of design changes.
There are lots of reasons people tend to screw with things that are fine, but the root cause is that they get away with it. Hell, they even get rewarded for it.
Many companies already do have forums like this and they're filled with UI complaints having sometimes thousands of upvotes, but it's all for nothing because almost none of them actually use that feedback.
My bet is still on "UI design isn't a full-time job, it's project work, so UI designers have to keep moving things around to stay relevant in one company". As much as I don't like outsourcing, having a bunch of designers on your payroll with nothing to do most days but still needing to pass all the employee rating crap is bound to result in an unstable and never good enough UI.
No they generally dont. And generally, they never used focus groups, unless we are talking about something super big.
Neither one of these groups know much about UI/X but hold strong personal opinions which they automatically believe must hold true for all users.
I am currently in a tug of war over such UI/X change for a feature in a banking application, making the case that we have plenty of older users who will have massive issues with the current redesign.
My suggestions on performing user testing on the new design to validate them has not received much support over the last weeks.
And so, I have started looking around for other opportunities on the market (this is also why places with bad UI/X continue doing so, they select for the people who are ok with making it).
Imagine If software engineers could get paid to constantly refactor the code and change APIs -- oh, wait, API devs do, for the same reason.
This is usually (at least) an order of magnitude more than your users (well unless you're Facebook I guess). I think many people just get bored looking at the same old screen all the time; and so when a designer inevitably proposes something different everyone on the team thinks it looks great and so much better than the old design.
It's hard for them to realise that it's not better, but merely alleviates the boredom they feel.
Honestly I've heard this line more from designers than any other field:
"We can't add that feature/button because it's too confusing"
Usually the above statement is conflicting with reality and the request to add the feature/button is to give the UI clarity (or worse, provide the feature the customer asked for!)
I'm not a designer, but I know this. They needed less stuff on the right, so the can have a notch in the center.
This made the UI worse for everybody else.
Very hard to get anything meaningful done.
They could have made the service compatible with all of the existing media players, and never hired a UI team to begin with.
I work at a tech company, and I’ll offer my take on why this didn’t happen.
Some growth oriented organizations incentivize product people to keep iterating and “improving” a product. Then, product people are on the hook to show some kind of measurable improvement in some metric. Otherwise, they miss out on promotions, or worst case, they get pushed out.
What I’ve seen happen is some elegant, simple UX that no one ever complained about suddenly morphs into a convoluted, busy mess of its former self. But hey, as long as some A/B test shows an increase in click through rate or total engagement time - great! Mission accomplished!
The root cause is these teams and product people don’t really obsess with the product or the customer experience. They’re incentivized towards optimizing some metric - which at face value appears like optimizing it would provide a better product. But it turns out that’s not the case.
These people all get promoted, pat themselves on the back, and move on. Slowly, the engineering teams realize that these business requirements and stringent launch dates led to a convoluted architecture. We can no longer move quickly or truly innovate. It honestly turns into death by a thousand cuts, where the second and third order effects of the incentive structure ultimately results in a not so great experience. It actually becomes increasingly expensive to fix the past mistakes… the reason could be compatibility or versioning issues, a mess of dependencies and services that no one really understands, or even just a general fear of breaking things and not having clarity on how to get back on track.
It might be that team A has the right senior leadership, but they rely on team or org B to fix issues or update some code. But that other team or org has their own product people, with their own priorities. They couldn’t care less.
What’s worse is that no one is really willing to call out these issues, at least not on the record. Sometimes it’s disengagement and other times it’s fear of coming off as a negative person. Because the immense complexity is too difficult to solve by one person alone, and they honestly don’t have a solution that people would really get behind.
Slowly the engineers burn out or feel disengaged. The great engineering talent ends up leaving. You end up with the career people or the disengaged people who are coasting by. At the end of the day, the customer suffers. We stopped obsessing with the customer experience. It’s turned overwhelmingly into cross team or cross org politics, salesmanship, and often times people focusing on the wrong problems (inventing solutions to problems that don’t even exist) while the obvious thing is right in front of them.
Okay I’ll stop my rant now.
While internally I nod my head and 'agree' that all the above points must be true, the lack of voices on why we have such seemingly random UI changes bothers me on this subject.
There must be tens of thousands, if not higher, of UI/UX designers, and while I struggle a little to believe that Product Management is in such a sorry shape that PMs feel the need to change for the sake of change, it's harder for me to believe that we don't hear more complaints/post-mortems from the UI/UX devs out there. Surely not everyone is under some iron-clad NDA or is so afraid of their employer they won't even try with some throwaway accounts to tell the story of Management's lust for changing UI...
The sad (specious) conclusion I reach is that UI/UX changes that seem bad probably have far more thought put into complaint articles than the UI/UX/PM team ever had with the change in the first place. Whatever the motivation or justification is, seems the real reason for a lot of the changes from such softwares is 'what're the users going to do about it?', in most cases, the company already has their money...why care if you already recouped the on-boarding cost and then some?
But again, just speculation.
For music I can't simply install an open source alternative. That I make a backup of the apk before hitting update says enough I think.
But also before moving away, I was subscribed to one of the ones they made exclusive, Gimlet Media's something-science I think it was called. Enjoyable and fairly informative much of the time, but if they are going to create a gated community I'm just not going to be part of making that a success, so I immediately stopped listening & recommending it and unsubscribed.
This makes sense in the short term but what happens when UI design passes you by and all your competitors look sleek and modern while your UI looks clunky in comparison? Would you use Spotify if it's UI looked straight out of the 2002? Maybe you would, but most people will not.
Similarly with the Google Play to Youtube Music transition. Play was so clean, snappy, and intuitive. Youtube Music is similar to what you describe of Spotify where everything is buried, busy layout, and nothing is intuitive.
Presumably Spotify makes more money if you listen to artist A instead of artist B, and these changes are all part of the gradual change from an interface designed to let you browse and discover music you like to an interface designed to make you do whatever makes Spotify the most money that day.
The trend started with Windows 8 and continues to this day. And if someone brings up "improved security" as a benefit of more modern Windows systems, then they pretty much immediately concede the argument, because it's really not the job of the end-user machine to provide you with enterprise grade security.
Nor is it really true that older OSs simply aren't able to be made secure without releasing additional UI/UX changes alongside security patches.
It's the version of Windows that normalized ads in the OS, unreasonable amounts of telemetry and horrible flat UI.
Apple Music on iOS has its own major issues, but at least search works the first time.
Generally: ideally we imagine UX & product roles as creating a strong experience rewarding the user on for their engagement, by user standards. In practice, in order advance their career, these roles need a narrative of wins they can sell to higher management. That usually means change one can take credit for, if possible paired with a metric management is invested in. Sometimes this metric is even connected with a rewarding experience for users. Sometimes. The incentive for change is there, though, regardless, at least as long as there's money in the dev budget for it.
Spotify Specifically: was founded under the premise that consumers could be drawn into a product that acts like a record collection buffet in the cloud, but only pay broadcast prices! (ie, free or flat rate). This premise was correct, but also relied on the idea that Spotify was entitled to pay artists broadcast-royalties while effect occupying the space where recording royalties used to live, cannibalizing the market for recordings. And so you get execs telling artists that it's "entitled" to want rates as high as a penny a listen for their music and Spotify wasn't built to solve the problem of artists getting paid it was built to solve the problem of piracy (artists not being able to get paid or set their prices is indistinguishable from the problems of piracy). [0] This tells us that either Spotify isn't getting enough revenue to pay a penny a stream, or it feels entitled to keep what it is collecting.
And here's what else we know about Spotify: their revenue per user is essentially fixed. Their model doesn't have much in the way to collect more from a user based off the users own values/actions. They can increase ads, but that's probably not a user driven win. What else can they do?
Well, they can do what the rest of the social media companies do with their feeds. Randomize appearance of content, mix in known engaging user rewards with other things that let Spotify sell user attention -- to a label or individual trying to promote music/audio in a given space, to third parties wanting to advertise or place another content.
That degrades user experience? Sure. You think the company that is founded down to the core on exploitation cares even a little bit about that? Especially now that they're such a huge name in music they outshine Apple in a lot of markets?
Eventually, I suppose, other people will be dissatisfied in the same ways you are and maybe in a snowballing number of ways caused by the kind of bad-incentives driven rot. But it's likely to be a long slow ride down the curve, with an exodus as fast and complete as FB.
[0] https://www.digitalmusicnews.com/2021/06/29/spotify-executiv...
> An unofficial soulseek client. Allows for searching, filtering, browsing folders, and downloading files.
https://play.google.com/store/apps/details?id=com.companynam...
Entire albums simply do not work without gapless playback.
All I can imagine is that there is some confusion at Spotify and the developers must have the sign backwards, thinking that research findings are what not to do. It’s a consistently shitty experience.
I still find it hard to navigate and find things, and the performance is bad, but before was really really bad, the last iterations come out well for me.
I will like more features.
For example I really want a feature to make playlists with albums, you can create playlists with all the songs of many albums, but is not possible to see it as a list of albums with the cover arts, like the Library. For example make a playlist of favorite albums of 2021, favorite albums of 90s rap, favorite albums of Bowie, etc.
Also improve the Library feature, I want to order/filter all my albums by year, decade, genre, artist.
A "listen later" feature on albums and songs will be great too, I want to have a place to "test" music, and later add it or not to my Library or Liked songs.
Lately the streaming platforms and the music industry is focusing on songs more than albums, and this is reflected on the features that their apps have. I find great the power that playlists give to consumers, but I find that the album experience give me a layer of artistic exploration that can't be captured with playlists, discovery weekly, top charts, etc.
This kind of thing boggles my mind. An album, a playlist, the current queue, these are all lists of songs. They ought to be implemented by the same model under the hood. You ought to be able to do the same set of actions to any of them - add to a playlist, add to the queue, etc. But for some reason you can only do some of things to some of the lists of songs and that changes depending on which client you are using.
This is not unique to Spotify either, Amazon Music had the same issues.
Liking/saving all the songs of an album. You used to be able to do that with one click and they would be added to your liked songs play list. Now you either have to like all the songs individually, or like the album and not have it appear in liked songs.
Being able to search through all the artists for songs you’ve liked/saved. You can now only follow an artist. You can’t just browse through all the artists you’ve liked before, which makes it hard to go back to song you liked years ago before they made the “follow” change.
https://engineering.atspotify.com/2021/04/07/building-the-fu...
According to https://community.spotify.com/t5/Community-Blog/The-New-Desk...
"We're working on bringing back a list-like Discography view, something many of you have mentioned missing in the new UI"
They could have just left things as is, but no.
How is that stupid?
(I'm not an Electron fan, but I think accessibility is important.)
But now, if you click on a movie, it starts playing immediately. If you want to see what it's about, you hover over the movie, wait for it to expand, then click a small caret symbol to expand the movie page further to see details.
And if you want to see reviews or customer ratings, too bad because Netflix decided those aren't useful so you have to go to IMDB or some other site to see what other people thought about it.
The original player (in QT, iirc) was incredibly good : light (some mb of RAM), fast, zero bloat, well crafted UI.
I signed up for Spotify because it was an incredible product, but I stay because I’m forced to (shared family account and nothing really better in terms of bloating).
Sometimes those stories makes me wonder that the golden age of « life changing » software is behind us (I’d say exactly the same thing with Dropbox).
Curious to know if anyone finds it usable!
I generally assign the problem of "change for the sake of change" to the UX developers, at least at any significantly large company. Once a company gets large enough, you're employment is no longer justified by the quality of your work. You justify it by shipping product features, enhancements, and fixes. So UX developers can't sit back and do nothing, the incentive is to endlessly tweak the state of the UI, by moving things, converting panels to ribbons and vice versa, redesigning icons every 6 months or so, etc. Is it the UX developers fault for doing this? No. But are they the ones doing it? Yes.
You can't shuffle all songs in your library anymore, since they removed the songs tab completely. There used to be a workaround with a playlist of all your liked songs (which turned into all songs in your library). That was killed too, so now the only way is by using a playlist and managing it manually. Playlists are limited to 10k songs though...
Generally they seem to remove features in every second update and i'll move on to another service after my current sub runs out in 3 months.
In these apps, you just had to have normal windows operations, like drag and drop, select multiple things, copy paste and many more things you just... did with computers. Also, if you wanted to list all songs by singer X by genre Y... you could just do that. It's just something music apps could do as a basic requirement.
Now spotify makes drag&drop like ~somewhat~ work, but you still can't sort your music and at least the 1/4ths of the screen permanently shows an empty "connect with facebook to have 'friends'" sidebar, that can not be minimized.
It's funny to me how the invention of these JavaScript apps has thrown computing back by a good decade. If you look at how careful Win9X was designed and researched, and how careless 100% of the current UIX is designed (mostly blindly A/B testing I guess), it is such a contrast.
Are there any UIX designers or frontend devs here on HN? How do you deal with essentially being representatives of the dark ages of your profession? Are you embarrassed, or do you yourself think that your "craft" doesn't really matter for the bottom line? Or has design already been replaced by AI/ML anyway, and we are all yelling at windmills here?
I really wonder how you release something like Spotify et. al. as, say, a lead designer or lead frontend developer, lean back in your chair and go: "Yeah, I did a good job here".
Having the friends sidebar always there probably increases engagement with Spotify's social growth strategy which boosts network effects and drives recurring revenue or something. It's all stuff you can plot on graphs and show that you're being effective.
This mentality isn't unique to product managers. Mobile developers and front-end developers increasingly don't want to work on technologies that are perceived as outdated, or even to work on someone else's code. Everyone wants to list new technologies and greenfield projects on their resumes.
This was one of the biggest hiring challenges at my most recent large project: iOS developers wanted to rewrite everything in Swift. Android developers wanted to rewrite everything in Kotlin. Our web app was already written in React, but the web developers constantly wanted to refactor it to use the latest state management trend. When Hooks were introduced in React, we spent far too long arguing with developers who wanted to refactor all of the working code to use hooks instead.
The bigger problem is that nobody wanted to work on someone else's codebase. Everyone wanted to work on greenfield projects and technologies that would look good on their resume going into the next job. Some of the most talented developers we hired were obviously only interested in using our company as a stepping stone to FAANG jobs (which didn't actually pay much more, but they were more prestigious on a resume so they wanted to switch).
Blaming product managers is an easy out and will likely match popular opinion among people who aren't product managers, but the problem extends to development teams as well.
So that feedback loop is going to incentivize short term thinking and small changes that might not be beneficial to the whole.
This is why "it's the PMs" is a refrain -- because the changes they make are very tangible in the end product.
I’m fortunate that the company I was hired at doesn’t care that I haven’t worked on Kotlin or React. But I was passed up by many companies because I didn’t have react experience - can’t help it if my last few jobs were all angular.
Many engineers are focusing on doing what will help them get the most compensation. And following industry trends is part of that.
In most fields, there are also second-tier jobs. You get to enjoy a nice middle-class lifestyle with a good work-life balance in a stable long-term job. The incentives are there to do your job well, because you have to face the consequences of your choices. I know plenty of software engineers in jobs like that. When the company eventually goes bad, they have no trouble finding new similar jobs, because good experienced software engineers are scarce.
I am just writing some hardware test app using C++ and wxWidgets.
But in general, yes, you are completely right. It's just virtual signalling between developers. You can't just write something, it has to be Instagram friendly. It needs to be popular and have hundreds of stars in GitHub.
Surely there must be a point where the product functions as intended and the peak number of users like it like that. Instead we carry on. Everyone has to keep proving their 'value' right? Always changing, always growing. Everything eventually gets iterated to death. Any piece of software or design, no matter how much you might like it will eventually be replaced. It's as true of software as it is of car shapes or curtain patterns.
Just imagine being the CEO of Evernote (mentioned elsewhere in the thread) announcing to the world that they are feature complete. It's a finished product and they are laying off everyone except customer support and marketing. They would be considered insane despite that decision delivering the best profits and customer experience.
So my resume always needs to be fresh. I can’t be working with older technology because when it comes time to jump again, I won’t have the skills to do so.
Asking an iOS developer to work on Objective-C is asking them to sacrifice their future prospects.
Devs have a lot of the same incentives product managers do.
I also see the same pattern in "Ask HN" posts and many comments here from people venting about how they've started so many side projects but can never finish them. Starting new projects is fun. Shipping things can be hard and requires some tolerance for boredom.
A lot of people get into the field because they like to program and play with new programming things. Regardless of jobs or compensation, there's a strong pull toward doing new and different things. There's also a strong aversion to working on someone else's project.
To throw another log in this rant bone fire, a few decades ago software was seen as harder and more expensive, and while there was some frivolous and/or stupid apps, big enough development projects were usually bound to some purpose.
Our industry in its current form is more open to build meaningless things and trash after a while. I knew devs who were specialized in home page redesigns, and they viewed it as facelifts to show the client company is still alive. It has a business purpose, but in the grand scheme of things the only person that really enjoyed the project was the guy using it to learn vue.js.
Or a team porting an app from Objective-C to React native, not because they think it’s shiny but because hiring is hard/expensive and/or the business wants to have one size fits all apps for iOs and android.
This just sounds insane to me being a non-programmer. Literally nothing in my job requires me to be up to date on technologies that are less than 10 years old to be considered for a job.
The impact a language has on your career prospects is U-shaped. Knowing new languages is good for your career. Stagnating on an 'old' language is bad (Swift is only 7 years old...). But eventually knowing the old language puts you back in demand again, to port and support old codebases.
The FAANGs have tons of Objective-C code. The largest and most popular iOS apps in the world are actively developed in Obj-C and C++.
It’s absurd to me that mobile developers actively undermine their ability to get those extremely well-paid jobs by limiting themselves to one language.
Developers want to change stuff and do greenfield because it's fun, but that's a whole different beast to a career track whose job it is to change things. This goes beyond just poor incentives ["Googler gets a raise because shiny new thing"], into "upper management have created a construct whose purpose it is to disappoint existing customers who like what's already there".
There may be an argument that you'll draw in more people with shiny stuff, than you'll lose when you break old stuff. I only have anecdotes and personal experience that that's untrue [digg? reddit? metro?], and no examples of cases showing that argument to be right.
Also, personally I get my jollies working on other people's old code. I work with several FORTRAN codebases that pre-date my birth, and I enjoy it.
Sure, but companies aren't being blindsided by project managers who sneak into their org charts and start driving change unbeknownst to company leadership. They're hired to do these things and their performance is based on how well they do them, just like anyone else.
This might be a good example of the struggle of middle management: You get blamed from all sides for just trying to do the job you're assigned.
Swift is hardly new anymore... are you going to maintain an ObjC codebase in perpetuity?
What's the objective benefit of rewriting something already working into a different language?
No wonder they don't want to work on someone else's code, they don't even want to work on their own old code :)
It really feels to me as if developers these days care much more about the development process itself, and how their code looks, than about the end product of their work that the users see. Same for designers — they want their UIs look "clean" and enjoyed like works of art, disregarding obvious, glaring UX issues that arise when any person at all tries to use the thing.
I don't want to work at a place that has "business goals". I don't want to work on a proprietary product either. I just want to use my skills to make the world a better place, and moving money around ain't that. I don't want to participate in the rat race or help it in any shape or form.
I worked at VKontakte (Russian social network) and was the only Android developer for several years. It was amazing when Pavel Durov was still the CEO. I was living the dream. It all went downhill form there when it was acquired by mail.ru group and I had to quit because it started feeling like an abusive relationship. My app being closed-source didn't help either.
Then was Telegram. Same Pavel, mostly same team, but the tasks were much more ambitious, and the product itself much more complex and internally intertwined (every single update touches the chat screen, which in the Android app is more than a megabyte of pure Java). I did the VoIP library from scratch. In hindsight, this certainly isn't a one-person endeavor, but I didn't know any better. So, yeah, eventually, but very unexpectedly, I was fired by that same person who I was a huge fan of for so many years. The reasoning was that "our calls are shit". Apparently I was supposed to write code that didn't contain bugs and just "test it myself". Oh all those foolish other companies having QAs, right?
I have no idea where to go now. I want my 2011 back. I want to be passionate about something again.
* It's (mostly) all open-source.
* It's self-directed. Don't like a team? There are a dozen others waiting scrambling for developers that you can join with no bureaucracy nonsense. Want to work alone? The tools are mostly mature enough that you can release products as a one man team.
* You seem to have disinterest or even aversion towards money, from its role in tricking people into mindless jobs. DeFi is about the roots of what money is, voluntary transfer of value between people, which is something I think everybody can agree is fundamentally good.
* You can have a huge impact.
Though, yes, if I wanted easy money, I could go work at such a company. Or I could as well go to a FAANG-ish megacorp and earn craploads by working an hour a day.
Be very careful when putting your trust in visionaries.
Also another problem that doesn't seem to be talked about a lot is that way too often, the stake holders and the developers have nothing in common with the end user.
Apple in particular is a good example here. They used to position themselves as a company that makes great tools that empower people. But now they're putting their own agenda, and, conveniently, bottom line, before that. That's how we end up with endless redesigns of things that worked perfectly fine for everyone (e.g. safari).
What is it in it for the developers to work on Object-C and other older technologies?
Some of the best software I've used are mostly developed by solo developers or small teams (Sublime, YNAB4) because they actually care about their product instead of the underlying tech.
But YNAB is also a great example of apps-getting-worse — you're explicitly praising the 2012 version over the 2015/evergreen version.
(In YNAB's case, they had business reasons to make the app worse (or thought they did), but I bet that's true of many of the examples in TFA)
Probably because Google says Kotlin is the way. You can't use Compose, Google's reboot of the View system, from Java. Why did google create Compose? To eliminate a decade of cruft and problems for one, so congrats ... now your developers are stuck with it.
It's a hard problem. Sometimes it's unnecessary but sometimes the tech debt is real. It's not uncommon to have one blessed path for doing most things but hey, here's this edge case that doesn't fit our mental model and is a pain to test and bloats our bundle and we keep getting paged for it and the engineers who built it left the company and didn't leave any documentation or tests, so let's just kill that feature.
And now users are pissed and don't understand, because from their perspective, they think the cost of leaving the feature alone is zero. But the truth is the cost of keeping it is quite high and there just isn't enough usage to justify engineering effort to reduce ongoing maintenance costs.
If you look instead at a mature ecosystem, like, say, C++ or Java, you might reasonably maintain a codebase for a decade without needing to adopt new language features.
This isn’t actually the developers’ fault, either. I think we need to blame the tech industry as a whole for this.
Resume driven development is a bad anti-pattern and leads to software nightmares. Avoid it.
> Everyone wanted to work on greenfield projects and technologies that would look good on their resume going into the next job.
Greenfield = easy. Fixing a 10 year old architectural mistake = hard.
> Blaming product managers is an easy out
Resume driven development and product managers who make changes for the sake of their own resume are two sides of the same coin. It's all putting good for yourself over good for your customer and good for your employer.
Wouldn't this not happen if the employers just paid more? From what I understand, people do resume-driven development because they want to work at a place that will pay more at some point.
If I was maintaining some decades-old legacy code and knew that my employer will most likely still be around and pay me a competitive salary for the rest of my life, I wouldn't mind just mastering COBOL.
But most companies go bust or lay off developers at some point, so keeping yourself employable by working with the latest tech stack is unfortunately quite a necessity.
[1] https://marker.medium.com/why-dont-tech-companies-pay-their-...
> If I was maintaining some decades-old legacy code and knew that my employer will most likely still be around and pay me a competitive salary for the rest of my life, I wouldn't mind just mastering COBOL.
That is how I feel too. In fact I'd prefer working on something that really lasts compared to the latest fad. But the differences in salary make this a difficult choices.
Backend folks do this too btw. I’ve seen adoption of Docker, Kubernetes, microservice architectures, Rust, etc. driven more by a desire to use the latest trends than the best tool for the job.
Despite hating the game, I'd probably create similar incentives if I had a company. Because the other option is stagnation.
Is there a third option?
Yes: some companies have employees who don't quit as soon as a new JavaScript framework is launched. Do what they do. Yes, large companies operate by different terms than startups, but I assume (big guess here) there are startups who aren't just angling for acquisition or unicorn-or-bust layoff pits. Note that they may not say they're going in those directions, but they will definitely manage you in those terms.
[In fact, I'd be curious how many <20ppl companies with 80hr/wk soldiers aren't hustling for acquistion or aren't running out of money]
For GP, it seems obvious that they're interviewing the wrong people. It could be their phone screening, it could be their ad, it could be their industry sector. For instance, don't advertise for a Front-end Developer, advertise for a [thing you're actually hiring for] Developer, and screen resumes on this basis regardless of what you put in the ad (which hopefully is accurate as to job responsibilities and necessary skills).
While I don't think appealing to new hires should drive your tech stack, telling them we still used SVN was something you kind of said under your breath with a bit of shame. As for "nobody wanted to work on someone else's codebase" is true, but I think needs some give and take. If you're making someone responsible for something you need to give them some latitude for running it their own way. I'm going to grumble less about dealing with my own mistakes over someone else's, but rewriting everything every time someone quits isn't an option either.
That doesn't mean you should actually do it, but as someone who's had more than enough time to get over the new and shine syndrome there's a lot to be gained by migrating as often as needed (ie. the productivity gain from the new outweighs the migration/current support cost in a reasonable timeframe).
Programming tools, techniques and languages are still evolving quickly and even in the same ecosystem I don't use many of the tools and a frameworks I did 5 years ago.
The good old days of really good, dedicated mac software studios are over. Made by Sofa, Delicious Monster, SubEthaEdit, TextMate, Panic Inc, Rogue Amoeba, Strange Flavour. These were really great software studios that really upheld a standard of excellence for Mac software.
But how are you supposed to keep that up when apple forces you into a marketplace that basically relies on customer handouts, where your only way to make profit on your 99ct app is to hit it so big, that your have several million customers.
It's no wonder that there are no good apps anymore, we've swamped the market with cheap cheap stuff, and nobody wants to pay for quality anymore.
I've recently switched from VSCode to Panics Nova, and for a very brief moment I felt like I was back in the old days of Mac Os X where things just worked, and where I felt at home with my OS, without constantly waiting for a better alternative to come along.
I have a windows machine and a Mac machine. The electron apps are the ones most most likely to function exactly the same on both machines.
Setting up vs code was a matter of copying and pasting config file.
Picky users might complain but from what I see, most users are just fine with Electron apps. We all use Slack, Discord, etc. at work and everybody loves it.
Vim and sublime still exists and yet people flock to VS code because they would rather get a more powerful laptop to run an electron app.
Sometimes I think I can almost perceive a little bit of slowness compared to e.g. Sublime—but then I lose sight of it.
Certainly in comparison to any similarly fully-featured IDE I've used its feel is notably quicker.
I only have two on my machine: VSCode, and Microsoft Azure Explorer. If I run them both at the same time, there's a 20% chance I'm going to have to reboot that day.
Microsoft has enough money and resources to make a real program, but it chooses to be lazy and cheap.
And of course, every program thinks that it's the one and only important program running on the computer, which is how we get into the situation we're in.
But as long as the product is “good enough “we will see this trend more as most consumers of apps care more about features than performance
They made one of the best text editor/IDE and released it for free. I wouldn't call that being lazy and cheap.
i find it pretty good, i use it for swift development (packages/libs) with a swift plugin (language server)
it works pretty well for that, its quite lightweight and smooth for the most part
my only concerns are
1. the swift plugin hasnt been updated in a long time, when will it stop working? (general issue of relying in plugins)
2. i think it uses its own text engine, so it "feels" different to other cocoa apps, not a big deal, just something i notice
3. if you wanna just open a file and get syntax highlighting, dont care about autocompletion/building, its maybe a little heavy for that (in the ui sense)
4. this may depend on plugin functionality, but error messages sometimes dont work as well as in xcode (click to fix, duplicate errors reported etc) ---
its not as fully powered as jetbrains tho someday maybe it could!
In my experience, people actually pay for quality, even more than they used to. Back in the say, an app was like 99 cents. Nowadays, most apps are way more expensive or have some kind of subscription, which is okay for apps that are maintained and improved over many years.
I'm willing to pay for quality. The main problem is convincing me of the quality before buying.
Luma fussion just updated to allow you to video edit directly from an external SSD without having to import/export to local storage.
Is there some place that catalogs development companies that are more boutique and quality focused? I want to help support these guys and keep them going.
[0] https://en.wikipedia.org/wiki/Category:Macintosh_software_co...
Never saw it being a problem for Panic, the OmniGroup, Procreate, Things, and others. There are tons of apps that are not 99ct and do just fine...
It's interesting that Apple struggled for a long time with 3rd party software. Developers weren't interested because the volumes were too small. Now it's almost the opposite, there are plenty of customers but the market is awash with cheap or free options.
There are many problems with Apple’s stores, but I don’t see how this is one.
I love (old) Mac software and I hate Electron software yet if I sat down to create a commercial app today, I'd use Electron. Here's why:
- I don't feel the Mac's UX is great these days. If my app doesn't benefit from a consistent and elegant GUI, I might as well do it with web tech.
- I can't keep up with Xcode and the OS changing constantly. There was a time when you'd get a couple years between OS upgrades, when Apple's documentation wasn't (entirely) useless
- Desktop software on the Mac involves so much complexity today (eg: sandboxing, certificates, iCloud, icon formats and sizes, etc) that I don't want to deal with it
The Apple ecosystem doesn't offer enough advantages for me anymore to warrant the effort.
Little details like the title bar of of every window behaving the same were great like ten years ago. You always knew if a dot was in the red close button it meant your work wasn't saved. You could drag and drop the tiny icon just like it was an icon in Finder. It was almost always consistent.
Preview used to be a simple app for viewing documents. I welcomed the addition of annotation tools like adding a signature, but why did they axe the standard titlebar behavior? Now you have to hover over the filename of the document and wait almost a second before the title slides to the right and reveals the little icon. How is that possibly an improvement over just leaving it alone? Did they think saving 16px to show a longer filename without ellipses was more valuable?
Notes is kind of a new app in my mind so it hit the scene when macOS was already starting to feel more like an iPhone, but it's still worth talking about. They keep making it more powerful, like adding checklists and tables and such, but they hide the most basic functionality, text formatting, under a flyout menu. I really like the iOS feature to scan documents. The cropping and contrast adjustments are so good that I can usually quickly scan several pages of handwritten homework within a couple minutes. However, exporting a scanned PDF out of a document on macOS is a mess. Right click on the scan and it take seconds for a context menu to appear. At first I thought it must be my computer got hung, but it's like this consistently. How did they ship a product that make something as basic as a context menu hang for several seconds?
I could gripe with more examples, but the overarching feel I get is that macOS is being pushed more and more towards feeling like iOS, the emphasis on programs editing files is disappearing, and one day everything will be sandboxed and I'll have to click through "share" menus to transfer data from one app to another, provided those apps are kind enough to let me import or export.
This appears to be the standard behaviour of document windows now. It also occurs in the title bar of Finder windows, for example. It is excruciating.
Worse: if you try to rename a file by clicking the drop-down chevron, typing into the Name box, and pressing Return, there will be no effect and the name you entered will be lost. Yes: they broke rename in every standard application! The only method I've found that works is to resist my natural urge to hit Return and press Tab instead.
defaults write -g NSToolbarTitleViewRolloverDelay -float 0
https://mjtsai.com/blog/2020/10/05/big-surs-hidden-document-...
However, for me the big issue with Electron or other web-tech apps is the performance - they all feel incredibly slow and laggy, engorge themselves on my machine's resources, and generally slow down substantially the longer they have been open.
Considering my main gripe about macOS when compared to say, Windows, has been the general performance of the UI and apps, this isn't a particularly welcome phenomenon.
ElectronJS is brilliant, it just needs to go on a diet. It truly is write-once-run-everywhere, which makes my life worlds easier as a dev supporting three OSes.
But it doesn't make your GUI pretty: you still need a designer. And because of that, I miss native GUIs where the design is consistent.
I would ding Electron because it facilitates a diaspora of GUI design when we actually need consistency.
It's not so much an app thing, as it is a societal thing. "You get what you pay for" was such common knowledge that AT&T used the phrase in its television advertising.
Now there are large segments of American culture driven by a "good enough" ethos, and the notion that cheaper equals better. When it only sometimes is.
You could see it happen when advertisements stopped having the warnings "Some assembly required" and "Batteries not included" because those defects suddenly became normal. The companies pushed final assembly from the factory onto the customers, and somehow we thought it was OK.
There's a lot of blame to go around: China. WalMart. Millennials/Boomers (same animal). Recessions. Globalization.
In my family, we do everything we can to buy quality, and support independent manufacturing when we can. But you can't always. My wife just spent $1,300 to replace a piece of furniture that was $300 Chinese junk from Ikea, because she was able to support a local furniture maker, and she knows it will last the rest of our lives.
But it doesn't always work for everything. Especially things like household basics.
It used to be that if you wanted to reach the niche of tasteful customers who would for good software, all you had to do was target the Mac. Obviously it’s harder now.
Considering that companies like Unity were in the same boat, I'm a bit hesitant to point the finger squarely at Apple without considering the decisions these companies made for themselves.
Decisions such as making a 99 cent one-time purchase app and still expecting to succeed as a business.
They all sound like band names, which shows the passion, that went into these endaveours!
When I jumped into Apple in the early 2000's, there was amazing software. I recall in particular my first Intel-Mac-laptop. There was this amazing program that changed the GUI to look like the Bjork video "All is Full of Love". It was absolute magic (beyond the random crashes of the first Intel macs which SUCKED).
I think the problem with all app-stores is this:
1. There's lots of very low quality software. 2. There's no way to verify the software does what it says it does before purchasing.
I can't tell you how many times I've bought an app for my daughter--even from "reputable" companies that only has a few minutes of content before it starts begging for money, coins etc.
Or even if the game didn't beg for money, it was just nonsense. I bought my daughter a game that had no pay mechanics-- but, you had to earn "coins" to do impossible challenges to get prizes. I ended up playing most of the game for her because it was just too hard for a kid, and it was just too hard for an adult who cut his teeth on Atari and Nintendo. It wasn't fun, just tedious. The game required you to make 300ish correct decisions with about one second each in-between them.
In the old days, I was happy to drop 25$ on an interesting app.
I'd love to check out Panics Nova but the Apple Ecosystem isn't viable for me anymore. :-/
Apple killed the paid upgrade model for apps, and helped usher in a race to the bottom when it comes to app distribution. Now everyone expects to pay a dollar or two at most for an app if they pay anything at all.
For a while, I had that same nostalgia... everything looked great... but then, nothing really worked, the plugins were all kind of bad (half of my work is Golang, which Nova does not support), and VSCode allows you to have the same stuff on all three major platforms.
I realized the Mac software from your studios looked great, and yeah had unified Mac feel unlike the messiness of Windows world, but usually had worse functionality. (And they were all always paid.)
There was recently an article from Sketch, that says, how proud they are to have a native app in 2020.
https://www.sketch.com/blog/2020/10/26/part-of-your-world-wh...
Yeah, nice, but... Figma is not native, it has a "worse" looking/feeling app, but... allows you to collaborate instantly - it's "collaboration first", not a feature side-bolted to existing app. And it can be run anywhere.
Chromium is horrible in abstract (why do I need to take whole Chrome with every app?). But they win where matters I guess.
What the fuck, it’s your decision to charge $1 because thousands of other devs do it, not Apple’s. If you want to charge $10-$50 and you think can convince users to pay that much, Apple is not stopping you. Seriously wtf.
Apple’s ecosystem got those hundreds of millions of customers in the first place because Apple lets the users decide how much they think apps should be worth.
Do you think users pay more on Android? https://www.macrumors.com/2020/10/02/app-store-earned-twice-...
It's not just Apple, this has been a general trend for several decades. In the nineties I paid for Office (about £400 I think), now I use Google Docs. It was the same for development tools, £1800 for an MSDN subscription, now I use VS Community, git and open source components.
I suspect this is inevitable because the marginal cost of software is so low.
Then they rewrote it from the ground up as a sluggish piece of Electron crap. Added a bunch of new stuff that sure looks pretty but gets in the way of the core function of “taking out your phone and scribbling down an idea before it vanishes”. I could roll back to the not-shitty version on my Mac but every time I pull out my phone it takes multiple seconds to load, then multiple seconds to leave the “Home” screen to search through my notes, or for the editor to be ready to use to write a new note.
I still haven’t found a replacement and I really need to. (Requirements, before you suggest your favorite note app: needs Mac, Windows, iOS, Android clients; must not be a goddamn web view crammed awkwardly into an app; needs to let me access local copies of my notes when the internet is down; needs to let me share some notes with my husband. “Actually having a nice UI for handling sync conflicts” would be nice too, EN always did the bare minimum of “now you have two copies with a note about sync conflicts on one of them”.) Right now I am kind of thinking of spending a week trying to press Scrivener plus an external sync service (Dropbox, etc) into service, since their clients are all Very Native, and one of the things we actually use EN for is a writing project...
Now Evernote is releasing new features every couple of months and while it still not feature complete when compared with the old iOS or Mac native apps at least it has chance to compete.
I switched to DEVONthink earlier this year but keep my Evernote account just to see how things are going. I want them to succeed, the key is wether the churn of existing users can be offset by new users.
My point of view is if you can't deliver new features you become the incumbent and new player will replicate those features with lower cost or better execution. Also, the ball is moving: newer apps are heavy on features like backlinking that could not be delivered with the glacial release cycles of the "good old Evernote".
I understand that EN is still the best on being the ultimate digital repository, but as a "digital brain" the market has slightly moved towards the PKM space (see Obsidian, Notion, and so on).
I don't.
Event loops, for example, work completely differently on macOS, iOS, Android, Windows and the Web. You will abstract across them eventually and you will get that abstraction wrong unless you are a programming god--at which point you might as well just use a cross-platform system to start.
The cross-platform guys have big companies with lots of money and programmers solving problems that you haven't even dreamed of. If you're releasing on multiple platforms, you will not win.
Encrypted sync is causing many people issues with multiple keys being generated after adding a mobile sync target. There is no easy way to remove superfluous keys from Joplin, once they have been created and synced across clients.
The cli UX is weird and doesn't follow Unix best practices. The main developer made some weird design choices and some important features haven't been implemented for years now.
Instead, about half the time it returns an error screen that says (paraphrasing) "That note can not be displayed right now, try again later"
I do not want to look at my note later. You have one job: show me my notes!
(I have nearly 3,000 notes in Evernote spanning back over more than a decode, so my hunch is that I'm tripping some edge-cases that most of their testing fails to cover)
Searching is only better than organizing if searches are exhaustive, and I can trust that they are exhaustive. My experience with variety of products, including Evernote, Google Drive and GMail, tells me I can't trust that. I had plenty of instances when I searched for a thing I knew I have stored, and search returned nothing.
It's because of this why organizing is still better than searching - if you're able to sort your stuff into some hierarchy ("groups", "folders") and then be able to browse that hierarchy, you can do a fully exhaustive check manually, by just going over everything.
From what I see around me, though, most people just do not have any digital organizing skills whatsoever. It's honestly exceptional that I meet someone who has files going back more than five years and those files are not on their desktop in a "previous computer" directory; and even that category of people includes only those with tech friends that helped them move the data over and set the new system up.
I don't disagree with you, but we might just be the minority.
I recognize that us power users are a minority, but I really wish there was a shop out there that would build software for us instead of everyone converging towards "user-friendly."
How they managed to fuck up the UX on that core button is insane. Two clicks to create a new note. Why? Just why?
> needs Mac, Windows, iOS, Android clients
Wunderlist had the same problem. A todo list app that runs 10+ processes when it's not even open? WTF?
I noticed the same about discord, slack and basically all modern apps. Why do these basic things need to run so many processes in the background? They are completely over-engineered and sluggish and slow.
At this point i only use the web versions of most software when i need them, so they don't clog up my system with useless processes.
For example, when you load the kanban view, when you re-focus the window, the tasks jump and bounce around, even if there's no change. I think that when the window gets focused, the front-end requests the latest data and then repaints it. Why repaint if the data has not changed?
Another example is links. We add a lot of links in our tickets, and I'm always frustrated at how difficult it is to interact with them. When an issue page loads, it kicks off these async things which fetch the link data, and eventually renders them into some kind of first-class link div. The problem is that if you click on the link before the async call finishes and updates the link element, sometimes it works, sometimes it doesnt. If the link does work, and you control click it, it will sometimes not open in a new tab, but instead in the current window. Which means that when you go Back,you have to wait again for the link to render.
I respect that a lot of people are big JIRA fans, but I can't help but wonder if my experience is unique, or if nobody at Atlassian really uses it in anger.
Atlassian are the current, unchallenged, world beating champions of S L O W and have been for a long time. But the purchasers don't care they don't have to use the crud.
Literally the exact same thing happened with my mother and Google's own Picassa. It was fantastic application to easily manage your photos collection, until one day google just went...nah? The app itself still works, but a lot of the functionality is just broken, and without the google photos integration working anymore my mum lost the easy to use way of sharing the photos she takes. And the actual google photos interface is horrendous, I'm willing to bet that it's constantly being redesigned so that someone at google can justify a raise/promotion, not because there's any actual reason to keep redesigning the whole thing periodically, other than someone's career progression.
I wish they still did unlimited storage, but the app is quality, with some pretty smart search built in (you can search things like "sunset" with great accuracy). The editor is pretty easy to use as well.
The only thing is I wish it had the smart photo off-loading of iOS Photos. I don't want to delete all synched pictures from my phone, only the least recent ones. So I can still send the new ones to family without re-downloading. Why cannot I do that? iOS Photos can do that.
It's common for PMs and product designers to move company after about 3 years.
Many of the apps I use have been around for more than a decade now.
That means I've likely been using them for significantly longer than the people who are making design decisions about them!
Changes that are "obviously bad" to me - based on my very specific patterns of using the app over a ten year period - may not be at all intuitively bad to the team working on it.
One thing that has likely exacerbated this issue in recent years is "data-driven" product design. While I'm fanatical about evidence-based decision making, so many of these products are designed around a vague concept of "engagement" which is all about getting users to interact with the app as much as possible. While this is the natural end state for ad-driven companies, I find it very frustrating that a subscription-based service like Spotify feels the need to take as much control away from the user as possible.
I don't need my hammer to be frustrating to use, a nail-hitting-service subscription model, have social chat options... etc. You get the idea.
Like the idea of a good butler, the best tool is one that removes a concern for the user, and doesn't take any more attention after that.
It said that researchers tried for ages, and at great expense, to find ‘the perfect’ pasta sauce and couldn’t do it. No-one would ever all agree. It turned out you needed to make 3 or 4 versions and different people would find each perfect according to their whims.
This never seems to happen with software though. When Facebook does a massive redesign they (eventually) force it on everyone. Likewise the new iOS or any software update as mentioned in article. It’s always in this quest to find one perfect version, rather than accepting that there is no perfect version for everyone and you have to give different users choices, or at least options!
This is the TED Talk you're talking about.
(The incorrect Barry Schwartz one I posted is excellent too though!)
I mean, Winamp had skins and plugins more than 20 years ago. Surely it isn't some hopelessly lost skill, like making the roman concrete or the greek fire?!
Skins might also get in the way of showing ads.
I would fine tune that conclusion a bit: it's not that everybody each had their own different individual preference particular to them. It's that there really were specific, objective answers and that it wasn't specific to the individuality of each and every person. But the "right" answer wasn't one but three or four different right answers. But importantly, there weren't Zero right answers, and there weren't infinity. There were three or four.
The next major version update was a huge disappointment as they decided to take away all the good and unique things out of the app and make it just another clone of their mobile web interface which just looked barren on the iPad screen. Fortunately I had a backup of the old version which I was able to restore but still had a sour taste in my mouth knowing this version might stop working any day from then.
I did try other 3rd party clients but none was as good as the good old official one. The same design was copied by Weibo for their iPad app which held out a bit longer but eventually it went the same way Twitter had.
I find these "7 billion" apps are often effortlessly smooth for basic tasks that I don't want to spend mental effort on. They seem to know what I want to do and make that just about the only option.
https://en.wikipedia.org/wiki/1%25_rule_(Internet_culture)
The Twitter app for example, is perfectly ok for me as a lurker/consumer -- but is most often criticised by the people who i follow (and who are active tweeters)
Everyone is focused on the journey of the 80% user.
I think it'd be nice if our tooling made it easier to support multiple "versions" of a deployed application. As it stands, it's far too expensive and error-prone to let customers opt into UI upgrades. As a product consumer, I can't stand continuous deployment. It just means my workflow can break at any time.
Basically same thing here. Companies don’t promote those who preserve good things. They want new things.
"outdated" "old" is an actual stable experience with bug fixes and responsiveness to actual users and not product managers.
The migration to swipes for everything on the phones is mind boggling.
Super cool for the tweens and twenty year olds that are used to being pushed to the next thing every 2 months.
My older relatives have no concept of what a swipe is and why it should do anything.
Total chaos and brokenness for them and millions of others.
The one thing that is absolutely unforgivable is an app that you expect to trust instead ends up failing you.
My example: After installing I needed to compress a folder of important code and pictures. Just use Archiver right? Well I compressed the folder into a zip file. Something seemed strange. Ubuntu's file manager was reporting 0 bytes for the file after compressing. Strange, so I copied it to another folder. OK 8.5MB. Maybe the file manager was just not able to automatically refresh. The file size seemed small given the input was 300MB. Me being a little worried after seeing this and having been burned in the past, I opened the file and attempted to decompress. First, I was able to see the files so I could have stopped there thinking the file is fine but I continued and clicked extract. It failed. Turns out the file was corrupted.
Imagine if I had not done this sanity check and 6 months later I go to uncompress and the archive is corrupted. That is a potential anxiety attack.
This is not a joke, if you cannot ever trust the damn system to do basic things, you will constantly feel like you are walking on thin ice. Its 2021 how is this still an issue? When you go to complain you are treated with an uncaring groups or more likely an actively hostile group of people.
I have been going back and forth from Linux(various distros) for 15 years now. Not once have I ever felt that I could fully trust my system. The people who develop this stuff don't seem to care about basic quality. If it works for them, ship it. I don't know how to solve this problem without a financial incentive. There are no consequences to shipping regressions and thus even though the software is free as in freedom the incentives are not really aligned with many users.
Maybe I need to sit down and read through as much of the code of the OS and associated apps as possible and set specific version that I "FREEZE" on that are good known versions. But then I will not be able to get any help when something does break since im on old versions and typically googling issues returns fixes for the latest version...so now I would be left with fixing the code myself.
Imagine a Word 5-equivalent WP (and no, AbiWord is nowhere near that), a WP 5.1 clone, a XyWrite that knows OpenType, a dBase-style interface (definitely not a clone) for a modern, free database system. Those older programs simply worked, had command systems that could be explored and learned (shoot, before the Ribbon even Office could be sussed out through experimentation), and were about work. As much as I appreciate what I can do, capability-wise, with modern systems, the people who design them don't seem to be the people who use them.
Where? OSS is consistently a mish-mash of unfinished ideas.
I guess you haven't used GIMP
Compare, say, to Affinity, Pixelmator, Procreate...
I couldn't name a single open source desktop apps which has good UX or design.
It's natural, since these are built by developers, not designers, and they primarily care about functionality and don't have to entice users with good looks and UX.
I do know some Android apps that are pretty good, eg RedReader for Reddit.
Although I will say that is the case for every sync product I've tried and I have tried most of them.
Also, “good” is a very high (and ambiguous) bar. Can you name any commercial apps you believe to be good?
So it completely boggles the mind that, during the last decade, we are witnessing an unbelievable onslaught to any sane UI convention that people have come to expect. At the top of my head:
- No accessibility at all, even though there are extensive sets of standards fully implemented by the UI toolkit. - No scrollbars at all. Even worse, scrollbars that don't behave quite right.
- Ugly styling that doesn't follow even the most basic modicum of guidelines crystalized around the 80s.
- Text boxes and other widgets that have hidden weird behaviours, or are generally ridiculously slow.
- UI widgets that are badly sized and don't correctly follow the regular zoom controls.
- Windows without a title bar that can be moved only by dragging them from a specific small and narrow area.
- Trivial apps for which the browser has to download megabytes of js and raise the CPU to a point that the fans need to start spinning.
- Cryptic icons that don't have any semantic connection with what they are supposed to accomplish.
- My favourite, UI widgets that cannot stay where they where originally placed, resulting in failures to click them as they keep moving/reflowing under the button. Because the toolkit decided to reflow while the user was already allowed to interact with it.
- Phone button menus that have an unknown size below the bottom of the screen and there is no visible clue how many icons below the bottom are not visible.
We are possibly very near hitting rock bottom in terms of UI in 2021, which (oddly enough) means that there is bound to be a renaissance of some sort as regards those things. After the middle ages many turned to the classical antiquity for inspiration. Drooling over the skeuomorphic UIs of the original iPhone and the pseudo-3d toolkits of the 1990s...
Windows without a title bar that can be moved only by dragging them from a specific small and narrow area.
big sur right there:plain white/black windows with no divider line, yet you can only drag from the tiny sliver of the now non-visible bar at the top
same thing happens when a dialog appears, you can only drag from that tiny little sliver even though the whole window is darkened... ugh
This is absolutely the worst thing that interfaces do. It’s terrible, I hate it so much.
But it’s harder than that. Apps need to keep up to date with operating systems, technology changes, business changes.
Take The Economist mentioned. Maybe they noticed an uptick in cancellations, so the change was designed to stem that. They have data you don’t.
Similarly, iMovie. I agree, I preferred the old version. But my wife, who had never used it until last year, got on fine with the new one.
All of the above are still examples of product managers runing everything.
This could be one of those things where you don't know it can be better until you see it.
Things like - faster computer, more comfortable car, better mattress (for you). Sometimes you live fine until the glass shatters and the old one will never be the same.
Edit: this sounds very consumer-y, it's just the examples that pop in to my head. It can be better bosses, more competent plumber, whatever.
On the other hand, it could also be that some people prefer the old way because they've got used to it. Any change to is uncomfortable for them simply because it's different. Every time Facebook has updated its timeline, my sister complains saying "the current one is perfect", forgetting that she'd previously said it was so bad she was closing her account.
To what extent it's one rather than the other is extremely subjective. If Facebook had not updated its UI (and the apps mentioned by the OP had not changed theirs), then they may well have gone out of business. Always saying "the old version was better" is just a form of nostalgia, a sentimental view on which most corporations in a modern capitalist economy cannot thrive.
- make it less something you settle with longer-term and more something that's basically roughly the same axe but differs on a pretty short timeframe
- use the changes to probe what people care about to a greater / less extent
- take away as much that the average person doesn't care about enough to get really annoyed about (which is fine if it's cheaper/better for the consumer but often it's more about hiding the change in the blizzard of activity so you don't get it cheaper or notice the cuts that save the producer without passing it on).
In software the one that was eternally annoying everyone I worked with was WebEx - initially a product that was great in my firm but eventually became the reason no one could start meetings on time because you couldn't rely on it launching in a timely manner because there'd be some idiotic update. It carried on until we ditched it abruptly - great move PM :)
Anyway, it's annoying but at least it's not as bad as the other modern trend: wilfully messing things up for you, so they can charge you to have the non-messed up version back (eg airline seats being broken up on purpose for no good reason! Unless you pay a fee for them not to be a total pain!)
Great sales pitch: "Fire all your expensive, experienced native developers, and hire cheap JavaScript programmers right out of bootcamps, that write everything on the server, so the native app is really just a WebView!".
"Write once, deploy everywhere." Where have I heard that before? Oh yeah...they said that about C. They they said it about Java. They said that about X11/Motif. They said that about Qt. They said that about React Native. Now, they are saying it about Web apps.
Don't get me wrong. There are some applications that I think hybrid or PWAs are the way to go. If someone asks me, and the use case they describe fits my vision for that, I will recommend they explore hybrid/PWA/WebP/Whatever. I recently pulled several native apps off the App Store, because I thought another developer had a better solution, using Ionic.
It's just that native will always give a richer user experience than any kind of abstracted framework. If delivering the best UX is important, we still need to go native (which is generally delivered via built-in frameworks, anyway).
There are many apps that get worse over the years. I literally don’t know how to use most apps these days and I don’t care to. On an app we use for work, I went irate that a button I used often mysteriously disappeared. A few months later, I was having a beer with one of the devs that works on it and it came up. He laughed and said that 40% of users had the same reaction I did. It was less than 50% so they shipped the change. :sigh:
Meanwhile in the growth-hacking section, they’ll raise an project proving that they could get 40% more users if they had a single specific button, if only these were not the users we betrayed in the first place.
Expect more with AI.
Similar behavior I feel among other apps as well.
- New features aren't that useful. (bells and whistles because everyone has it, so should we)
- Old features aren't maintained or getting worse with each release
- Apps seem to be getting slower.
- They don't seem to be completely native (probably using incorrect terminology). When you minimize an app and go back to it, it'll refresh the page. You were reading something?, thought you found an interesting product and paused to look up something?
I don't mind paying a subscription either. If I'm using an app regularly, it needs to be maintained over OS versions but so many apps are getting worse.
We are in a world being rapidly destroyed by metrics. Any sense of intuitiveness or even humanity is considered worthless, because no PowerPoint-driven argument can be made in favor of it, while the metrics faction has reams of “data” to back then up. A thousand times a day we’re subjected to things we don’t want to experience, nobody wants to experience, but they make a metric somewhere go in the right direction. Shittier, harder to use software is just one facet of it.
It simply did not work. And the reviews on Google Play were 1 star reviews, because the app simply stopped working.
I wasn't using this app for years, since I've written a Python script to read out the scale via a Raspberry Pi, but I wanted to change some weight thresholds in the scale, which my script didn't support, so I installed the app, after two years of not using it.
I think this app messed up the scale. It connected once, then never again. I even installed versions from 2 years ago, assuming that at least that would work. It didn't. I've tried this with 3 different phones. Pixel, Motorola, Xiaomi. No success. I've rebooted the phones several times.
So I searched for the Bluetooth codes which were responsible for setting these thresholds in the scale, and added them to the script. The script worked fine and did set the new values.
But now I have the issue that the Raspberry Pi often fails at connecting to the scale. It's annoying, but at least the scale has a buffer for several measurements, and once it can connect, it downloads all the measurements.
For others this simply means to throw away the scale or use it offline. Granted, it was a cheap one at around 15 €, but that's no reason to break things.
I'm currently so angry at this.
So, eventually I gutted its controller/display and replaced it with arduino, HD44780-based display, and HX711 mass sensor module (that reads the existing four sensors), with any form of wireless module for communication being easily addable, if needed.
Now, it's 1-gram precise, which is enough to be used as a large kitchen scale if need be (I plan on adding a switch), I've added supports customized calibration, and customized averaging (it takes N measurements, and displays that).
Further, I plan a smart home integration, and will replace the display and functionality with smartphone app with current user selection (presets + guest), logging, etc. (and subtraction of the phone's weight from the total).
It never supported those "fancy" additional measurements as water and/or fat percentage, but I guess those are relatively easily addable as well (aluminium/copper tape as sensors?). With this, formulas used for calculations would be the greater challenge.
Really, this is the only option of 100% future proofing ones hardware - do it yourself... plus, it is saved from a landfill.
The AWS recipe is easy though: add another service instead of touching the old one too much. Great now there are 200 services and approaching them is like learning C++. If one considers "the product" to be the entire offering of cloud services - I'd argue that the PMs fell in exactly the same feature trap.
> I’m not going to claim that our UX was generally excellent because it wasn’t; the fact that most users were geeks let us somewhat off the hook.
Has this person used the Amazon website? The UI looks much older than AWS. Which I don't mind, don't get me wrong, but it just surprises me for such a popular website, it really looks like the owners stopped updating it in the late 90s (and the search function works like something from the pre-google era as well). Amazon's shopping site is the last one I visit when I'm desperate and can't find it on normal sites, it's always a fun ride of page after page of "this is not what I looked for" and "even if your price field is a string this sort function should work better". No, it's not the geeks that let you not update the UX I think.
At some point Amazon introduced "real page numbers" for their ebooks. Those are supplemental numbers intended to synch up with the page numbering of physical books. You could display your "page number" instead of your location number.
Recently, the option to display your location number was removed in the Android application. So here's where things stand:
- Going from Kindle to phone, you open the book on the phone and go through an unnecessarily long sequence of button presses until you finally reach the "go to" command. This is already a significant step backwards in usability compared to the UI of the Kindle Keyboard from 2010. But once you're there, you can enter in your location number and jump to it.
- Going from phone to Kindle, you open the book on the Kindle and go through, yes, an unnecessarily long sequence of button presses. Once you finally reach the "go to" command, you are presented with the option to jump to a page number or a location number. But the page number option is grayed out, so you have to enter a location number. But the phone app won't display a location number -- it wants you to view your physical page number instead. As far as the phone is concerned, you shouldn't be allowed to view your location number even if you want to.
- The Kindle is similarly opinionated. It displays the option to view page numbers instead of location numbers. But, much like in the "go to" command, that option is grayed out. This is technically a step up from the phone app, where the option to view location numbers doesn't even exist. But it's not much of a step up.
- There is a workaround, for now, in that the phone app will display your location number in the "go to" command's popup dialogue. I assume someone is at work as we speak hunting this down so they can remove the information from the dialogue.
- Amazon's customer service people aren't familiar with their own products. They struggle to understand the concept of "I want to display location numbers in the phone app". One of them unilaterally disconnected from chat.
It works auto-magically for me all the time. I read a lot of books, and I often switch between my Kindle and my phone several times a book.
Maybe you don't have your Kindle connect to your network or whatever, but the reason you're struggling is because you're following the less trodden path.
It works for books I've uploaded to Kindle too, though I always use the upload service via email, precisely because then it's available on both devices.
Correct.
> the reason your struggling is because you're following the less trodden path.
No. Did you read what I wrote? I'm following a path that existed and is being intentionally removed.
You're going through a bit of pain while they transition because you use it in a weird way.
In that...?
Locations start at 1 and increase from there. Page numbers are a disaster. In the book I discuss above, page numbers start at 1 alongside "page 1" of the book. There is plenty of material earlier than that, which doesn't have page numbers. It only has location numbers.
The pages of a physical book are larger than a phone screen. So several pages worth of the ebook all have the same page number, which prevents you from jumping to later pages by using the page numbering.
Jumping restrictions are even added in where they aren't needed -- in some books, jumping to location numbers doesn't work. Instead, you jump to a location that is determined by the app as being "near" the location you specified. This has the effect of preventing you from getting all of a particular passage on the screen at the same time, which I want for screenshots.
So no, there's no improvement to numbering going on, just a steady removal of functionality that used to work.
Then synchronization works flawlessly.
Why do you want to do everything in such a manual way is beyond me.
For example, imagine a web app that embeds Youtube videos, that will show you every new video published by channels you choose. No home page suggestions, no "trending", no "you might be interested in".
You could do the same with Spotify or with one of those terrible news websites.
Some examples of this already exist: Nitter (shows Twitter contents), Invido.us (shows Youtube contents) but they are not mainstream and not particularly polished.
Also, I'm aware that this concept when applied to news websites results in something that is terribly close to an RSS reader.
So, the next idea would be a service that scrapes contents and builds an RSS feed.
Also, I can see that for other services like Twitter, there are indeed third party providers that can create feeds https://rss.app/blog/how-to-create-twitter-rss-feeds
Also Reddit subreddits and users: https://www.reddit.com/wiki/rss
For podcasts, just don't use Spotify and instead get the RSS feed of the podcast you like
So, yeah I'm now thinking of going to my RSS reader (which I currently only use for news) and adding all sorts of stuff.
Thank you for posting your comment :-)
Efforts like youtube-dl are a constant arms race between google making changes that prevent it working, and the youtube-dl devs pushing fixes. It's a piece of software where "too old to be useful" is measured in months as tons of things don't work anymore.
These companies will never willingly give up control over the user experience (especially if they NEED that control in order to serve ads), and they'll use every method at their disposal in order to do so. Discord already threatens to ban anyone who tries to use a third party client - how long until twitter does the same?
With those services that don't have RSS (Youtube does), you will still need a little scraping just to discover the URL of new tweets/posts in a given channel. But it would be just basic scraping and probably more manageable compared to something like youtube-dl.
The original provider wants to make money off this, so they use the UI to provide you with ads and a bunch of tricks to keep engagement up. No way they let you off the hook to use what's costly without being exposed to what drives the income stream.
Open APIs, that's what you need. Obviously Facebook, Twitter, Instagram, Google Chat, etc don't have any, for the above reasons.
I'm honestly surprised that email is still a thing. It's the last somewhat open API around. (Unless you count HTTP..)
Well I agree in principle, but I also agree with you that the big guys aren't going to offer APIs. And even if they were, I think if you rely on some API you are going to be shut down in the long term (remember all those Twitter clients that were using the now defunct Twitter API?).
So, I think the way to go is to base everything on embeds. They are never going to get rid of the ability to embed posts/videos/tweets because it brings more traffic to their sites.
You still need a bit of scraping, in case the service in question doesn't have RSS (Youtube does for example). And yes, with scraping they will try and make your life impossible (dynamic class names etc. to make scraping hard), but you would only need it for discovering the URL of new posts/tweets/videos, and nothing else.
Turning them into regular audio files and using your favorite player and having proper backups of the files is so much nicer. I'd straight up not use Audible if that was not an option, it's just not worth it.
And yet, YET, they flatly refuse to make their apps do proper mac full screen.
Sure we can blame the Product Managers incentives, but lets look at what also guides their conclusions: "hey look at customer stared at this page for slightly longer and then accidentally clicked an ad!" not realizing the customer didn't want to do any of those things
Anyway, for a while they had the feature where you could hold the main button on the remote while on a video, and a context menu would pop up and you could save it to watch later.
One day, that feature went away. So now you have to play the video, watch 1-2 ads, then go to the menu and add it to watch later from there.
Such a pain in the ass. I wonder why they got rid of it.
I think it's pretty obvious why they got rid of it...
AWS really does like to "bounce ideas" off customers. To the extent that I am wondering if we should start billing them for consulting services. A hour long meeting every other month with 3-4 senior team members adds up.
Another example is Android Auto. I was kind of interested when Google announced it was being "optimized" to just work standalone.
The problem is, is that it is actually way more optimized for me to just use google maps and my music player and my podcast player and etc, than it is to use android auto because android auto sleeps the screen and I have to click the power button on the side to make it wake up (vs just double tap to enter the phone). smh. Just can't even get very simple things correct.
On the contrary, Chrome on Android recently release "tab groups", and I hate it. Had to search around for a bunch of esoteric chrome flags settings, but even after applying those i couldnt get back to individual tabs.
The “tabs” feature is such a borked UI. I suspect they added tab groups to try and “improve” the tabs feature, but they definitely stuffed it up even worse!
Closing a tab is now horribly inconsistent and multiple clicks (plus swipes if in landscape) - arrrgh. To close a tab, the best option is now to long press the [n] tab icon (next to the vertical ellipsis), which pops up a “X close” menu option (a fairly hidden feature).
The new tabs UI is so painful I did investigate other browser options.
I remember back at the Snow Leopard release of what is now macOS, when it was announced that this was not going to be a feature release (https://cdn.arstechnica.net/wp-content/uploads/archive/20090...), but rather a release of, basically, catching and squashing old bugs. I was so happy about that release.
Imagine if the Apple of today could manage to do that, rather than taking away yet another battle-tested, decades-old desktop convention in favour of continuing to pretend that conventions developed for mobile interaction will always, or even often, be well suited for the desktop.
Also, as much as I love AWS as a service overall, it's actual user experience is pretty terrible and I wish it did change over time (for the better).
we... did?
Having a dead man's switch in an app is particularly annoying, especially when the new version intentionally cripples the previous functionality.
This is a point of stability that Knuth tried highlighting, but gets panned for. Once a piece of foundational software is released, it has to remain stable not just in "doesn't crash" but in "doesn't change."
Common Lisp gets this right to an amusing degree by how much extension can be provided in user space. The lesson being that the less you do in the core offering, the more folks can depend on it? Maybe. Not sure, with how much that offering actually does.
I do think "enable your users" should be more the focus. Not "control your users so that they do what you think they should be doing."
Admittedly, I don’t use a personal general-purpose computer for as many things as I used to (managing an mp3 collection is no longer a thing; movies are on a smart tv; messengers are on a phone; …), but these days I try to avoid new stuff, even where it’s a bit clunky to do things in the GUI programs I already use. Which are basically xterm, Emacs, Firefox, and Darktable like once a month.
Phones are a lost cause.
About 10 years ago I switched from Gnome 2 to 3. Because my distro did. It was a huge drop in features. Over the years I had tuned my desktop experience on Gnome 2 with different panel apps, layouts, some custom hacks. It worked great. Gnome 3 ended all this. It was really simple, so that it was almost dysfunctional. It was new so I thought the community would soon catch up. But it never did. The experience is still much worse that in the Gnome 2 days. Even a few extensions that try to mimic the Gnome 2 experience can't really compensate, and many of them break with every other update. It's such a shame.
Separate to that it's not such a great example here even if you hate the change as it's a major version. Gnome 2 didn't change much where you find things and how it works for many years. Gnome 3 has been going on in a similar vein of not having changed much from a UI perspective (at least that I've noticed) for what, 8 years or so? I don't even recall the last time I had to learn something new about using it. You're completely within your rights to dislike it. There's mate and xfce for you that might be more to your taste. And as an aside, isn't just seriously cool that we have good options and alternatives if we don't like the way something goes on the linux desktop? When Apple/MS change you go with them or dump everything you use and how you use it to shift to a competitor. Gnome to xfce is pretty straightforward and you use it to use all the same software applications.
These operating systems are harder to use, have fewer features and are uglier than Windows 7.
Hundreds of millions of people battle with Windows every day.
Oh What a time to bring this up. Just when I am losing confidence in Apple. iMoves and iPhotos, I remember the backlash in 2008 / 2009. But everyone ( including myself ) were too focused on iPhone we sort of brush aside those mistakes. And to be fair iPhone was far more important.
Just reading this I feel bad for GrandMa.
I cannot search for videos about python that are longer than 1 hr. That is my pet peeve and regularly drives me up the wall. I have wanted this for years.
In addition to that, my feed is static. It's like I'm being told, "hey you, we know that you will like these and I won't show you aught else until you watch them first". Aarrrghhh.
(Maybe i should have stayed as a web dev. years ago...life was simpler back then, and not as rife with frustrations with other humans as it is nowadays. /sigh)
Muscle memory is a thing and moving buttons around makes using the app harder.
Similarly, I want apps to realize that is not the only app I have on my phone and my life is not going to revolve around using it.
I long for a culture of Software as a Tool, like the hammer in my garage, it exists for when I need it. It does not beckon me for attention or email me about how the handle got updated. It will not need a huge update the moment I pick it up. I do not want to log into my hammer.
Perhaps I am nostalgic for pre-fast internet software. You acquire some bit of software and install it and it is what it is until you, the person using the thing, goes and installs the newest version.
You would get used to the bugs in the version you had - knowing they wouldn't go away - but the software still had utility and you kept using it. Now I get used to something and it changes every 2 weeks and every not and then it breaks something I liked leaving me frustrated and complaining into the void.
I used to get constantly brigaded by people on HN for claiming there's a point of completion.
I believe people in general have come around to this idea more lately.
It's possible to get to a point of "no further improvement, only maintenance"
The whole app has gotten significantly worse since the Lyft takeover.
I think it's something else. It's first of all a self-reinforcing vicious cycle of "keeping up with the Joneses" brinksmanship. When Hulu releases a shiny new homepage layout, the Director of Amazon Prime Video probably fires off a memo to the PMs and designers and UI/UX researchers (haha I joke), demanding that they also refresh their style. Doesn't matter if it's perfectly fine. You need to DO something, dammit!!! And of course, since the motivating factor was how beautiful the competitor's UI is, you need to make your UI equally pretty. Usability? Who cares. The CEO/Director probably doesn't even use the product, his/her kids do.
Most people have chrome/edge/firefox/whatever warmed up on their machine. Opening a new tab to spotify.com takes under a second, assuming you are using any caching at all. Opening an electron app cold is almost certainly going to take longer and hurt your system resources more.
I feel like Spotify is a case where native desktop app doesn't make as much sense as something like Discord, where you do need a lot of native hooks for the 2-way nature of the product.
I'm a sysadmin and the amount of times Office 365 security admin pages has changed in the last year's is madening. AWS's UI sucks hairy balls (e.g.: security group links) but at least is stable.
In principle, a minor bug fix and a feature aren't all that different. There's a control experience and a new experience, and an A/B test can compare their performance.
In practice, I find many features are run with stat sig analysis of their impact, whereas UX bugs are either not fixed (not important enough) or fixed, without measuring their impact.
Of course experience-breaking bugs should be deployed at 100%. But what about all those UX bugs that are in a flow which is shipped and kinda working already?
Wouldn't it be interesting to see that a UX "fix" actually performs worse? Or, wouldn't it be nice to know when a UX fix produces a measurable performance increase?
My anecdote: A scrolling bug on a mobile web sign-in page. It's 1 field form - email address. On mobile web, you can't scroll to see the email field when you have the on-screen keyboard open. This page is the top of funnel for a promotional offer via ads. It's obviously broken, but it's already shipped and (surprisingly?) actually kinda working. Would you fix it at 100% rollout, or do it via an experiment, or not fix it? Why?
Curious if anybody has other experiences to share about this idea :-)
I think that story illustrates why software gets worse: it's less about the company caring too little about it, and more about caring too much. It sees its software becoming popular, liked, and the people in that company (I don't think it's just the PM, but everyone) feel the urge to "do" something. Make it better, bigger, more functional, oh look we should add the kitchen sink too, but not we need to rip apart the old floor because it is not waterproof, "it'll be fine".
>Maybe we ought to start promoting PMs who are willing to stand pat for an occasional release or three. Maybe we ought to fire all the consumer-product PMs. Maybe we ought to start including realistic customer-retraining-cost estimates in our product planning process.
Or maybe software companies should ask more input from users before, when, and after they make changes on how the software works. Bad software changes can be rolled back, unlike the devil's son's eye.
Looking at you Google and YouTube and your lack of a fucking auto-repeat button even though you have an annoying ass auto-next button which I have to remember to disable way too often >__<#
Or the inability of Instagram, an app dedicated to sharing photos, to let you view photos in full screen, full quality, without cropping, and save them.
Considering that often people complain about the lack of Product Managers or similar roles in most of the FOSS projects, and that nevertheless the same kind of things happens there (it is just a bit slower thanks to the lack of resources), I guess PMs are not the only culprits indeed.
I guess it just comes down to working ethics. Doctors are a good example. Among them there are people who just do a job, who aren't passionate about the whole saving lives. And those are people that work directly with patients and heal people. Now imagine how bad a situation is when a person doesn't work directly with people and responsibility seems little. Among developers, there are people who are genuinely concerned about quality of the code they produce, but they are a minority. There are far more of those, who came in the field just because that's the next big thing and where the money's at. They just spend their whole day ramming that badly written code in a badly written codebase because manager told them to get it done by the end of the day. They don't see the consequences of their actions.
I read something like "a bunch of developers are controlling data of millions of people" some time ago. It feels relevant. Quite a lot of developers don't realize the scale of impact their software can have on people.
It's just your general mundane ignorance and wrong values.
Sometimes I think it would be an interesting mental exercise to convert most (all?) web pages and PC apps to something like a bog simple Windows 3.1 application. You could melt an online banking site to a handful of drop down menus and dialog boxes.
You have to wonder what the effect of ever-more-obtuse interfaces combined with visual gingerbread has on people with vision problems.
OTOH, there's apps that have been around for years where you have to wonder what they were thinking to begin with. Calibre. After Effects. Gimp.
The second points are valid, IMO, but the first... I think this is simplistic.
First, there aren't a ton of example of software products succeeding by staying still for long. Not none, but not a ton. Even fewer, if you define success commercially. In CD days, version upgrades were often an indispensable part of the business model.
These days, apps exist in multiple device world. Big chunks of it are server based. SAAS, which most everything is to some extent, has its own business imperatives. Iphoto deals with a mostly iphone world today. The Economist, like most magazines, is trying to figure app how a software based magazine business works.
It seems naive to blame the PM. Constant change isn't a thing because PMs have egos. There's a big hairy dynamic at play. Not changing doesn't seem to be an option, in recent years, maybe ever.
I wonder though, whether b2b software also suffers from this, because such software isn't really made for public recognition and etc. in the first place.
Can't have good things when the only thing the people making them care about is money.
You can't just fix this by saying "ok let's promote PMs who are obstinate about not changing things" -- this will not align their behaviour with existing customers any better, bad things do still need to change. You'd need to adjust the business goals to be aligned with stability, and that's not something you can fix in a performance review. That's not even something you can fix at a company level.
It's just consumption-driven capitalism in action.
In software development, there's an internal to the company dynamic where the designer/lead-architect/etc wants to show value to the company and so rework the architecture into the current thing or some idiocy of their own devising and this is how features worsen. You can call this a extra process but I think of this as just the way economic dynamic happens. If this dynamic didn't still make the company, it would be stopped.
Now the question is: how can we determine whether the new app update is better or worse? I think PMs and developers intend to produce better apps; but don't they realize that their updates are bad? That's why this issue needs more research to be understood IMO.
I think one of the indirect reasons is that in this world of countless options and emerging new things, people (including PMs and developers) don't want anymore to spend their years working on one thing and making / keeping it great. I'm sure there a lot more to it than this...
Very interesting discussion here.
- Analytics packages need to shrink. Most can be under 5kb, but rarely are.
- excessive event tracking and demanding items like scroll listeners need to die
- Ad tracking is completely nonchalant about speed, and oftentimes chains dozens of tags (or hundreds to thousands for header bidding)
Analysts can save the day by tracking the right metrics:
- time and clicks in navigation should be tracked and optimized for minimal use. Get users to content fast.
- rage buttons. No lengthy surveys, just allow users to indicate they are angry at a feature. Count the times it gets clicked per location.
- Optimize towards retention signals first. They matter far more than conversions. Look at the usage patterns of users that don’t return and/or churn. The top-line funnel will sing if users are pleased with the UX. This matters as much for desktop tools as it does for SaaS.
- Each deployment with UX implications deserves tagging and long-term measurements. Look for how long it takes users to adapt to changes, and not just when it’s brand new. More clicks is probably worse, don’t brag about that.
- Sometimes a longer session means more contented usage, but often it means more frustration.
- pay close attention to engagement with settings UX. That’s where people go when the UX isn’t right.
- Give users some access to the dashboards you look at, if feasible. I’m a firm believer that people being measured should be able to observe some form of what is derived from that data. If PMs exist to improve user engagement, engage them in the process. Two-way mirrors, whether virtual or physical, are creepy AF.
David Pogue delivered a nice TED Talk 2006 [1], when he's enthusiastic about a new version of a program that didn't change a thing but just made it more robust.
I'm nut sure but I think they change their UX/UI about once a month, it's so extremely frustrated that a banking app, which is just a tool, not for entertainment, has to be figured out again and again because they keep changing it. Without adding anything. The UX never improves, just changes...
Where are my recent transactions? How do I change the currency? Where are my account details? How do I pay someone?
All these things worked and were clear at some point in the past.
Now you can still do them but first you have to click the wrong things a few times first before you find it.
Purely UI though, the actual sending of money still seems to work.
What about the Nest PMs? That app hasn't changed at all in at least 3 years. Ok maybe it doesn't count if they've abandoned it.
You’re damned if you do and you damned if you don’t. If you find a great UX for your app and decide to keep it that way, 5 years later all potential new users will look and say “that’s old, isnt there a modern app for this?”
It’s silly, just like fashion, but software has a user base way beyond tech enthusiasts and that user base is very sensitive to cues similar to the fashion industry.
Software is no different
The old android app was terrible too because of frequent crashes.
Fundamentally, you need a healthy balance between conservatism and liberalism. Software companies don't have enough reverence for the former, and perhaps they're structured in ways that incentivizes the latter far more than they ought.
Fuck 'em and their dark patterns. I'm happier going old-school and buying blue-rays from the criterion collection.
Turns out there's someone in my country that rents movies via snail mail. I suspect it's just someone with a very large collection trying to recoup some of the money spent on it. It works really well.
Let's take a live example tested while writing this comment. I searched for "Stand-up comedy", and I see 9 results on my TV right now:
- The Grand Tour
- The Grand Tour presents: Lochdown
- The Grand Tour (again? must be a different season?)
- The Grand Tour (yes, again)
- The Tomorrow War
- The Office
- The Office (again)
- The Office (again)
- The Office (again)
And just for fun, let's list the next 9:
- The Office (again)
- The Office (again)
- The Office (again)
- The Office (again)
- The Office (again)
- Borat 2
- South Park
- South Park (again)
- South Park (again)
It's baffling to me that table-stakes features like this can be completely neglected for a product which is obviously a massive capital investment. I do think I understand now why it is that my friend with Prime Video watches The Office almost all of the time...
Edit: Apparently searching for "stand-up comedy live" or simply "comedy live" does show the type of content the search implies. I'd be keen to have someone explain what non-live stand-up comedy looks like to justify the difference in interpretation. Perhaps they could also tell me about how "stand-up" carries zero usable information...
I'm leaning more towards laziness and lack of creativity.
- Butch Bradley: From Las Vegas
- Melinda Hill: Inappropriate
- Steve Treviño: My Life In Quarantine
- Jimmy O. Yang: Good Deal
- Jim Gaffigan: The Pale Tourist
- Michael Gelbart: All New Smash Hits
- Sebastian LIVE
- Tom Segura: Completely Normal
and so on.
I knew i could not change their minds so decided to change the cloud provider and using alternate services whenever and whereever i could.
in my opinion, Whoever designed the current AWS UI should be fired.