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?
My App Is Dead in the Water
41–50 of 206 posts
Re: My App Is Dead in the Water
#42Why 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.
Re: My App Is Dead in the Water
#43Re: My App Is Dead in the Water
#44Re: My App Is Dead in the Water
#45Re: My App Is Dead in the Water
#46Re: My App Is Dead in the Water
#47Is the app actually parsing the articles and displaying them the app or just like other HN clients that just have links and you open them in Safari? If it's the first then I guess the complaint makes sense if you are implementing some kind of "Reader" mode in the app itself by scraping the content.
This is exactly what his app is doing, I fail to see what are the differences between the two?
Re: My App Is Dead in the Water
#48The real maddening thing is that there is no appeal process and no (mainstream) way to distribute your app if Apple has a vague problem with it.
I hope for a day we will have mobile devices that are free and usable.
Re: My App Is Dead in the Water
#49I understand the frustration that leads to this question, but it is wholly irrelevant and only loses you a bit of the reviewer's attention span.
Re: My App Is Dead in the Water
#50Why can't you include the agreement for the API as documentation of this? Seems really straight forward. They are trying to protect themselves, not get into a philosophical battle over software and media copyrights.