I originally thought this was a no-brainer, considering how easy it is to use Google Sheets, and the fact that it’s free, but some recent developments in the spreadsheet war have me wondering on the best direction. It’s always felt like Tiller leans heavily to Sheets, but that might just be my impression.
Would love anyone else’s perspective on this as well. My guess is that it comes down to personal preference, but innovation might change that equation a bit.
Yeah, I think it’s both. Personal preference based on what you’re most used to plays a big role, but I can see changing when the feature set of one tool becomes more compelling than it’s competitors. Currently Google Sheets infrastructure is more friendly to a product like Tiller. If Microsoft changes that, many might consider switching to the Excel based Tiller as it either achieves more parity, or even is able to offer unique capabilities that the Google version can’t match.
In addition to what jpfieber said; while MS365 has the latest updates; there multiple version of excel and most wouldn’t interact with the direct online connection as well as google since that’s online first.
To an extent i felt except for online collaboration and sync, excel was a much better overall product with the hotkey and responsiveness.
I don’t mean Tiller specifically, but workflows that work the way Tiller does. From building Tiller templates for both Sheets and Excel, I founds Sheets templates are much easier to share than Excel are (I believe sharing was planned from the start of Sheets). Also we’ve heard from Tiller that doing things like “Direct Fills” was easier in Sheets, and is proving to be more of a challenge in Excel/M365
Fair points, both. I didn’t consider the sharing aspect, and that’s one of the many things I love about the product. Thanks for the replies. I really appreciate it.
It really goes back to how sheets was designed with online collaboration in mind so all of the add-ons already have scripts support. While excel started with a desktop version with being more vetted through an enterprise system and thus more clunky. obviously the upside of the latter is that everything can be local along with functions that don’t conflict with the browser’s.
