> Thanks Kee, but I am a bit puzzled by the restriction.
> That would require complicity from the businesses, which if reputable would 
> be a stretch, no? For example, if I had an app that linked to course 
> selections on University websites, are they going to suggest that these could 
> be portals to pedophile shopping sites by entering a secret pass phrase? By 
> the sounds of it, please correct me if I am wrong, no iStore app can link to 
> a website for content regardless of the status of the organization that 
> stands behind the site? Hmmmm, I still have a lot to learn in this space. 
> Are there any links available to guidelines that describe these limitations?

The guidelines don’t matter much because you’re at the mercy of whatever tester 
get’s your build to approve: it seems to be very subjective by reviewer. What I 
have found is that you can have some website stuff, but you need some mobile 
app specific features as well (push notifications, location services, etc.). It 
has also been my experience that “leading” with the web content isn’t as 
successful as opening with some static content. YMMV

Last week I got a brand new app approved (for TestFlight, not fully released 
yet but is the same approval process) for a University that contains a web 
viewer. This is only 1 of half a dozen cards in the app, and goes directly to a 
mobile landing page for a particular department. You are free to click around 
and visit the site, but you can’t manually enter a URL into a field and visit 
that site you are “stuck” with whatever links we provide. Since this isn’t the 
main focus, and is fairly contained, I had no worries about this being an issue 
(and it wasn’t). If you message me off-list with your AppleID, I’d be happy to 
add to TestFlight so you can see what I’m talking about.

But I have had apps with services that were “coming soon” so to start there was 
some bare bones content and a few browser widgets going to specific pages on a 
business website: this got rejected due to Apple’s 4.2 Minimum Functionality 
clause. After rushing to add a feature or two, and make sure those cards were 
the first to appear rather than the browser widget, got the barebones project 
approved. (A year later, the client still hasn’t paid to finish the project so 
it’s still sitting in the App Store at v0.4.03)

—Andrew Bell
use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription 

Reply via email to