Guidelines 3.1.3 for cloud storage

Question

terajnol OP

Created Jul ’17

Replies 2

Boosts 0

Participants 2

Hi everyone,

I have an app, free on the Store, with many content.

I now want to add contents for some of the users who also are professional customers. From an external website platform, they bought an access to a securized server.

The new content on the app for theses customers would be a way to send data (text, picture...) created through the free content of the app to this server. Some of the data will be received back from the server after processing, the other will be accessible to someone else (the server will handle the authorizations, and the recipient will access this data through a diffrent web platform).

Here is a simple example : the free content of the app runs as a text editor. If the user is one of my customer, he can send one of the text to someone else through a securized server. The user can also send the text to the same server for writing analysis and get back a modified version.

What I make my customers to pay for is the ability to use a securized server for sharing and processing, and the app content is only the way to acess it.

Do I follow 3.1.3 guidelines by considering this new content as a "Reader app" ? In this guideline, Apple writes that we can allow a user to access previously purchased "cloud storage", but maybe this is not related to what I want ? Or maybe I consider guideline 3.1.4 and can say that the server access is a specific hardware my content is depending on ? I saw recent posts on this forum but I am not sure if I can consider my server as a "specific hardware"...

In the case of a "Reader app", is it possible to have this content locked by login, even if I do not respect guideline 3.1.4 ?

Thank you for your help,

Boost

Answer 1

PBK OP

Jul ’17

Your server is not 'specific hardware', IMHO.

Your app might be operating as a 'reader app' if all your app is doing with the new content is 'accessing' it - not processing it as a text file.

You can certainly limit access to the new content that your 'reader app' is trying to access.

0

Answer 2

terajnol OP

Jul ’17

Thank you for your anwser PBK.

I understand that my app can operate as a "Reader" if it only "access" to the new content.

In the case of cloud storage, does this concern only the reading of content form the cloud or also the writting (sending) of content to the cloud ? My ideas are not clear about that...

If I come back to my example, the first option for the user is to send a fileto the server, there is no reading of a new content.

With the second option, however, the user can send the file to the same server and get back a new content after processing. In the case of a text file, my app will only managethis new content as the other files but won't be able to edit it. For the second option, I think I am fine with the "Reader" app guideline.

Thanks

0