Return to Answer

edited body

Source Link

edited May 26, 2017 at 3:42

Sounds like you are technically not "linking" the pages (to open in Chrome, Firefox, etc.). Google suspects you of "bundling" someone else's content:

We don’t allow apps whose primary purpose is to drive affiliate traffic to a website or provide a webview of a website without permission without permission from the website owner or administrator.

The overall [Stack Exchange *Terms of Service* states][2]:

Other than as expressly set forth in this Agreement, Subscriber may not copy, modify, publish, transmit, upload, participate in the transfer or sale of, reproduce (except as provided in this Agreement), create derivative works based on, distribute, perform, display, or in any way exploit, any of the Content, software, materials, or Services in whole or in part.

The Terms of Service makes allowances for the API, but does not mention WebViews or iframes^‡.

But iFrames have never been allowed for Stack Exchange content and WebViews are considered worse, by content owners -- hence why both Google and Apple closely scrutinize apps that use them.

You can contact Stack Exchange and attempt to get clarification. (Please comment below, if they respond.)

But, until then, just display the key info, from API calls, in your app, and per the API terms of service. Then, in the display, you might include a hyperlink that opens in a standard browser.

^{‡ (It also doesn't permit browsers; so Google is in big, big trouble? (^_^) )}

Sounds like you are technically not "linking" the pages (to open in Chrome, Firefox, etc.). Google suspects you of "bundling" someone else's content:

We don’t allow apps whose primary purpose is to drive affiliate traffic to a website or provide a webview of a website without permission from the website owner or administrator.

The overall [Stack Exchange *Terms of Service* states][2]:

Other than as expressly set forth in this Agreement, Subscriber may not copy, modify, publish, transmit, upload, participate in the transfer or sale of, reproduce (except as provided in this Agreement), create derivative works based on, distribute, perform, display, or in any way exploit, any of the Content, software, materials, or Services in whole or in part.

The Terms of Service makes allowances for the API, but does not mention WebViews or iframes^‡.

But iFrames have never been allowed for Stack Exchange content and WebViews are considered worse, by content owners -- hence why both Google and Apple closely scrutinize apps that use them.

You can contact Stack Exchange and attempt to get clarification. (Please comment below, if they respond.)

But, until then, just display the key info, from API calls in your app, and per the API terms of service. Then, in the display, you might include a hyperlink that opens in a standard browser.

^{‡ (It also doesn't permit browsers; so Google is in big, big trouble? (^_^) )}

Sounds like you are technically not "linking" the pages (to open in Chrome, Firefox, etc.). Google suspects you of "bundling" someone else's content:

We don’t allow apps whose primary purpose is to drive affiliate traffic to a website or provide a webview of a website without permission from the website owner or administrator.

The overall [Stack Exchange *Terms of Service* states][2]:

Other than as expressly set forth in this Agreement, Subscriber may not copy, modify, publish, transmit, upload, participate in the transfer or sale of, reproduce (except as provided in this Agreement), create derivative works based on, distribute, perform, display, or in any way exploit, any of the Content, software, materials, or Services in whole or in part.

The Terms of Service makes allowances for the API, but does not mention WebViews or iframes^‡.

But iFrames have never been allowed for Stack Exchange content and WebViews are considered worse, by content owners -- hence why both Google and Apple closely scrutinize apps that use them.

You can contact Stack Exchange and attempt to get clarification. (Please comment below, if they respond.)

But, until then, just display the key info, from API calls, in your app and per the API terms of service. Then, in the display, you might include a hyperlink that opens in a standard browser.

^{‡ (It also doesn't permit browsers; so Google is in big, big trouble? (^_^) )}

Source Link

created May 26, 2017 at 3:31

Brock Adams

Sounds like you are technically not "linking" the pages (to open in Chrome, Firefox, etc.). Google suspects you of "bundling" someone else's content:

We don’t allow apps whose primary purpose is to drive affiliate traffic to a website or provide a webview of a website without permission from the website owner or administrator.

The overall [Stack Exchange *Terms of Service* states][2]:

Other than as expressly set forth in this Agreement, Subscriber may not copy, modify, publish, transmit, upload, participate in the transfer or sale of, reproduce (except as provided in this Agreement), create derivative works based on, distribute, perform, display, or in any way exploit, any of the Content, software, materials, or Services in whole or in part.

The Terms of Service makes allowances for the API, but does not mention WebViews or iframes^‡.

But iFrames have never been allowed for Stack Exchange content and WebViews are considered worse, by content owners -- hence why both Google and Apple closely scrutinize apps that use them.

You can contact Stack Exchange and attempt to get clarification. (Please comment below, if they respond.)

But, until then, just display the key info, from API calls in your app, and per the API terms of service. Then, in the display, you might include a hyperlink that opens in a standard browser.

^{‡ (It also doesn't permit browsers; so Google is in big, big trouble? (^_^) )}