Apple now rejecting apps with Pebble Smartwatch support • Hacker News Board

Re: Apple now rejecting apps with Pebble Smartwatch support

#111

Post by Dylan16807 » Thu, Apr 23, 2015, 2:50 PM UTC

AlexandrB wrote: post #97

captainmuon wrote: post #79

Earlier quoted context omitted.

They have a monopoly for the iOS platform, at least. And in some jurisdictions you don't need a monopoly to be guilty of anticompetitive behavior.

Do you have the same stance on Twitter? Twitter has a monopoly on the Twitter platform and may choose not to provide API keys for apps that it doesn't want to exist. Is this abusing a monopoly? If not, why not?

Twitter has definitely performed anticompetitively in the past like that. Legal or not, it's abusing their position.

Re: Apple now rejecting apps with Pebble Smartwatch support

#112

Post by loumf » Thu, Apr 23, 2015, 2:51 PM UTC

mey wrote: post #96

d0m wrote: post #76

It's a bit tricky. I agree with most comments here that Apple is in the right to control what appear in the description and metadata. Not just from a competitive standpoint but in a way to make the it better for the user experience. That being said, in the Pebble case, I think it makes the user experience worst for the user. I.e. if I have a pebble watch and am looking for an iphone app that play well with it, I'd wa…

Under US law, it would be anti-competitive to use market control to stifle competition. I agree on your point about android, but you should be able to see what the software supports. Of course a court would need to decide, IANAL etc

Apple doesn't have control of the smart phone (or phone) market. Having control of the iPhone market is not considered monopolistic.

Re: Apple now rejecting apps with Pebble Smartwatch support

#113

Post by sesteel » Thu, Apr 23, 2015, 2:51 PM UTC

7Z7 wrote: post #31

sesteel wrote: post #4

I am no lawyer, but this sounds like an antitrust lawsuit waiting to happen. Apple, IMO, should not be allowed to monopolize their platform in this way.

In what way? They aren't rejecting the app, they're rejecting the use of the trademark "Pebble" in the app's description.

They are suppressing information which could help a customer make a decision. Users can no longer search for or discover apps that support their watch via the AppStore. I view this behavior as anti-competitive and does not serve the greater public good. Apple is a corporation.

Re: Apple now rejecting apps with Pebble Smartwatch support

#114

Post by marincounty » Thu, Apr 23, 2015, 2:51 PM UTC

d0m wrote: post #76

It's a bit tricky. I agree with most comments here that Apple is in the right to control what appear in the description and metadata. Not just from a competitive standpoint but in a way to make the it better for the user experience. That being said, in the Pebble case, I think it makes the user experience worst for the user. I.e. if I have a pebble watch and am looking for an iphone app that play well with it, I'd wa…

"I got tired of that 2 years ago and switched to android, haven't looked back since."

And you just made my decision easier.

Re: Apple now rejecting apps with Pebble Smartwatch support

#115

Post by the_mitsuhiko » Thu, Apr 23, 2015, 2:52 PM UTC

Someone1234 wrote: post #15

This forum appears to have an invalid certificate: Domain: forums.getpebble.com CN = *.vanillaforums.com If you use HTTPS Everywhere, you'll want to uncheck this specific site, remove the HTTPS part of the URL and reload. PS - I love HTTPS Everywhere but it always surprises me just how many sites have broken HTTPS implementations.

Many websites do not support HTTPS but have no chance to disable the default listener that is in place because it comes from somewhere else.

Re: Apple now rejecting apps with Pebble Smartwatch support

#116

Post by k-mcgrady » Thu, Apr 23, 2015, 2:52 PM UTC

Touche wrote: post #54

k-mcgrady wrote: post #32

Total BS title. They are rejecting apps that mention other products in the metadata. If you submit an app that says 'also available on Android' the same thing will happen and it has been enforced for years. The rejection was very clear.

It's worse discussing though because mentioning Pebble has not been enforced for years, it only started to be enforced when Apple created a competitive product.

Sure it can be discussed but the rule is quite clear and my problem is with the title of the article which is completely untrue.

Re: Apple now rejecting apps with Pebble Smartwatch support

#117

Post by Alupis » Thu, Apr 23, 2015, 2:52 PM UTC

AlexandrB wrote: post #97

captainmuon wrote: post #79

Earlier quoted context omitted.

They have a monopoly for the iOS platform, at least. And in some jurisdictions you don't need a monopoly to be guilty of anticompetitive behavior.

Do you have the same stance on Twitter? Twitter has a monopoly on the Twitter platform and may choose not to provide API keys for apps that it doesn't want to exist. Is this abusing a monopoly? If not, why not?

If Twitter was killing an App or Device made by a 3rd party simply because Twitter was entering that market and wished to monopolize the user-share, then yes I'd consider that anti-competitive.

(yes, Twitter does just that, and yes, it's anti-competitive in my book).

Simply not being able to mention "Android" or "Android Wear" or now "Pebble Watch" is ridiculous. If I chose to buy an Android Wear or Pebble Watch, it's because I felt it was a better match for me... I still would have bought an iPhone (since I'm looking for iPhone Apps).

Re: Apple now rejecting apps with Pebble Smartwatch support

#118

Post by BinaryIdiot » Thu, Apr 23, 2015, 2:53 PM UTC

minikites wrote: post #19

It's just a metadata problem, the author of this sensationalist piece even quotes it as such, maybe they're unclear what "metadata" means. > Please remove any instances of this information from your app and its marketing materials, including the Application Description, What's New info, Previews and screenshots. > Since your iTunes Connect Application State is Rejected, a new binary will be required. Make the desired…

> It's just a metadata problem, the author of this sensationalist piece even quotes it as such, maybe they're unclear what "metadata" means.

I think the issue here is that Apple is reclassifying smart watches as mobile platforms and thusly don't want you including it in your description. If I support a smart watch why the hell can't I MENTION that I support it? That's just unreasonable.

Re: Apple now rejecting apps with Pebble Smartwatch support

#119

Post by blumkvist » Thu, Apr 23, 2015, 2:54 PM UTC

zak_mc_kracken wrote: post #52

A good reminder of what it would be like if we lived in a world where there is no Android and iOS is a monopoly. Apple's anti competitive behavior puts Microsoft of the 90s to shame.

Nowhere near...

Re: Apple now rejecting apps with Pebble Smartwatch support

#120

Post by JohnTHaller » Thu, Apr 23, 2015, 2:54 PM UTC

Someone1234 wrote: post #15

This forum appears to have an invalid certificate: Domain: forums.getpebble.com CN = *.vanillaforums.com If you use HTTPS Everywhere, you'll want to uncheck this specific site, remove the HTTPS part of the URL and reload. PS - I love HTTPS Everywhere but it always surprises me just how many sites have broken HTTPS implementations.

This is the whole reason the site itself doesn't direct you to https or advertise it is available. In order to support https, you don't just install a cert, you know. You have to make sure your whole chain supports it. Including things like third party CDN providers, which can be more expensive to enable https than you pay for the CDN. So, if you use an extension that randomly directs you to connect using a method the site operator never told you to use, expect problems.