If you've still got your plan up, happy to give you an extended trial if you want!
But overall I think you're right on both points. I've been wanting to add better support for modeling options for a while; for anyone who'd like to bump priority there, feel free to upvote this item in changemap: https://changemap.co/projectifi/projectifi/task/5735-better-...
For #2, I'll do some thinking to gauge level of effort in rigging up a mechanic like that with the current stack. Losing data sucks, and I should take more steps to reduce the chances of that happening to anyone in the onboarding funnel.
I could see allowing only localstorage saving with no option for exporting or importing of data being limiting enough for me personally to have enough reason to upgrade to pro, maybe limit the number of plans you can have (if you haven't already, I haven't tested it) as well as the number of times you can actually save to localstorage.
I liked this enough where I made a model during my lunch break, then remade it when I got home, and then remade it a third time after I had accidentally pressed the "back" button on my mouse talking to someone on Discord, taking me back to the landing page and losing all my data.
After that last one I decided to at least get the free trial so I could save, but I had already planned pay for Premium so I wasn't too bothered.
How would you recommend enforcing a limit on number of localStorage saves? If the number was held in localStorage as well, that's easily circumvented, and even if the save number was stored in Firebase and associated with the auth ID for the account, seems to me like people could probably just create a new account as needed and adjust the localStorage content to match, with a few lines of JS.
But overall I think you're right on both points. I've been wanting to add better support for modeling options for a while; for anyone who'd like to bump priority there, feel free to upvote this item in changemap: https://changemap.co/projectifi/projectifi/task/5735-better-...
For #2, I'll do some thinking to gauge level of effort in rigging up a mechanic like that with the current stack. Losing data sucks, and I should take more steps to reduce the chances of that happening to anyone in the onboarding funnel.