We are continuing to experience delay with the launch of Savings 2, in fact, we have yet to official put out the first beta.
Things are starting to fall in place though. Stay tuned.
Again, if you would like to paerticipate in beta, please sign up.
Thanks for your patience.
p.s. For people who are experiencing sync issue that cannot be resolved by our sync troubleshoot page, please sign up for the Savings 2 beta. We will not be fixing sync issue in Savings 1 because our resource is very limited.
Savings 2 is coming. Yes, we know, our schedule has slipped a bit, but hey, this is software 😉.
What we won’t compromise on though, is the quality. We are taking the time to get it right. For those of you who loved Savings 1, you will feel right at home on Savings 2, and will appreciate all the fit and finishes that is at a level above Savings 1.
Sign Up for Beta
We will soon be releasing Savings 2 for beta testers. If you are interested, please sign up to become a beta tester.
And as always, we love to hear from you if you have any questions.
In case you are wondering why Savings hasn’t been updated for a while, there are two reasons. One, the team has had some internal changes lately, and that had an impact on our release schedule. Second, we are working on something very exciting that we plan to ship later this year. We can’t talk about it yet, but if you want to be the first to know, be sure to sign up to our newsletter for announcement.
Savings for Mac 1.8.2 has just been released on the Mac App Store. This is a quick update that addresses two issues that were introduced in version 1.8.1.
The first is a crash that sometimes occur when you are entering the payee of a transaction. The second is a crash that sometimes occur when you are importing transactions from bank.
Please update to this version of Savings if you are experiencing either of those issues.
In this update, I focused on improving small bits of the user experience in the Mac app. Things like payee and category autocomplete, increasing the size of the balance footer, and clearing new flag when editing multiple transactions. It is also easier now to delete accounts and budgets from the sidebar. Just press the delete key or use the contextual menu.
Sync is also improved for the Mac app. If you keep Savings running in the background, it will receive updates from iCloud. So whenever you activate Savings, you will see the latest data without waiting for refresh. This brings the immediacy of sync inline with the iPhone app.
To get the update, visit Savings on the App Store.
I’ve been asked several times if there is a guide for newbies to learn everything they need to know about using Savings. That is, in fact, what I am working on these days. I expect to have it released within the next couple of weeks. So keep your eyes peeled on the website!
I’m happy to kick off the year with an update to both Savings for Mac and Savings for iPhone. There are many new features planned for 2016, so please stay tuned to this blog for future updates.
The main new feature Savings 1.8 (Mac) and Savings 1.3 (iPhone) is the ability to lock Savings with a password or passcode when you are not using it. This is a highly requested feature, and now, both apps have the ability to do so.
To activate password on the Mac, just go to the Securities tab under Preferences.
To activate passcode on the iPhone, just go to Settings > Passcode.
Push sync refers to the ability for a change to automatically be pushed to all your devices once it is made on one device. The end result is whenever you open the app on any device, the latest data is already there.
This functionality is now a part of the iPhone app, and will soon be brought over to the Mac app. Be sure to allow Savings to send you push notifications when you are prompted.
Savings also now shows you an activity indicator when its syncing data. Please note that on the Mac, you have to be running El Capitan to see this.
To make sure your data is never lost, Savings now makes a backup of your entire database regularly. If you ever need to retrieve the data, you can contact support for instructions.
Subscribe to this blog via RSS.