Closing out last year I took a good look at the merits of using DEVONthink to Go as an iOS only user. I am a fairly recent convert to DEVONthink more generally, but the more I use them, the more I understand their immense value.
As I prepare my own version of the indulgent listicles you see everywhere, I am reminded of the myriad ways I have integrated DEVONthink into my workflow. The thing that has surprised me most is the way DEVONthink has affected how I work on iOS. It has even solved a problem I suspect might resonate with a lot of other nerds, which is how to centralise your data if you’re an incessant app swapper. DEVONthink is so easy to get data in and out of, I simply keep everything there. 1 I recently had a brief twitter exchange that got me thinking about DEVONthink as an app silo. Seeing as I have this iOS giveaway for DEVONthink to Go, I thought I might also share a couple of quick thoughts on that
On the Question of App Silos
The way DEVONthink works on the Mac, makes this an easier question to answer on macOS. If putting everything into a database is a problem, you can use the indexing feature instead, and still take advantage of the search super powers. You data remains at large in the native file system. I intend to cover DEVONthink on macOS in the not too distant future, I will look at the pros and cons of taking this route then.
In the meantime, as that option is not available on iOS it might seem more cut and dry. I’m not so sure. This is a crude analogy, but in a sense the architecture of iOS makes it something of a modern day terminal client. Ordinarily, your data is always somewhere else. Even if you maxed out the storage option, keeping all of your data locally on an iPad is not only atypical, but seriously risky. Operating on those terms also tends to raise other considerations, especially concerning security.
Functionally, the question becomes how you access and interact with that data. The key for me is that DEVONthink doesn’t change the structure of your data, which is prec