Skip to main content

Stop saying thank you in release notes

HI @Fabian

I am coming from strong UI/UX background, so please heed these 2 pieces of advice. Virtually 100% of the userbase will agree with this IMO:

  • I would recommend against “thank you for using budget flow blurb in the version history.” It clutters up the “what’s changed” screen in iOS and makes it difficult to see what’s actually changed. I’m sure there’s loyal BudgetFlow users that check to see if anything useful has changed to see if any useful stuff has been added.

  • Also be specific with what specifically has changed. Too many companies use “ stability and performance improvements” and it’s annoying to see that. If there’s bug fixes, say what bugs were fixed.

Status: Completed5 comments

Log in to comment and vote

Comments5

  • moneytracker2948

    •

    Jan 22, 2025

    Whoops! My title got cut off, Lol. It was not meant to say “Stop” in as much as “Stop saying thank you in release notes”

    • Fabian

      Team•

      Jan 29, 2025

      Hi @moneytracker2948,

      Thank you for your feedback!

      I totally understand your point, but there are times when the changes are very small or technical, and in those cases I tend to use phrases like "stability and performance improvements" or "adjustments to the user interface" because it's hard to be more specific.

      However, for major changes that might be of interest to non-technical users, I make sure to list them (like the ones in the latest release). And for really big features, like the search functionality introduced in version 2.1.0, I also show a pop-up view after the update that lists the new features (which can also be found under "New Features" in the settings).

      Nevertheless, I'll definitely try to include more details in the release notes in the future!

      Best regards

      Fabian

      • moneytracker2948

        •

        Feb 8, 2025

        @Fabian Thank you so much for keeping an open mind. I am find with stability / adjustments if it’s hard to be specific.

        I would recommend though to stop putting “Thank you for using budget flow!”
        Alternatively, if you’re really wanting to do that to increase exposure, I propose moving that entire section to the bottom of the changelog so users can easily see the changes.


        A picture is worth a 1000 words. This picture should convince you about what I am talking about. I can’t see what the changes were without going into each one and clicking because of the thank you text. Users won’t like this.

        https://imgur.com/a/GzcRVHp

        • Fabian

          Team•

          Feb 10, 2025

          In general, the text could be reversed, i.e. list the changes first and then write the "Thanks for using" section. But from my point of view it probably doesn't matter, because you would have to click "More" anyway to see all the changes. Or how do you see it?

          • moneytracker2948

            •

            Feb 10, 2025

            Reversing the text would at least show 1-2 lines of changes. IMO. it would be an improvement IMO from what we have now.