I like that this is a solo-dev project, but there's probably loke, a good chunk of people who like this tool likely have built some kind of spreadsheet or other thing to get close to it and likely know exactly what they would like to see for certain things.
Having the abilty to perhaps build our own models and keep them to ourselves, or maybe have them available to share might not be a bad idea.
I'm not sure if this is reporting, or setting up a sequence or frequency of payments, etc. Depends on the backend I suppose.
Having a little trouble parsing the specific feature ideas here. It seems like one of them may be an ability to share a read-only view of your plans... but on the other(s) I might need a little more detail.
* My Personal Stamp Collection API Plug-in (not-public, not-for-sale)
Basically, theres enough weird stuff out there that could be a component of someone's financial hopes and dreams, that communities could sprout on being able to enhance around a topic.
There's also that first step of needing/wanting to be able to API-into the product to explore the idea to see if it's even something that can be modeled.
Being from the UK, having a plugin layer able to differentiate US from UK implications on finances would be extremely useful. But also as a fellow developer I hate to recommend a level of refactoring that might break you!
I think this is because you are conflating "model" and "plan"; whereas the conventional use of plan probably means model, when playing in your Sandbox it looks as if "plan" is model+data.
The grandparent poster is describing sharing models.
Having the abilty to perhaps build our own models and keep them to ourselves, or maybe have them available to share might not be a bad idea.
I'm not sure if this is reporting, or setting up a sequence or frequency of payments, etc. Depends on the backend I suppose.