I’m not sure if this is exactly from the old adding new features just to have the devs work on something when everything is perfectly fine playbook. It could be, but that’s not what concerns me. I’ve worked with devs that are (as you alluded to) so self-absorbed into what shiny new thing they could add that they disregard what might seem glaringly obvious to even the most basic user. It’s real hard to get through to them once they get started on their development when it would be better to just keep things simple and demolish about 70% of the code they wrote.
In other words, what’s really concerning is that this is turning into the thing where the developer thinks they know what the user wants, but they really don’t. Color highlighting, which screams “don’t fix what’s not broken,” has turned into something more complicated (never a good thing to make things more complicated for users) and add an underlining feature with its own color (never a good thing to make things that are hard to see). I don’t know how you do any sort of A/B user testing and come to the conclusion that this was a user-friendly change. The frustrating part is that the user has no customization options. No, we can’t use choose to use the legacy version, we’re forced to use the new version. Or, forced to just cancel our subscription, if you want to talk about the options the user has.
I take the time to write this not to just put people on blast. I say this because I doubt I’m the only person who will just say to myself that this isn’t worth the cost to use when it doesn’t fulfill very basic needs that the old version did and end up canceling their subscription.
) If so, which of those does it actually bring up in phrase pump? Only ones that include vocab that phrase pump wants me to learn right now?
