Things 3.0.2
Cultured Code has unveiled Things 3.0, a major new release that introduces a redesigned user interface for improved workflows and clarity. The task manager gains a number of new features, including project headings that enable you to create categories, checklists to break down the details of a task, time-based reminders, and calendar integration for viewing your schedule for today and the upcoming week. The release also adds natural language recognition that autocompletes typing (such as “Tom(orrow)”), enables you to open multiple projects in their own windows, and adds app-wide tag filters that display all items across all projects and areas.
Shortly after the 3.0 release, Cultured Code pushed out two maintenance releases — version 3.0.1 to address minor post-launch fixes and version 3.0.2 to fix several crashes and resolve an issue that prevented the OmniFocus import script from importing deferred projects.
For those with a Things 2 license, there is no upgrade pricing for Things 3. However, Cultured Code is offering Things 3 at $39.99 (a 20 percent discount) through 26 May 2017, and a 15-day free trial is available from the Cultured Code Web site. Cultured Code has also updated its iOS apps to version 3.0.2 and discounted them by 20 percent for the same time period as the Mac app discount. That prices Things 3 for iPhone at $7.99 and Things 3 for iPad at $15.99. You will have to upgrade all versions of Things to retain sync capabilities, which won’t work
between Things 2 and Things 3. ($49.99 new from the Mac App Store, 12.1 MB, release notes, 10.11+)
I infer data is not portable between Things 2 and Things 3, but helpful to have that explicitly confirmed or corrected. Eg between mixture of Macs and or iOS 2/3.
I apologize - I've tried to make it more clear that there is no upgrade pricing for those with a Things 2 license. You should be able to bring your data from version 2 to version 3.
You can't sync between Things 2 and Things 3, i.e. you need to update to Things 3 on all platforms if you want to retain syncing. When you do the update to Things 3 it is very straightforward to import all your Things 2 data.
It's also worth remembering that with family sharing you can pay once & use the app (Mac or iOS) for multiple people in your family group.
Remember if you're trialing Things 3 to keep Things 2 installed. If you want to go back to v2 then you'll need to re-upload the To-dos from within Things 2, which deletes everything in Things Cloud.
If you uninstall Things 2 there's no way to get your info back once Things 3 starts syncing. Unless you have a system back up in Time Machine, etc.
There is a serious security issue with Things 3. In Things version 1, you could sync between devices over your private home network. In Things 2 and now Things 3, you must sync between devices using Things Cloud. The Things Cloud servers are in Germany.
Cultured Code's claims of security are deceptive and misleading. They say, "With Things Cloud, all your network traffic is securely encrypted using the latest SSL technology, ensuring that everything you do is for your eyes only." What they don't say is that once your encrypted Things data arrives at the Things Cloud server, it is decrypted and stored in human readable, plaintext form. It is not secure and it is not "your eyes only." Any curious Cultured Code employee with access can peek at your Things data. The only thing that stops them is Cultured Code's internal policies. Consider who might be using Things, and whether outside hackers or Germany's intelligence services might be interested in the data on the Things Cloud.
What about their comment about "Encryption at Rest"? https://support.culturedcode.com/customer/portal/articles/679590
The "Encryption at Rest" protects the data if the drives are physically stolen. Unfortunately, it does NOT protect your data from authorized Cultured Code employees, who have the keys to unlock the encryption at rest. If they can read your data, then there is always the possibility that foreign intelligence agencies and/or hackers may also read that data. They could steal all the data in Things Cloud. Or Cultured Code might simply share it with the German government. Who would know?
A far better implementation would have been if the users control their own unique keys to their own Things data, thus eliminating the concern that sensitive data might be breached.