> Somebody please show me a downside to this model?
For whom? The user? It's an absolute clusterfuck. Always online video games have already done this shit, and it's been a nightmare for the end user, and that software doesn't do anything "important".
Can you imagine not being able to open or save your file because the servers are overloaded? Or getting charged a premium at the end of a long day because you weren't carefully counting your credits and you need to save your file?
I was just suggesting that something like this could be offered alongside existing models, and so offer a cheaper alternative to people who only want to edit a few files per month.
>Can you imagine not being able to open or save your file because the servers are overloaded?
This happens all the time in business since the world moved to the cloud. Microsoft is down? No opening or saving office files, say goodbye to email. Amazon down? Your website is now not currently taking customer orders.
> not being able to save a file you've worked on because you ran out of credits would be a serious issue.
Yeah I agree with that, I think I went down the wrong path with credits = individual functions. Ive since seen that Autodesk does a credits system where tokens are used for time using the software. I think thats a much better idea than mine.
For whom? The user? It's an absolute clusterfuck. Always online video games have already done this shit, and it's been a nightmare for the end user, and that software doesn't do anything "important".
Can you imagine not being able to open or save your file because the servers are overloaded? Or getting charged a premium at the end of a long day because you weren't carefully counting your credits and you need to save your file?