So not even SFSafariViewController is protection from committing copyright infringement, apparently.
I also got the same workaround from ASR: make the links exit the app to Safari. But now I'm curious what the point of SFSVC is beyond reading... a privacy policy for your own app? Web pages belonging to your own app? But then why not use a WKWebView?
Please read vikasnair's answer [0] below. I think that is the best answer to get your app approved right now.
I'm happy to be enlightened on why this practice makes sense, but so far I've come up with nothing.
I suspect if the app is changed to operate more like Reddit (view the article title/source and view comments, if any, prior to opening the article) it would be approved by Apple. Alternatively, as suggested by Apple, the app could initially present only an excerpt of the article and fall within the exception but, as pointed out in the medium post, that probably isn't particularly valuable to HN users.
You also could have tried reading the link I included with my original comment.
None of these is addressed by your original comment or the link, which all presuppose that the fair use doctrine is the only way to escape copyright problems associated with loading a webview with someone else's content.
A third-party application doesn't have the same permissions/protections. Copyright law doesn't always require the author's permission though. If you don't have permission you can still display the content if you have a legal justification. The Fair Use Doctrine is the set of factors to determine whether or not publication without permission is justified.
The transformative nature of the publication is only one factor, although it's the most important. Another factor working in OP's favor is that the use is non-commercial. He says in his blog post that he maintains the site on his own in his spare time, doesn't charge users to download the app, and from what I can tell, doesn't have any ads.
I really think OP could make some small changes and get it approved by the app store.
Typically in this nomenclature the first and second parties are the user and OS (or computer) vendor. The third party is an application developer. So typically Google and Mozilla would be third parties the same as maker of the HN browser.
Aside from that, I see no real distinction here. When I launch Firefox, it shows me on my "blank" home page (provided by the browser, not a web page) a list of popular articles curated by its Pocket division. This is essentially identical to what OP's app does. One is a browser that proffers links, the other is a browser that proffers links.
I have seen of lot of funny or meme apps which rip content off same popular websites. I think it unfair to operator of such sites. A lot of these app will show their ads, but won't pull in ads of publisher.
I think this is a bad argument. Showing web content is how the web works.
Not providing attribution in the form of the address bar (title + url) might be the main problem here but I personally feel fixing sharing would help as well.
- Twitter: uses SFSafariViewController
- Reddit: uses custom in-app web view, shows page title and url on top, provides "open in Safari" option through share button
- Instagram: uses custom in-app web view, shows page title and url on top, provides the built in share-sheet, interestingly disabling open in Safari, but enabling "Add to Reading list"
Your current app on the App Store embeds third party content in an in-app web view, without showing the title or original URL on top and without being able to open the link in Safari.
I suggest you to either use SFSafariViewController for the third party content or mimic something similar with a proper title bar and and share button with Open in Safari option.