51–60 of 84 posts
As usual, it's all written in the bible http://www.joelonsoftware.com/items/2009/06/10c.html
Earlier quoted context omitted.
Another missed step - Apple approved the "gray area" app in the first place.
That's the thing I don't like about this. If they approve an app in the first place they should only then remove it under extreme circumstances. This kind of nervous uncertainty among devs is bad for the platform.
Is that really true? This has been going on since day one and yet the platform is thriving.
It's plainly stated in the terms ( https://developer.apple.com/app-store/review/guidelines/ ) Section 10: 10. User interface 10.4 Apps that create alternate desktop/home screen environments or simulate multi-App widget experiences will be rejected So, like it or not, it's what we agree to if we develop apps for iOS.
Ehh I'm not sure I'd consider this either an "alternate desktop/home screen environment" or something that "simulate(s) multi-App experiences". It's a collection of action shortcuts. iOS 8 does something similar when you double tap the home button. It shows recent contacts at the top and tapping one expands into actions such as call or text. I mean I get it. Apple is King and if you stand too close to the line they p…
Earlier quoted context omitted.
It's what we "agree" to. As in, we have no other choice. They could write a clause that said your third child must be named Macintosh and everyone would "agree" to it because there is no other option. That does not mean it's right. Consider this: It's the late 1990's and the Terms of Service for Microsoft Windows contains "10.4 Apps that create alternate web browser environments are not allowed". Microsoft has its pa…
The article essentially chronicles surprise that this app would be rejected. What you describe is you believe the terms are unjust. These are two different things. I may not agree with the speed limit on the freeway, but I am not surprised if I am ticketed for going over it.
Earlier quoted context omitted.
> It's as if history is repeating itself: > Apple rolls out new features/platform. > Developer forges ahead in gray area (there's history here with apps that launch other apps). > Apple "clarifies" their stance by rejecting said developer's app. (In Apple parlance, clarifying means issuing a firm opinion on their openly stated policy of "we'll know it when we see it".) > Development community cries out. > Apple remai…
Another missed step - Apple approved the "gray area" app in the first place.
It's as if history is repeating itself: Apple rolls out new features/platform. Developer forges ahead in gray area (there's history here with apps that launch other apps). Apple "clarifies" their stance by rejecting said developer's app. (In Apple parlance, clarifying means issuing a firm opinion on their openly stated policy of "we'll know it when we see it".) Development community cries out. Apple remains singularl…
You make it sound like being in a grey area is a bad thing. Most things worth pursuing are probably a little grey in some sense, otherwise they're probably just a 'me-too'. That this app was downloaded so much indicates a strong desire for it. Retrospectively coming up with policies will always create ire.
As much as how cool the app may be, it does violate what apple's terms are, which include making effective replacements of their components. This is why "browsers" like Chrome on the iPad still use the webkit components and it just adds password-management and bookmark syncing on top.
2.17 Apps that browse the web must use the iOS WebKit framework and WebKit Javascript
It's plainly stated in the terms ( https://developer.apple.com/app-store/review/guidelines/ ) Section 10: 10. User interface 10.4 Apps that create alternate desktop/home screen environments or simulate multi-App widget experiences will be rejected So, like it or not, it's what we agree to if we develop apps for iOS.
Except it wasn't rejected. It was accepted, sold, and then Apple changed their mind. Did we agree to that fickleness?
It's plainly stated in the terms ( https://developer.apple.com/app-store/review/guidelines/ ) Section 10: 10. User interface 10.4 Apps that create alternate desktop/home screen environments or simulate multi-App widget experiences will be rejected So, like it or not, it's what we agree to if we develop apps for iOS.
Your profile states:
>my AppleTV runs XBMC
Which breaks the terms of your Apple TV software agreement. http://images.apple.com/legal/sla/docs/appletv.pdf
>You may not, and you agree not to or enable others to, copy (except as expressly permitted by this License), decompile, reverse engineer, disassemble, attempt to derive the source code of, decrypt, modify, or create derivative works of the Apple Software or any services provided by the Apple Software or any part thereof (except as and only to the extent any foregoing restriction is prohibited by applicable law or to the extent as may be permitted by licensing terms governing use of open-source components that may be included with the Apple Software).
>BY USING YOUR APPLE TV, YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS LICENSE, UNLESS YOU RETURN THE APPLE TV IN ACCORDANCE WITH APPLE’S RETURN POLICY. IF YOU DO NOT AGREE TO THE TERMS OF THIS LICENSE, DO NOT USE THE APPLE TV.
So, like it or not, it's what you agree to when buying an Apple TV. You should probably return or not use your Apple TV