So as I was reading through Rabbits vs. Turtles I started thinking about apps and their data usage.
Will apps be required to buy storage to store a users application data as that data gets larger or will the user’s app data be counted against the app user’s available storage amount?
It would seem right to me (as a classic web dev) that we don’t want to make it hard for developers to get started when they are building apps (ie perhaps their free space or other free space up to some amount). Then when the app is large enough (using more storage) we will want to have them purchase more space to handle the load of their app or require the users of the apps to use their own storage allotment.
As I understand things, the more an app is used, the more micro payments or app charges they might receive so this will/should play into things as well. Having enough farmers to handle all this data will be a HUGE deal. Incentivizing farmers will be a HUGE deal. Incentivizing builders with good ROI will be a HUGE deal. Incentivizing users with great apps will be a HUGE deal… I’m noticing a pattern here.
I’ve read through the blog post “The Economics of Safecoin” but have not read all the posts on this forum so maybe this has already been talked about. I’m really excited to help make this work and wondering what others are thinking about app data…
My snap answer is:
- that the app need not worry about storage taken up in the user’s space
- that an app won’t have its own space independent of its users, else its more like a publication (e.g. website)
I suppose a good case is a data browser app (e.g. Web browser). There is a clear separation between the app, and the data it browses. If the data is public, it is stored for free (current SAFE plan is to not charge for storing public data), if data is private - e.g. available only to selected users of an app - the publisher/creator has to pay (current SAFE plan, is you pay with equal amount of storage or using Safecoin).
I think that works, and doesn’t create any barriers for the app developer, but possibly for publishers if they are creating a lot of private data (e.g. a paywall).
I’m not a builder, so not the best person to answer this question. But I will try anyway.
Depending on the type of App, scalability requires the consumer to pay the cost of their personal data.
Let’s look at facebook mini games for example. The only unique data on those applications is the user’s stats. Everything else, like graphics, program functions/scripts, even the application itself has already been uploaded and paid for by the builder. So while the user is accessing the builder’s application, the only cost to them is their own personal data on that game. This should be a very very very small amount. Even with large MMORPG games, the effect would be the similar.
I would also classify the (personal stats data) as a private share between the App and the User. This should prevent cheating. Stat changes originate from the Game App and the User accepts the replacement stats file and stores it, using their storage amount.
Regarding Apps that use a large amount of unique data like a 3D graphics design programs. The program itself will not be an issue, but the large amount of unique graphic imaging will have to be paid for by the consumers. This could be done whenever they go to “save” their work.
If any builders want to chime in and add their point of view, please do so.