[ineedasername]

For something that needs to be editable and analyzed and shared among users that are highly proficient in financial tech (excel) but are not programmers, an app framework isn't going to work.

My work is often an input into the work of the finance folks where I'm at, and they have countless very complex excel docs. None of them are programmers, but all them (and anyone else moderately proficient in Excel) can look under the hood, see what's going on, and make their own additions/changes as needed.

And there may need to be new versions of all of these that have slight or major changes made on a monthly/quarterly/annual basis. No single build w/ a web-app framework is going to do this very well without a very large investment in developer costs, and that simply isn't necessary when there is already a perfectly good tool for their needs. Developer costs aside, it would also mean that these folks had a significant delay in their work: They could no longer clone last quarter's sheet and spend a morning making the necessary changes. They'd need to spend a few days going back & forth with a developer over the scope & specs of the changes, a little longer for the developer to write the code, do a bit of UAT, and assuming everything works as expected then get to the actual work and hope nothing new came up before next quarter that would stop their work for more dev time.

The types of systems that eliminate a little bit of this are part of industry-specific monolithic ERP systems, and even those may only cover the 60% of requirements that don't change often or are supported by contractually guaranteed TOS upgrades each quarter from the vendor.