nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Parity between Mac and PC versions of Quicken

msoultan

I find it quite amazing in this day and age that we still have software that doesn't have parity between platforms. It's horribly frustrating to work on someone's computer that's running Quicken for Mac, only to find that they don't have the same tools available to perform functions that are possible on the PC version. Please, Quicken, make the feature sets match between the two platforms.

Find more posts tagged with

Feature Request

Comments

jacobs

@msoultan It will never happen. Quicken Mac is built on very different underlying technology, from the database to many tools provided by the Mac operating system. Quicken Windows had decades of head start, and a larger development team, so there will always be differences. With those disadvantages, Quicken Mac also has some advantages because it was restarted from scratch more recently in order to keep up with advances in macOS. The ongoing hope is that Quicken Mac will add key features which currently exist only in Quicken Windows, but they will never be identical.

In order to make the feature sets of Quicken Mac and Quicken Windows identical, they would likely need to restart development of both around a common database and tools. That would be a massive and very lengthy process. Consider that the re-write of Quicken Mac started nearly 20 years ago (although there were a few lost years where former parent Intuit bungled development before things got back on course), and after all that time, the program has nowhere near all the features users want it to. It's just not going to happen. It seems clear that the long-term future for Quicken is the browser- and cloud-based Simplifi product, which doesn't have the inherent problems of different operating systems.

msoultan

I understand the two products have different architectures, but workflow parity for core tasks (bulk edits, category cleanup, split editing tools, etc.) should still be a priority. When users switch platforms or share files, it’s frustrating to discover essential productivity tools exist only on one platform. I'd ask that they attempt to have feature parity for the workflows power users rely on.