Live data from Hacker News

Apple takes down another indie dev

blog.rollins.io

21–30 of 84 posts

Re: Apple takes down another indie dev

#21
post #3

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.

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…

There are plenty of other choices, though.

Re: Apple takes down another indie dev

#23
post #15

Eventually an alternative app market free from apple or Google oversight and copyright infringement nonsense will come out. It's about time someone made a significant effort to establish it. Such a market will be profitable too.

[deleted]

Re: Apple takes down another indie dev

#24
I think one day will come, OS manufacturers will be the only one actually releasing applications for their systems.

Computers will just turn into consoles.

To be honest, apple just makes computers that work like consoles.

Re: Apple takes down another indie dev

#25
post #3

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…

As a developer, you've got to be able to assess risk in a more nuanced way than this is/isn't violating the guidelines. It is startlingly obvious that Apple's Guidelines are full of gray areas. Just read the introductory bullet points:

https://developer.apple.com/app-store/review/guidelines/

"We'll know it when we see it."

If that isn't a clear indication that Apple takes broad latitude in the judgement of what is acceptable, I don't know what is.

It's obvious to me that the launcher widget fell in a gray area. Any app that launches other apps overlaps with the functionality of the home screen.

Re: Apple takes down another indie dev

#26
post #3

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?

Re: Apple takes down another indie dev

#27

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…

> 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 singularly focused; stringently enforcing their policies (even if they are often unclear or inconsistent).

You missed the last step - one iOS version later, Apple copies the killer feature it originally rejected as a misuse of the platform, and makes it its own.

Re: Apple takes down another indie dev

#28
post #20

This seems like a pretty clear case of "not obeying the spirit of the rule": "On September 26, Greg submitted what he believed was a valid compromise: The click would take the user to the main Launcher app, and from there the app would call the appropriate action." It's quite clear that while the code would no longer be launching another app from the widget, the user would experience essentially the same action. That…

Does it really matter what his compromise is? His app is a Today widget app launcher. Apple decided after initially approving it that you can't make Today widget app launchers. The end.

I agree that the dev thinking it is a "valid compromise" is iffy, but I don't think there was any compromise that would allow his app to stay on the store.

Re: Apple takes down another indie dev

#29
While I disprove strongly with Apple's policies, that article is hugely apologist. They act like it is a peppy lone developer underdog stepped on for no reason and it is an utter surprise!

Sorry but Apple's app store policies are pretty clear in this area. They have also squished tons of similar apps previously (which was well publicized).

Plus according to the article Apple contacted the developer essentially saying "Do X and Y or we'll pull you!" and the developer didn't do X and Y so consequently got pulled. They say the developer "compromised" but the way it is worded I have to assume it was a one-sided "compromise" (as in, he never got Apple's approval before submitting an update that clearly didn't fix the issues raised).

I honestly would have had more sympathy if the article wasn't so manipulative. Now it has just got my back up and I'm more on Apple's side than the developers.

PS - Apple's policies are dumb. I dislike them. I'm all for protecting user privacy and security, but many Apple policies are essentially "don't compete with us!" which is dumb when app installation is entirely voluntary.

Re: Apple takes down another indie dev

#30
post #3

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.

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.

Post reply on HN