3 ms·
If there's no outwardly visible features your customers care about then no, don't charge for the upgrade. You should only consider charging customers for an upg
by taylodl 8y ago
If there's no outwardly visible features your customers care about then no, don't charge for the upgrade. You should only consider charging customers for an upgrade when something of direct value to them has been added to your app. In this example it sounds like you, the developer, are the primary benefactor of this change. It makes things better and easier for you. Once you've used the new framework to deliver something of value to your customers then consider charging them for it.
- hilti 8y agoThank you. My gut feeling told me something similar and you're completely right: I am the one who benefits. Well then I must first go in advance.