Thank you for your patient explanation! A very valuable perspective —- people are not willing to continuously pay for something static that doesn't get updated. Actually, I have plans to develop some features that require a server, but as you mentioned, perhaps I should put the blueprint in the README or on the homepage to make users feel it's worth continuously paying for.
Can I conduct a small survey? I previously considered offering a feature to store users' JSON in the cloud, but I didn't see the need since there's GitHub Gist, and you can always use that, so I didn't implement it. From your perspective, would you need such a feature?
Can I conduct a small survey? I previously considered offering a feature to store users' JSON in the cloud, but I didn't see the need since there's GitHub Gist, and you can always use that, so I didn't implement it. From your perspective, would you need such a feature?