Am I the only one who HATES when apps open links inside a webview and you have to tap yet another button to open the link in Safari? Most apps do that and they annoy the hell out of me.
My App Is Dead in the Water
61–70 of 206 posts
Re: My App Is Dead in the Water
#62I wouln't like if someone scraped my web site, and put it in a iPhone app. Why not just open the links in a web browser !?
...that's what the app is doing. It was just opening the links in a webview inside the app instead of tossing the user over into Safari every time they click a link. There was no scraping happening.
Re: My App Is Dead in the Water
#63Why not launch Safari when the user clicks on an article? And make it clear that you have permission from HN to use their API? Having used your app for exactly one minute, that seems like it would address their concerns and preserve usability.
Given the "back" link from Safari to your app since iOS 11? (10?) - this is the right solution IMHO.
The worst offender is the Gmail app since half the links I click on there interact with cookies in the Safari app (account activation, notifications, etc). And Gmail will even keep nagging me to install Chrome which I will never do. Ugh, I really need to switch away from Gmail.
Re: My App Is Dead in the Water
#64Re: My App Is Dead in the Water
#65This might be a good time to reconsider what made iOS the best platform for this application in the first place. For example, can the app be re-packaged as an HTML5 app instead? What's the compelling advantage for building on iOS for this application?
That would be the same from a legal standpoint. You app would just get shittier UX, nothing else.
Re: My App Is Dead in the Water
#66I see the comments are already filling up with the usual cries of how this is what you get when you play in a curated market, but something about this doesn't make sense. Apple provides several views specifically designed to show web content: UIWebView, WKWebView, and SFSafariViewController. This ruling of theirs would apply to all uses of these views that aren't for specific domains and URLs known in advance, which…
Re: My App Is Dead in the Water
#67Re: My App Is Dead in the Water
#68Re: My App Is Dead in the Water
#69Earlier quoted context omitted.
Given the "back" link from Safari to your app since iOS 11? (10?) - this is the right solution IMHO.
Especially with the swipe gestures on the new phones since the X, my pet peeve are apps that use web views inside their app inside of just opening Safari. The worst offender is the Gmail app since half the links I click on there interact with cookies in the Safari app (account activation, notifications, etc). And Gmail will even keep nagging me to install Chrome which I will never do. Ugh, I really need to switch awa…
I don’t want my twitter and RSS reader app exploding my safari tab count. I look at articles all the time in those apps and decide not to open them in safari.
Re: My App Is Dead in the Water
#70This might be a good time to reconsider what made iOS the best platform for this application in the first place. For example, can the app be re-packaged as an HTML5 app instead? What's the compelling advantage for building on iOS for this application?