This guy has shown quite a talent for self-sabotage. Apple was willing to reinstate him if he'd undo some of the PR damage he'd created by spelling out that he shared the credit card with someone, and that maybe that's not the best idea. Instead, he was enjoying the spotlight so much, he used the opportunity to escalate further, even publishing his phone call with Apple (illegal on one side of that conversation at le…
I don't know what the app is about, I have never even used an Apple product in all my live. But I admire this guy for not bowing to the demands of Apple. Sticking to your principles, even when that means you're losing money (or, as you put it, "self-sabotage") is not something you see very often nowadays.
Dear Dash Users – A message to all Dash users from the Kapeli Blog
21–30 of 110 posts
Re: Dear Dash Users – A message to all Dash users from the Kapeli Blog
#22After listening to the recording of the conversation, my feeling is that Apple is handling this in a very fair and professional way, and that I was too quick to take sides. I think it is not unreasonable to assume that: same credit card + same hardware = same developer.
Re: Dear Dash Users – A message to all Dash users from the Kapeli Blog
#23This guy has shown quite a talent for self-sabotage. Apple was willing to reinstate him if he'd undo some of the PR damage he'd created by spelling out that he shared the credit card with someone, and that maybe that's not the best idea. Instead, he was enjoying the spotlight so much, he used the opportunity to escalate further, even publishing his phone call with Apple (illegal on one side of that conversation at le…
From my perspective, most of the PR damage is because a lot of other smaller developers have come out of the woodwork to voice their grievances with Apple. These kind of things happen all the time, and a lot of us feel stood on by the giant Apple. Even though this event sounds like a special case, it still highlights the draconian behavior we deal with. (That's what I would call Apple trying to get him to post a blog…
Re: Dear Dash Users – A message to all Dash users from the Kapeli Blog
#24I've only just run across this. It looks like the story here is: 1. Guy publishes paid app to iTunes 2. App is really good, gets a ton of good reviews 3. Apple decides those reviews must be fraudulent, and pulls his app from the store and tells the guy he has to publicly admit that he committed review fraud to get his app reinstated. 4. People who have bought the app can't download it, guy can't do anything to make h…
What actually happened: 1. Guy publishes good paid app and gets a tonne of good reviews 2. He helps out a relative by buying an apple developer account for them, giving them a machine to test with 3. Relative also uses same "com.kapeli.*" bundle ID 4. Relative decides to buy 1000 fraudulent reviews 5. Apple tells the relative to stop posting fraud reviews, who refuses 6. Apple terminates both developers accounts sinc…
Just saying: anyone can freely create any App ID they want. I just successfully created "com.google.android.nougat" as a test.
Re: Dear Dash Users – A message to all Dash users from the Kapeli Blog
#25Re: Dear Dash Users – A message to all Dash users from the Kapeli Blog
#26Earlier quoted context omitted.
Why is the developer being so dense? Just being difficult for no reason because he has a stick up his ass. "You're sure you want that statement to become public" it literally makes no sense... All he's done is posting that Apple call has burnt every bridge he had with them, and made Apple look great. Literally they sound very professional on that call and very willing to help him, and instead he is just being unneces…
Actually I wouldn't be so sure as to who burnt the bridge first. He posted the recording after Apple went public with their side of the story. What happened to the supposed blog post? Why did Apple go to the press without getting back to him on the draft?
That said, I was amazed how that guy from Apple was being so patient with this guy being so immature. The Apple guy was trying his best to sort this out, but for every word he said, this Dash guy would keep complaining. This phone call could have ended in 30 seconds but took over 7 minutes because all this guy did was complain (which I think he did for the purpose of making this recording), and I don't even know what you would get from complaining that way when the other person was trying to help you. I would have been pissed if I was that Apple guy.
Re: Dear Dash Users – A message to all Dash users from the Kapeli Blog
#27This guy has shown quite a talent for self-sabotage. Apple was willing to reinstate him if he'd undo some of the PR damage he'd created by spelling out that he shared the credit card with someone, and that maybe that's not the best idea. Instead, he was enjoying the spotlight so much, he used the opportunity to escalate further, even publishing his phone call with Apple (illegal on one side of that conversation at le…
From my perspective, most of the PR damage is because a lot of other smaller developers have come out of the woodwork to voice their grievances with Apple. These kind of things happen all the time, and a lot of us feel stood on by the giant Apple. Even though this event sounds like a special case, it still highlights the draconian behavior we deal with. (That's what I would call Apple trying to get him to post a blog…
Re: Dear Dash Users – A message to all Dash users from the Kapeli Blog
#28 My preferred solution would be for a fellow developer to get it
back on the App Store, as a free app.
Especially because: Open sourcing doesn’t look like a good solution at this time,
as most of my users are not iOS developers and are not familiar
with compiling an app for their devices.
I may be missing something but the author cannot open source the app, but expects a fellow developer to get it on the App Store as a free app. Can the fellow developer pick up the existing app (binary?) and upload it on the app store?Re: Dear Dash Users – A message to all Dash users from the Kapeli Blog
#29Earlier quoted context omitted.
Yes. Well the snippet of the call that was released on his blog anyway.
There is not blackmailing from Apple. They are offering him a chance to wipe his slate clean if he publicly (since he was the one to go public) acknowledges that what Apple did was justified (and it was). He has to now decide what's more important: his pride or his revenue ( https://web.archive.org/web/20150103225308/http://blog.kapel... ), it's that simple.
I'm not saying Apple did blackmail him, just stating what others on this site have said do me. Personally listening to the call I would of made the blog post, not because I thought Apple were blackmailing me but because I can see Apple's Point of View in this matter and that it had stirred things up.
But it had been pointed out to me that the blog post being a condition of having the account reinstated (and Apple ideally wanting to look over a draft of that post first) could be taken as Apple blackmailing him and its hard to argue against that point. And that's why I bring up the question in my post "Should a public statement explaining the incident be a requirement of reinclusion to the App Store?" (Whoops it appears I missed off the ? in that post, but it was meant as a question).
I'm going to give the Dev the benefit of the doubt for a moment when they said they got very little information out of Apple was to why it was closed. [1]
> A few hours ago I received a “Notice of Termination” email, saying that my account was terminated due to fraudulent conduct. I called them again and they said they can’t provide more information.
The first initial publication of the issue was that he had very little information to go off, he had been accused of fraudulent conduct, he believed that he had not done any thing fraudulent and Apple said the matter was closed.
If he believed he was in the right after that you have very few options open to you and as been shown in the past (and in my experience with Google) going public can be one of the ways to get a 2nd set of eyes on the issue. At the very least he would have to explain to his users why they can no longer update/download his app from the place they had purchased it from.
In this case getting that 2nd set of eyes on the issue as did get the ball moving again so I'm not going to hold anything against any one who has to use the tactic of going public (Though imo it has to be done carefully as it can be the nuclear option but if the other side has already used theirs you are often left with little other option. But it has to be done carefully because we have seen it used when the dev has been at fault).
I can see why Apple would like a statement clearing up what had happened but the "blackmailing" argument is should it be a requirement?
Again personally if I was in his shoes I would of made the post anyway, I wouldn't of seen it as a "condition" because I can see why Apple deemed the 2 accounts as linked and I would like to explain to my users what the mix up was, because after going public they are bound to ask anyway.
[1] https://blog.kapeli.com/apple-removed-dash-from-the-app-stor...
EDIT: When I say "they are bound to ask anyway." I was referring to my users, not Apple.
Re: Dear Dash Users – A message to all Dash users from the Kapeli Blog
#30This guy has shown quite a talent for self-sabotage. Apple was willing to reinstate him if he'd undo some of the PR damage he'd created by spelling out that he shared the credit card with someone, and that maybe that's not the best idea. Instead, he was enjoying the spotlight so much, he used the opportunity to escalate further, even publishing his phone call with Apple (illegal on one side of that conversation at le…
This is actually not correct, it depends on the state/country he is in.