We acquired RVCare LogBook (RVLB) from Jim Smith, who is retiring from software development, because we believed he had made a compelling product and we wanted to keep it alive to support the current userbase, and also continue developing and improving it, to attract new users. We still believe in all of that.
Our original intention was to ship a new version of RVLB last year, 2017, but the development time was eaten up by our main product, Server Ranger, and other work we already had on our schedule. We're getting back on track with RVLB now and I wanted to just take a moment and tell you what our plans for the product are.
The first release of RVLB from LibertyApp will be version 3.0 (the current release is version 2.7.11) and while we don't have an exact date yet, it will be available later this year. Version 3 will be our new baseline for the product and it will be the foundation of our development going forward. Version 3 focuses on two things: bug fixes and a visual overhaul. It maintains full compatability with previous versions and it will be a free update for anyone who owns RVLB of any version. It will be available for Windows and Mac, as always.
After RVLB 3.0 is released, we then move to improving the actual functionality of the product. You'll see more movement in this phase because we intend to release regular, small incremental updates, so that you get your hands on new features quicker. These feature updates will be community driven and to get your feedback, we will be launching a new forum for RVLB. The forum can be used for general discussion and bug reporting but it will also be used to discuss potential new features.
RVLB version 2.7.11 is still on sale (click the button below for the Mac version) and updates to version 3 will be completely free when available.
Are you on our mailing list? If not, please join it - we promise you'll get no more than 2 or 3 emails a year and we will only email you when we have something to tell you, such as the launch of the forum. If you have any comments or questions, please email me at email@example.com