←back to thread

830 points todsacerdoti | 2 comments | | HN request time: 0.401s | source
Show context
gtsteve ◴[] No.25135526[source]
Looks nice but it doesn't solve my fundamental problem:

1. I invest loads of time and effort developing an app

2. Apple rejects it

-or-

2. Apple approves it

3. I ship a new update

4. Apple rejects the update and now decides my app should have been rejected retroactively.

I'm especially concerned about what happened to Hey and others but my customers are demanding smartphone apps and there are still limits to what can be done with a mobile web browser.

replies(11): >>25135538 #>>25135628 #>>25135644 #>>25135672 #>>25135968 #>>25135975 #>>25136030 #>>25136106 #>>25136507 #>>25137973 #>>25139367 #
user-the-name ◴[] No.25135538[source]
This really isn't a problem in practice, unless you are going out of your way to try to bend the rules set in place, especially about sales.
replies(6): >>25135567 #>>25135586 #>>25135624 #>>25135693 #>>25135898 #>>25141783 #
adanto6840 ◴[] No.25135898[source]
I recently was in contact with someone who has written a menu-bar app to monitor Tesla Powerwall status. It's in the Mac App Store already -- but NOT the latest version, because Apple suddenly decided that they wanted written proof that accessing the Powerwall APIs was allowed (from whom?! It's MY hardware!). Apple will not allow the dev to update his Mac App in the MAS; yet they approved & continue to leave the original older version [with known bugs] up, available for purchase.

So now the developer is stuck -- he can't update his app on the Mac App Store, and what recourse does he have as a 1-man-shop vs Apple?! =|

As a developer I find it absurd, as a consumer [who bought the app on MAS and wondered why I had the non-latest version], I find it absolutely baffling & anti-consumer.

replies(1): >>25136003 #
1. sunshinerag ◴[] No.25136003[source]
he cannot withdraw the older version of the software from the app store? that is weird.
replies(1): >>25136696 #
2. ◴[] No.25136696[source]