Lets Talk YNAB Roadmap...

Its probably not fair to say I have ever really been an overly 'happy' YNAB customer. The product is good enough, and works for me, so satisfied enough form that point of view. But I have one major issue that really bugs me...the cost vs. lack of development. 

Because lets be honest with each other; the product is stagnate (and has been for a long while). I mean seriously, what significant features have been rolled out in the last couple years? Sign in with Apple for the iOS app? Um, great I guess. Portrait mode finally added to the iPad app? Happy about that one, but that took quite while a longer than it should have. 2FA finally added? I am all for security, so good on you for that one I suppose. The whole pastel colors redesign/fiasco? I think we all remember how well that went (especially those of us with color-blindness who were supposed to be "helped" by it). 

There's really not much though is there? The app is basically the same today as it has been for years. Which is kind of BS since you guys decided to go down the 'software as a service' cash-grab route.  And that's my biggest problem. If your going to force people to pay annual subscriptions ($84 much less), then there should be ACTIVE product development, which there is not here. Where is bank import support for non-US customers? We've been asking for years and keep getting nothing but the same lame excuse (which don't even hold up for places like Europe). Where is multi-currency support? Where are the improvements around stealing form the future? What about more reporting options? Multi-user support? The list goes one. Feature after feature that people have been begging for for years and yet, nothing.  And its not like you've been too busy with other stuff because seemingly nothing else major has been rolled out for as long as I can remember. So in light of that, I have a few sincere questions I hope you will honestly answer:

  1. How many full-time developers do you keep on staff for designing and implementing new features? Not maintenance and bug-fixes, but working on actual improvements to the product and dealing specifically with feature requests. Are there any dedicated for this?
  2. How many customer requested features have actually been implemented in the last 2 years, and how many remain open? Which were implemented?
  3. What is the development road-map for this year and next? What features are you planning to add in the next 12-24 months?
50replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Completely agree with this post. 

    I *love* YNAB the methodology and philosophy.  I'm *blown away* at the level of customer support.  The educational resources are *phenomenal*. 

    But I'm "meh" on the software.  And (as someone who has been in the SaaS industry a long time), I'm appalled at the terrible rate of product improvement.  On LinkedIn, there appears to be ample resources.  The engineering/product side of the YNAB org is being fundamentally mismanaged.  I'm concerned about the long-term viability of YNAB as a company if it can't get it's act together on the software development side.

    Like 7
  • I would still love an answer to my questions.

    Like 2
    • Forest Green Stallion  I think there are a lot of people here who would like to see the answers to your questions. I have been using YNAB for about a year and I love it but I too don’t understand the lack of development. 

      Like 2
  • I totally agree with this. As a paying customer based in Europe I can't imagine how easy it would be for them to apply or partner up with something like Tink that has connections with all banks in Europe almost or use the new rules and get access to the banks here..

    Like
  • There is no question in my mind that YNAB has not lived up to their side of the bargain when they launched nYNAB with the SaaS model. Jesse explicitly told us that it would allow them to develop more rapidly and not have to hold off on big features for future releases. As we all know, new features are rolled out like molasses. It took a couple years just to get the launched software up to snuff.

    Like 3
  • Hey Forest Green Stallion

    Thanks for taking the time to really think this post through and post it in a thoughtful and helpful way. I hear your frustrations and I genuinely appreciate the manner in which you brought them up.

    I won't be able to get as granular as you'd like with numbers, as there are a lot of metrics we don't share publicly but I'm going to get into your questions as much as I can. We're also going to have a slight difference of opinions here in relation to customer requested features and the primary reason for that is that I can see the requests and what they're for.

    All the features we build are coming from requests from customers. They may not be the requests you're making and we do not use a number of requests as a voting system (more on that below), but there aren't features we're just building for fun. I know that the same features are talked about on the forum over and over, but those are pretty rarely coming up to the top of the list as a whole when you look at all the different ways we take in requests.

    Our product team is going through feature requests that come in through our customer queue, but they're also going out to customers with surveys, user interviews, research studies. The determination and priority is coming from a more holistic view than simply by number of requests.

    Let's dig into your questions:

    1. I cannot give specific numbers, as our list of employees is kept mostly private. We do have a healthy mix of development team members working between app maintenance & speed, security, and building new features. There isn't one of these areas that is more prominent than another.


    2. We tend to keep the most popular requests listed on our Up Next page since they are asked about the most. In fact, with Sign in with Apple released, that list needs an update - making a note to get that updated. 


    We keep a running list of the features that were more highly requested and had been recently released on there for a while. Features like Running Balance, Two Factor Authentication, TouchID, Mobile Search, Dark Mode, Portrait Mode (iOS 13 updates in general) have been the requested features that we've pushed out. You mentioned a lot of these in your original post and I know these aren't things you have prioritized, but they were a large portion of the requests we had received before they were launched.

    The heavy hitters that remain open but not yet on that list are Reconciliation & Undo on Mobile and Sharing a budget with a partner which you also mentioned. There are other requests of course, but these are the ones that are higher in number of requests as of right now.

    3. Roadmaps are tricky, and we purposefully don't keep ours public because things change, minds change, the whole world shuts down and we want to remain flexible. It is our primary goal to build an app that helps people gain control of their money.

    Our focus for building features are currently sitting in these main categories: First Time Users (aiming to reduce that steep learning curve to use the app when you first sign up, think goals, etc.), helping partners share budgets & budget together (pretty self explanatory, but it's a complicated project), Direct Import Improvements (we're always working on this and you'll see some big updates coming soon but it's not outside the US & Canada) and helping users reduce debt (building features that will be more helpful to those who want to crush debt, credit card improvements, etc.).

    These are themes, places where we want to be helpful, not necessarily the specific features any one person might imagine. It's possible these themes could change (especially as we start to form a picture of how this pandemic impacts the world) and that's not a complete list, but I hope it's helpful to see those main categories listed out.

    One quick thing I wanted to mention, and I'm sure you've seen it here before, is that anytime you have new ideas or information to add to requests that you've made before or if you're simply looking for a timeframe on a feature, you'll want to let our team know via our Feature Request form. Our Product & Design team reads each and every one and takes your feedback to heart. 

    Like 3
    • Veronica You're missing the key complaint. 

      One complaint might be that YNAB isn't making the features a particular user wants.  That's what you are addressing.  You make very fair points, on which reasonable minds can differ.  But that's not the heart of the criticism.

      The compliant is that YNAB is just not improving the product at a reasonable pace.  I would be ok with "We're prioritizing other features because xyz reasons".  What really is inexcusable is the lack of product development, of any kind. 

      I've been in SaaS start ups for awhile now.  You have a robust engineering and product team.  You should be shipping more features and iterating on existing features more quickly.  

      Everyone would be more patient if it appeared that YNAB was actually making progress.  

      Like 5
    • Tan Wildebeest So Veronica are you not going to even reply to this user? As they said, you didn't even come close to answering the core question which is why the inexcusable lack of development for a SAAS product?

      Like 2
      • Til Debt Do Us Part
      • Divorcing Debt - Not Each Other
      • debt_do_us_part
      • 6 mths ago
      • 6
      • Reported - view

      Tan Wildebeest Forest Green Stallion Maybe she isnt responding because there isnt an "inexcusable lack of development". If you go through the Release Notes (yes, you have to actually research and look. The fact I spent the time to do this shows how much I let this forum get under my skin.) YNAB is averaging 2 feature releases a Month since last year. Not bug fixes. Feature releases. I dont know if you're all discounting these features because you didnt ask for them, because you didnt want them or because you don't like them. Maybe you havent been using YNAB long enough to see them all? Maybe they're not "big" enough for you. Regardless of the reason though, they're there. If you're not willing to recognize what YNAB has already done, I dont think it's fair to speak on what they havent done. Or, if the "slow" progress is really that big of an issue, stop giving them your money and filling the forum with these repetitive asks for features they said they arent planning.

      Like 6
      • Woolloomooloo
      • Risk
      • Lavender_Moose.2
      • 6 mths ago
      • 5
      • Reported - view

      Til Debt Do Us Part Thanks for this, you saved me the trouble. People generally vastly underestimate the resource requirements of making changes to widely-used and complex software. The cost of change is not related to the change itself, but the complexity of the thing you're changing, paraphrased from Dave McComb's The Software Wasteland, but a quote I really like.

      SaaS isn't necessarily correct;ated with fast iteration and feature-development. In fact the opposite can be true, because with traditional software the customer/client can choose when and how to adopt a new version. With SaaS, this isn't possible, which adds testing cycles (particularly regression, which while is relatively easy to automate still steals cycles from resources that would otherwise be developing). 

      If you're a product manager at a start-up, or releasing new SaaS features that can be adopted or ignored because they're a new product, then you don't have to worry too much about regression testing until you make version changes. Even then if the customer can choose to adopt or reject the new version, because they can do their own testing before implementation, so you get additional comfort. But if you're changing a product used by hundreds of thousands of people who MUST adopt the change (SaaS model), it's likely a huge time vampire and quite costly if you include the fixes needed both before and after release. Reading about Kanban theory on wikipedia doesn't make one a product management expert. And SaaS is banded about often by people who actually have no idea what it is.

      One other thing - I've seen YNAB advertise a few jobs in the development team over the years, and they really do look after their staff in terms of benefits and work/life balance. So while many companies push out features more frequently (perhaps with more issues) I think I'd rather support a company that cares about it's workforce than one that fixates on its turndown rate - usually correlated with a burnout rate - that's an engineer joke...

      Like 5
      • nolesrule
      • YNAB4 Evangelist
      • nolesrule
      • 6 mths ago
      • 4
      • Reported - view

      Woolloomooloo We've been having this same discussion for 4+ years.  Not 4 days, not 4 weeks, not 4 months. 4 years. We would expect some kind of serious progress over that kind of timeframe. Took 4 years to add 2 goals.

      And some of us have extensive experience developing SaaS and Web Applications. We don't need it explained to us.

      Like 4
      • dakinemaui
      • dakinemaui
      • 6 mths ago
      • 8
      • Reported - view
      Til Debt Do Us Part said:
      YNAB is averaging 2 feature releases a Month since last year. Not bug fixes. Feature releases.

      Please list a single new feature that was released since last year. Not bug fixes. Feature releases. (Don't even start with Apple Sign-On instead of signing on with a password. Something of substance, please.)

      Some of us do actually research and look... and are disheartened.

      Like 8
      • Til Debt Do Us Part
      • Divorcing Debt - Not Each Other
      • debt_do_us_part
      • 6 mths ago
      • 2
      • Reported - view

      dakinemaui That's you discounting the feature because you didnt ask for it or because you dont like it? I can only imagine the amount of "substance" necessary to meet Apple requirements. I can also imagine the number of people who said "No fair! People can login with Google but I want to log in with Apple". I strongly believe that the features you want just arent requested by the masses. You're out numbered. 

      Experienced users arent asking for a fix for SFTF because they know what it is and how to deal with it and new users arent asking because they dont know. So focusing on first time user needs seems like the best way to get what you want, but others are still upset by this for some reason. 

      Based on your criteria, nothing other than a major change would make you happy (though, it can be argued that sign in with Apple Is major, but whatever). Just to address your question though, the new payee search feature functions how a lot of you requested now (I'm on my phone or I'd bother linking that thread), the new report colors are really nice and split transactions through the API is a big deal. 

      Obviously you know how averages work and the three I mentioned dont have "substance" to you but, again, they're still there. 

      Like 2
      • nolesrule
      • YNAB4 Evangelist
      • nolesrule
      • 6 mths ago
      • 1
      • Reported - view

      Til Debt Do Us Part 

      Til Debt Do Us Part said:
      Experienced users arent asking for a fix for SFTF because they know what it is and how to deal with it and new users arent asking because they dont know.

       It'd sure be nice to not have to mention it every single damn time there's an explanation about budgeting money to future months (it should be noted this isn't the only "help" place, official or otherwise, where people ask for assistance with YNAB).

      Also, most experienced users have kinda given up on asking for things at this point. This thread just shows that we haven't gone away since we saw an opportunity to be heard and tried to take advantage. Personally I don't bother with the most recent incarnation of the feature request form because it's just plain tedious. I'd rather freeform a request, and if someone has questions, they can reach out.

      Like 1
  • Veronica said:
    Our focus for building features are currently sitting in these main categories: First Time Users (aiming to reduce that steep learning curve to use the app when you first sign up, think goals, etc.), helping partners share budgets & budget together (pretty self explanatory, but it's a complicated project), Direct Import Improvements (we're always working on this and you'll see some big updates coming soon but it's not outside the US & Canada) and helping users reduce debt (building features that will be more helpful to those who want to crush debt, credit card improvements, etc.).

     

    Now, this really grinds my gears. You are flat out admitting there is a whole group of users for whom you aren't interested in improving the YNAB experience.

    Nothing in here about improving the efficiency of using the budget for long-time successful existing users. There have been people here using nYNAB for 4+ years. Many users that are not First Time users, do not share their budget,  and don't need to reduce debt.

    I won't even comment on Direct Import, because I don't really consider it much of a feature to begin with (okay, I did comment on it).

    So why isn't some focus on the needs of your long-time SUCCESSFUL users? Is it because you've already got them hooked so there's no need to waste time on them? There have been asks for feature sets that would improve the general work flow (reimbursement management, Stealing From the Future being the two most discussed), and after 4 years that's resulted in 2 new goal types (I can think of 3 additional off the top of my head that would be extremely useful) and not much else.

    Like 9
    • nolesrule Veronica So no response to this person either?

      Like 2
  • nolesrule said:
    Many users that are not First Time users, do not share their budget,  and don't need to reduce debt.

    To be fair, many users that are not First Time users do actually share their budget and do actually need to reduce debt (both bad and good types of debt).

    Like
      • nolesrule
      • YNAB4 Evangelist
      • nolesrule
      • 6 mths ago
      • 2
      • Reported - view

      Blue Wildcat I wasn't excluding the people in those groups. I was pointing out YNAB was excluding a major group of users who do not fit into any of those groups.

      Like 2
  • I’m still just hoping that someday the software will recognize that when I manually match Hulu for $13.13 with the scheduled Hulu transaction for $13.10 that I maybe meant to do that and it won't ask me again to acknowledge that I really really really did want the charge to be three pennies more and that I’m not going to hurt myself.

    Like
      • Superbone
      • YNAB convert since 2008
      • Superbone
      • 6 mths ago
      • Reported - view

      WordTenor My biggest irritant is when I’m modifying a transaction and I select Manage Payees in the Payee field and make my changes and come back out and it doesn’t automatically put this modified payee in the field! In fact, it still shows the same payee when I started the change! I have to then type in the payee I just modified. Maddening.

      Like
  • I've been using YNAB4 for 7 years. It turned my finances around in the first 9 months and at this point it's a religion :)

    I try out nYNAB every year or so. So I've had snapshots of nYNAB and its development over the years. I have to say that other than some colour changes the core of the product is pretty much stagnant.

    I've spent the last couple of days trying really hard to like nYNAB. I like the new interface, much slicker, but the workflow of nYNAB is just too different. My main gripes are lack of non-US bank support, no "Income for next month" workflow. Mulling over the forums to get other users opinions and I can see there are echoes of the same complaints throughout that have gone unanswered for years.

    There just isn't enough improvement from YNAB4 to make me move, even though I really want to and am willing to pay the premium, the neglect of the product is a major turn off.

    It's just... dissapointing. :(

    Like 4
      • Superbone
      • YNAB convert since 2008
      • Superbone
      • 6 mths ago
      • 1
      • Reported - view

      lazynooblet For what it's worth, the income for next month workflow is a must for me and there's a pretty simple workaround. It only requires a few extra clicks a month. All my income flows into an Income for Next Month category automatically and then it's just a simple matter of releasing the funds to To Be Budgeted at the end of the month and budgeting all of next month with a few clicks using the quick budget functionality. Search the forum for "income for next month" for more details if you're interested.

      Like 1
  • One thing I've been very aware of lately is that many threads here end in "Just send us an email! I'm so happy to help!" 

    However, this is often down to a person not understanding basic functions of the software. YNAB 4 had a somewhat self-selecting group because honestly, it was a little opaque and it required a bit of financial know-how; at least the very basics of the ideas of reconciling accounts, maintaining an accurate ledger, and an ability to think in terms of account and cashflow management. So YNAB 4 users usually figured out the less-than-inuitive parts of the software. (prime case in point, Patzer’s formula in YNAB 3.) 


     It strikes me that many of the issues facing  confused nYNAB users boil down to these basic misunderstandings about how money works and how YNAB represents those workings. But the software isn't designed to help at that level, and sometimes runs completely counter: e.g., I just happened to be updating my credit card payment transaction amount for May, since the statement just landed in my inbox. Because of screen space, the bit at the top of the screen says "payment" instead of "reserved for next payment.” If you don’t understand YNAB, and barely understand credit cards and checking accounts to begin with, a spot in the ledger which says “payment” is most logically interpreted as “this is the next payment amount” which then leads to “why doesn’t it match what my bank says I have to pay” and then we’re off to the help races. Even if you look at the little GIF in the popup, if you fundamentally don't understand the idea of envelope budgeting, it's not going to make much sense. This is a problem that is fractally recursive across the entire platform, where the way YNAB has done it only makes sense if you already understand how YNAB does it.

    What continues to be missing is some way that the software itself helps people understand these concepts. This would cut down tremendously on the veritable army of support reps who seem to exist principally  to hold the hands of people who are baffled by design of the software. Instead of making the interfaces less opaque and more intuitive to someone with a very low baseline of financial knowledge (which seems to be YNAB's new target market--understandable as it's a much larger market), money seems to have been sunk into support reps to answer every beck and call. 

    This is backwards. Sinking effort into development instead of support ultimately provides better support, and to boot, creates people with financial knowledge. YNAB used to describe itself as an education company that made software. Now it's a software company with a staff supporting unintuitive software. 

    Like 8
  • People plan week to week and month to month, life and its events does not just "flow" continuously without landmark and neither do finances. Having walled months is an absolute requirement for me. The software also got PRICEY very quickly. I'd drop twice what I paid for YNAB4 in a heartbeat to if they moved away from SaaS and back to "boxed" software and I'd still come out ahead. So that tells you whom SaaS benefits financially and it isn't the consumer... not to mention unavoidable "upgrades".

    I've had software make changes that I didn't like, and I just rolled back to a previous version. This is not generally supported with SaaS. Don't like a change? Too bad, so sad.

    Like 1
  • Veronica said:
    Our focus for building features are currently sitting in these main categories: First Time Users (aiming to reduce that steep learning curve to use the app when you first sign up

    Given the majority of new posts in these forums are "First Time Users", this is contrary to your actions. Zapier integration?? Linking to Amazon Alexa?? Riiiiight.

    Here's just a few of the issues have plagued these new users OVER AND OVER during the last 4.5 years:

    • "I make a budget entry, but TBB stays at $0." (a.k.a., Stealing From The Future)
    • "TBB doesn't match what is in my checking account." (Segregate cash accounts in the account area and don't include credit overspending in Total Available. The budget is the plan for CASH. Make a ToolTip on the Cash Rollup that indicates this is the money in the budget, distributed between To Be Budgeted + Total Available + Budgeted In Future.)
    • "I categorized something as TBB, but it doesn't show up in TBB." (Display "Debt Management" instead of TBB in credit accounts.)
    • "I pay my CC off every month, but my Payment category is red." (Enter the correct budget entry for them at account creation if they indicate PIF. At least get them off to a good start. Track their PIF status and mention in the Inspector if they used to be PIF but now aren't.)
    • "I deleted a category and merged transactions, but now my budget is hosed" (Finish the implementation by merging budget entries as well. I am floored that you stopped half-way.)
    • "I've totally messed things up and want to revert back to yesterday's budget, but I've refreshed the browser." (Persistent / time-stamped Undo)

    Knock off a few of these and first time users won't have to resort to forum posts to figure out what the heck is going on.

    Like 10
      • Superbone
      • YNAB convert since 2008
      • Superbone
      • 6 mths ago
      • 4
      • Reported - view

      dakinemaui I don't know how much you like your day job but can we put you in charge of the YNAB development team?

      Like 4
      • dakinemaui
      • dakinemaui
      • 6 mths ago
      • 5
      • Reported - view

      Superbone Being in charge of developers is like herding cats. Takes a stronger will than I have. :-)

      Like 5
      • nolesrule
      • YNAB4 Evangelist
      • nolesrule
      • 6 mths ago
      • 5
      • Reported - view

      Part of my job is herding developers. But it's also coming up with workable solutions. I like that part.

      Like 5
    • dakinemaui YES! Exactly! And in the order you placed them. 

      Like 1
  • There isn't a whole lot I can add to this topic that I hadn't said in my reply above.

    The features we've built are all listed in our Release Notes page, and it is work our team is immensely proud of. We're likely always going to disagree on what is a "substantial" release because what one person wants to see isn't what all people want to see. 

    nolesrule I'd be curious to know what you would consider to be a successful user? I'm sure this looks different in many situations. Is it someone who has a certain amount of money, zero debt? Someone who has a one month buffer sitting in their account? Or someone who feels comfortable rolling month to month and using the YNAB method? I think it's really straightforward to identify where the first time users need help, but that doesn't mean we're leaving everyone else out. As I mentioned, the list of themes I gave isn't every single thing we're working on, but we do not have a group dedicated to "successful" users at this time. 

    dakinemaui Yes, we had earlier been working feature by feature but recently adjusted production to be based on some the themes above. I'm excited for the First Time User team to start pushing out features that will help reduce some of those duplicate threads we see here from brand new users. WordTenor The work this team is doing will also reduce the amount of times we need to help someone 1:1 in support, yes. 

    Like 4
      • nolesrule
      • YNAB4 Evangelist
      • nolesrule
      • 6 mths ago
      • 8
      • Reported - view

      Veronica I defined Successful user in my response. Someone who has the hang of YNAB and doesn't fit into any of the groups you mentioned. Users who have gotten ahead and have things under control.

      I'm looking for features such as:

       

      1. Fix Stealing From the Future by making overbudgeted globally accounted for in TBB (your entire budget is overbudget, not just the farthest month funds have been budgeted to
      2. Income for Next Month as an income category so we can all stop jumping through hoops
      3. Built in reimbursement management solution (offset category groups)
      4. A true monthly budget template function
      5. Monthly funding goal with a max available cap
      6. Monthly funding goal calculated on a combination of averages with a cap that equals the monthly  average + sum of monthly overage of the last 12 months
      7. Funding goal that takes multiple dates of outflows into account to derive the least needed funding amount to meet all outflows
      8. Ability to add a custom round up figure to any calculated goal
         
      Like 8
      • Veronica
      • Support Manager
      • Veronica_ynab
      • 6 mths ago
      • 2
      • Reported - view

      nolesrule Thanks. I would use 7 all the time. I just sent those (all but one, I'll explain why) to our Product team on your behalf. The one I didn't send was number 4, but only because I'd like more details on it. Is there another thread or a small 1-2 sentence summary I can send to them that might give them more detail to work with?

      Like 2
      • dakinemaui
      • dakinemaui
      • 6 mths ago
      • Reported - view

      Veronica #4 (a true template function) is something that does not clash with Rule 3. Once entered, the budget value can be changed without being nagged the rest of the month -- #lifehappens

      Like
      • WordTenor
      • I have the honor to be your obedient servant
      • WordTenor
      • 6 mths ago
      • 1
      • Reported - view

      Veronica There’s a really lengthy conversation about it between me and Todd in about September 2015 (It was before the launch of the credit card function rebuild, which was October). It pre-dates the in app tool, so I don’t have the record of  it (I just checked my email backlog) but it’s probably in the logs somewhere. 

      Also it’s in the feature requests pile. I know I’ve submitted it formally at least once, and I don’t think I’m the only one. The basic use case is this: each month, I budget $x for dining out, $y for groceries, and $z for fun money. I will cover all these things with each other so it doesn’t matter what they end up being, so long as together I don’t spend more than $x+y+z. It would be nice if I could set a goal and use quickbudget to budget the initial amount. But since the goal is designed to nag if I don’t budget the minimum, the minute I make the perfectly sound choice to repurpose “dining out” to “groceries” because of quarantine, I get a yellow warning. So there are a handful of categories I must either budget by hand, or ignore their warnings. I do a mix of both in practice but it’d be nice to be able to use quick budget.

      Like 1
      • nolesrule
      • YNAB4 Evangelist
      • nolesrule
      • 6 mths ago
      • 1
      • Reported - view

      Veronica here are a couple more UX items I'd like to see related to Scheduled transactions:

      1. The ability to peel off the next recurrence of a transaction without "Enter Now" changing it to today's date. So let's say you have a monthly recurring transaction scheduled for 25 April. I'd like to be able to enter in this occurrence while keeping the 25 April date, and then have the recurring one advance to 25 May. 90% of the time I have to use "Enter Now" and then adjust the date. I rarely use "Enter Now" to actually enter now.
      2. The ability to skip the next occurrence in a recurring transaction. Sometimes I just want to skip the next one. Instead I have to "Enter Now" and then delete it.
      3. More complex scheduling engine for recurring transactions. While I don't think it needs to get as advanced as accounting for bank holidays (although that would be a nice to have and not quite sure how to make that work globally), I'd like to see more options like "Last day of the month",  Xth <weekday> of Month (e.g.  3rd Wednesday), and an additional option to shift a day to a prior weekday if a date falls on the weekend.
      Like 1
      • nolesrule
      • YNAB4 Evangelist
      • nolesrule
      • 6 mths ago
      • 2
      • Reported - view

      Veronica One more thing about Scheduled transactions... but this one has been bugging me since the YNAB4 days and I just find it hard to believe it hasn't been addressed in all these years

      If I set a specific date at the end of the month, I want the recurrence to maintain the specific date even if it pulls forward for a shorter month. For example, I get paid on the last day of the month. So I set it to trigger on January 31st. Then in February, it triggers on February 28th (or 29th this year). In March I would expect it to trigger on the 31st, and in April on the 30th. But the way it works now, every month after February it triggers on the 28th/29th. I am constantly fighting with the scheduler.

       

      And this isn't an issue for my pay check only. I also have Scheduled transactions for my interest bearing accounts, almost all of which post on the last day. I also use these as a reminder to reconcile some of my tracking accounts. The date shift becomes annoying.

      I bring this up now, because today is April 29th, and I just had more than a dozen of these pop into my register. Yet tomorrow is the last day of the month.

      Like 2
      • Til Debt Do Us Part
      • Divorcing Debt - Not Each Other
      • debt_do_us_part
      • 6 mths ago
      • Reported - view

      nolesrule Mine currently do exactly what you described. My last day of the month transactions were dated 1/31, 2/29, 3/31 and April's is sitting for 4/30. I know I read somewhere that this only works if you date the transaction for the 31st. Maybe delete and re-enter come May?

      Like
      • nolesrule
      • YNAB4 Evangelist
      • nolesrule
      • 6 mths ago
      • Reported - view

      Til Debt Do Us Part I'll experiment with one of them before I do that with all of them, as that would be a lot of extra work for nothing if it doesn't work. It's possible it's because the were migrated transactions.  Migration was not a seamless and flawless process.

      Like
    • nolesrule Mine also work as expected. If the first time I schedule it is during a short month, it will reoccur on the 30th, but if i schedule it in a long month, it will always pull on the actual last day of the month. It's worked that way for a year and a half.

      Like
      • nolesrule
      • YNAB4 Evangelist
      • nolesrule
      • 6 mths ago
      • 1
      • Reported - view

      Move Light Sound Life Okay, so it's a good chance mine are due to migrated transactions. Like I said, I'll experiment the next couple months and see what happens.

      Like 1
      • bobbucy
      • Tomato_Snow_237e7f17927
      • 5 mths ago
      • Reported - view

      WordTenor I submitted a budget template feature request in YNAB4 so many years ago that I can't even remember exactly.

      Like
    • nolesrule 

      nolesrule said:
      More complex scheduling engine for recurring transactions. While I don't think it needs to get as advanced as accounting for bank holidays (although that would be a nice to have and not quite sure how to make that work globally), I'd like to see more options like "Last day of the month",  Xth <weekday> of Month (e.g.  3rd Wednesday), and an additional option to shift a day to a prior weekday if a date falls on the weekend.

       In addition to these, I'd like to see more granular control over timing.  Why can't I set a recurring transaction for every 6 weeks for instance?  Instead of the existing fixed weekly/monthly/annual schedules, it should be every X weeks/months/years where you enter in your desired frequency.

      Like 3
      • Falconar
      • YNABer since 2010
      • falconarx
      • 5 mths ago
      • Reported - view

      nolesrule I'd also love to see better recurring transaction handling, I'm forever adjusting transactions that fall on a weekend, and the inability to enter future-dated transactions makes it harder than it should be. I have to wait for them to happen on the wrong day, then move them to the right one. 

      I agree with a lot of the feedback in this thread, development pace is glacial and most of the updates seem to be trivial tweaks to the UI. Stealing from the future and reimbursement are big issues for me, and please do better with reporting - I can remember this being promised years ago as one of the reasons for the SaaS model, but  years later it is still so basic. 

      Regarding making nYNAB easier for newcomers, as a long-time YNAB user (since YNAB3 in 2010) I find a lot of what nYAB tells me is confusing. YNAB4 was so simple and the buffer plus income for <next month> literally changed my financial life, but yNAB is so much harder to understand. Age of money seems to be an arbitrary number, it's in the 90s for me so I ignore it, and I also have never really understood TBB properly (coupled to the SFTF issue). And neither Funds for May nor Total Available make sense either - they don't obviously map to any other number. Credit cards are just weird, I pay in full each month so ignore it, but don't understand these numbers either. Overall I probably don't understand where fully half the headline numbers on the budget screen come from, so i'm not surprised that newcomers don't either.  

      My income is substantially higher than my outgoings so can get away with ignoring the details; I budget to somewhere near zero (not exactly zero, as I've lost the buffer from YNAB4 and so it's harder to know what zero is), don't overspend budget categories, and it all kind of works out. But as far as i'm concerned, nYAB took something that worked brilliantly and made it significantly worse. 

      Only thing keeping me on nYNAB is that i've not found an alternative yet. I'm parallel-running Banktivity which is ok (and far superior for reporting) but transaction entry is clunky, direct import is broken there too, and I can't understand its budgeting. But I feel like i'm getting very poor value from nYNAB right now, and I can't imagine renewing if I can find a suitable alternative. 

      B. 

      Like
  • Veronica said:
    I'm excited for the First Time User team to start pushing out features that will help reduce some of those duplicate threads we see here from brand new users.

    I will be very happy to see such features released. I would greatly appreciate it if you would please forward  the common issues and suggested solutions I mentioned above to the team.

    Like 4
      • Veronica
      • Support Manager
      • Veronica_ynab
      • 6 mths ago
      • 2
      • Reported - view

      dakinemaui Sure thing. I sent your list right to our Product team on your behalf. 

      Like 2
      • dakinemaui
      • dakinemaui
      • 6 mths ago
      • Reported - view

      Veronica Thank you very much!

      Like
  • I have to say I agree. $84/yr is just too much for what we actually get (if it were $60/yr I would find that much more reasonable, of course now that you have gotten use to the high selling price I don't expect you will ever lower the price, even it that means getting  more users for higher overall revenue). But despite that I have not found a good enough alternative to switch to, so I am stuck overpaying for ynab I guess, but as soon as I find a viable alternative I for one am jumping ship!

    Like
Like12 Follow
  • 12 Likes
  • 3 mths agoLast active
  • 50Replies
  • 1311Views
  • 28 Following