{"id":30138,"date":"2020-09-14T16:18:01","date_gmt":"2020-09-14T20:18:01","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=30138"},"modified":"2023-11-22T12:02:22","modified_gmt":"2023-11-22T17:02:22","slug":"big-fish-casino","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/09\/14\/big-fish-casino\/","title":{"rendered":"Big Fish Casino"},"content":{"rendered":"

Cyrus Farivar<\/a> (tweet<\/a>):<\/p>\n

The app offers a variety of typical casino games to play, including their favorite, called Reel Rivals, a game in which players accrue points by playing a virtual slot machine. As in a real casino, players exchange money for coins to bet.<\/p>\n

Unlike in a real casino, there is no way to win money back or earn a payout on coins.<\/p>\n

But that has not stopped Shellz and her husband from spending about $150,000 in the game in just two years.<\/p>\n

[…]<\/p>\n

According to data provided by Apptopia, an app analytics company, Big Fish Games took in an estimated $139.3 million from Big Fish Casino and Jackpot Magic players from February 2019 through July 2020.<\/p>\n<\/blockquote>\n

I’m not saying that games like this should be banned from the App Store, as I think users should be able to install what they want on their devices. It doesn’t seem like they are being deceptive.<\/p>\n

But something seems out of whack when you look at the totality of apps that are allowed vs. rejected. Casino game apps where it’s impossible to win are OK, and Apple gets 30%. But users must be protected from streaming games and direct payment.<\/p>\n

And regular apps get rejected for the oddest reasons. Paul Haddad<\/a>:<\/p>\n

\n

Pastebot needs to generate a ⌘v keystroke in order to paste. When generating this keystroke on >= 10.14 an Accessibility permissions alert is shown by the OS.<\/p>\n

Apple rejected our app because of this.<\/p>\n

In order to get around the App Store we had to offer (and users had to install) a separate Paste service that shipped outside the App Store. The service would do nothing other than generate the ⌘v and would show the same alert on first use.<\/p>\n<\/blockquote>\n

Is that really better for the user? Who knows what rule this violated or why it was eventually approved two years later.<\/p>\n\n

And for not adhering to vague and changing guidelines that Apple itself doesn’t follow. Joe Cieplinski<\/a>:<\/p>\n

\n

Got rejected today for the button on this screen.<\/p>\n

So I’ll be sending them a screenshot of this button in response.<\/p>\n

Won’t make a difference. But I just can’t help being sassy every now and then.<\/p>\n<\/blockquote>\n\n

Cabel Sasser<\/a>:<\/p>\n

\n

Oh hey us too 🥴<\/p>\n<\/blockquote>\n\n

Timothy Buck<\/a>:<\/p>\n

\n

This stuff is really killing the Apple brand for me. If they believe these rules are helping keep consumers safe, why are they skirting their own rules instead of leading the way in transparency?<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n