Ocassion: Retail Product Categorizaion tool released
Updates: I'm finally getting things to flow r.e. updates with quicken. When you think of the business model, the number of way's Quicken can be accessed, desktop, multiple OS's, Web, Phone app, Tablet, the intense, intense need for security, it's the Grand-dady of tools, for me. Though, some bugs exist that, gee, after all this time, that bug still exists, give me a break.
Legacy and New: What do we want, Quicken to be the "Word Perfect" of finaincial managment software? For those who don't remember, Word Perfect was way out in front of MS "Word". They got trapped by several things and went out of business - their legacy software, and customers, were part of the fall.
Getting Amazoned: The new Retail Purchase Categorization tool worked well for me today, first time use, I took in the last 90days. Some atypical quicken bumps along the way, would have gone smoother if I had read the instructions. Men don't ask for directions, until they are desperate, and blamming the "navaigator" in the passanger seat. Some will stop shopping Walmart, Target, Temu becuse they cannot auto categorize, and split transactions. What demographic group(s) are represented in quicken users? The one's retailers want to capture.
The "problem" space, merge evertying financial, they are trying to solve the problem in is VERY complex.
Security Has to be job #1. I can suffer some GUI glitches, so long as the backend is absolutly bullet proof. Almost all software switched to a SAS business model becuse they had to, developers are way stupid expensive. Thank God Quicken is not a DOD product... yet.
Complex! Quicken supports multiple operating systems, multiple browsers, desktops, tablets, phones - for both Apple and Android, supports legacy stuff, does finance stuff, does tax stuff. This is expensive software to implament and maintaine, very expensive. I suppose they have to do some monitizing, and will probably have todo more to keep the developers paid and the owners making money.
Tight Coupling, the competiton faces it too: Will the Retail Purchase Categorization tool continue to work and get better? Retailers do not have to coporate.
There are several places in the software that are trying to provide solutions in "the problem space" that are fraught with the dangers of "tight coupling". See footnote. 80% of the solution to the problem is rather easy, the other 20%, that most budget like tools leave out, costs 80% of the development dollars. Over the last thirty, forty, years, I've seen dozen's of products come and go. There is no free lunch, there is no way to do all Quicken does, on as many hosts as it does, and do it on the cheap. The power of it intimidates and frustrates the newbies. But once your networth get's above some threashold, and you don't want to pay an accountant, you go Quicken.
AI to Make Quicken Better: With AI writting more and more code, the question is, will Quicken get better via the developers having better tools, or will it be replaced by AI? I have to wonder what new tools will help them r.e. development, in the future. Stuff from or like Palantir products. Read, for those who understand, integration of traffic managment with tracking money, doing development - AND TESTING better, not to mention marketing and tiering of customers, and AI customer service and help interfaces.
Foonote r.e. tight coupling, for those who don't know...
Tight coupling in software and systems refers to a state where two or more components are highly dependent upon each other, meaning a change in one component directly necessitates a corresponding change in the other. In a tightly coupled architecture, components are deeply intertwined and often share concrete implementation details, internal data structures, or specialized hardware requirements.
Ripple Effects: Modifying the internal logic, data schema, or behavior of a single module breaks functionality elsewhere, requiring a chain-reaction of updates across the system.
Low Interoperability: Components cannot easily be swapped out, upgraded, or repurposed in another system environment without extensive rewriting.
High Interdependence: System layers or services are combined so closely that if one goes down or suffers from latency, the entire application fails to operate.
Quicken, you've gotten better, keep it up, don't become the Word Perfect of finance mangement tools.
