YNAB, you just don't get it
YNAB, you just don't get it.
Today's release features yet another complete waste of code. I'm speaking of the changes to the goal inspector.
This feature is completely useless when you realize that there's no other way to store a normalized monthly budget in the software other than monthly funding goals. The YNAB team actually recommends this, too. This makes any extra information related to goal funding in the inspector completely pointless - from the little icons in the categories to the new goal inspector information. It's just more (and worse, redundant) code for my browser to have to load so I can budget. It's completely useless. It doesn't actually help anyone budget, which was supposed to be the stated goal of the software. This just one more issue in a long list of gripes related to the software. You guys do so many things right, but you also do things that are a complete waste of time and completely incongruous with the rest of your advice and workflow suggestions. How many UI components on the screen does a user need related to goals?
This would be one thing if it wasn't for the repeated refusals to introduce features in the software that the customer base actually wants, like income for next month. And it would be yet another thing if it wasn't for the development hours spent on features that the customer base isn't asking for, like zapier integration. And it would still be yet another thing if it wasn't for the bugs and flaws that have been in the software since launch, like SFTF. What the heck?
YNAB, you just don't get it. You don't understand what made you great anymore, and you don't understand how to provide the product that your customers want. Now would be a great time to remember how to do both of those.
Just to be clear, are you talking about the following three features from the release notes, or is there more to it?
- Added “Started” month/year
- Added the goal type in the title so that you know what kind of goal it is.
- We dropped the “s” from “GOALS” because that “s” was silly.
How many development hours do you estimate were diverted away from other projects because they removed an "s" in a string of text?
Sorry the release notes didn't seem to hit the right notes today!
I assure you, we're still working on those bigger projects, but we care about the smaller details as well. To provide a bit of insight here, SFTF is being revamped after receiving feedback from the round of beta testing and the Zapier integration was taken on at the request of a strong Zapier-YNAB user base (we were one of their top requested apps).
I promise there is a method to what may seem like madness and I'm sorry that isn't more apparent. We're working on a way to make this clearer to YNABers. :)
I'm a web developer, so I'm probably biased, but I actually like those little changes. I probably wouldn't have noticed them, nor do I think an "s" is high priority but I can appreciate the changes. If in there doing the other two things fixing the "s" is not a big deal typically. Knowing what kind of goal it is at a glance is nice, as is the start date so you can see your progress - AND I can see adding an initial date is likely one step towards having some of the bigger things like recurring goals (pay your insurance every six months? It's been requested to have it repeat every six months for example)
It seems the most development time was spent on import things, which is important.
I'm in software development, and think of these items as "low hanging fruit". Yes, they're not major impact, but something quick and easy to fit in if they're on that page already. Not every update is going to include items every user finds valuable, but they're doing their best. If they ONLY focused on the big ticket items, we'd probably have more frustration with the small things because they'd never address them. Depending on how they do their development, they're trying to fit in these small items as they can, when it makes sense.