7 ms·
Piracy Cripples iOS Game in Less than a Week
- gfosco 14y agoWhat if they were all paying customers? You couldn't scale at all, even during the first week, so you shut it all down? There is something fishy here!
- arn 14y agoNot sure if it's "couldn't" or just didn't want to, if they really made little money on the game. But, there seems like there's more to this story. I haven't played the game... but having a popular free-to-download game and making money on consumables is the new App Store model. So seems if it was a very popular pirated game, they could easily make money promoting it to the broad free-to-download audience and make money on in app purchases. I'm guessing the game will come back retuned as a free-to-play game. (looks like it already had IAP, not sure how effective it was).
- jotux 14y agoIf they were all paying customers they could probably afford to move more coders on to the project and help with scaling issues.
- pavel_lishin 14y agoThey mentioned that the increase happened after a pirated .ipa was released; plus I imagine that they could look at their sales numbers, and then look at the number of people logging in, and realize that something was amiss.
- deleted 14y ago[deleted]
- doe88 14y agoActually in this day and age scaling you code (to a moderate level) is maybe not the hardest part, I think the hardest part is to have the ressources to pay for hosting, bandwidth, cpu and ram. Thus if your model was not to provide a free app and have indirect incomes, in this case having non paid users is a major problem. But I think they should have thought about this problem before launching their app and implement anti-piracy measures.
- gfosco 14y agoYou're right.. It's not all that hard to scale, and on top of that a single server really can support a lot of users. I built the back-end for an app in the App Store with well over 100k downloads and tons of active users.. It runs on 2 servers with a load balancer, and is total overkill. I could dispose of the load balancer and just run it all on one server. I have a real problem with them blaming piracy for this, when there are many things they could have done to address the issue, as you mentioned.
- hmbg 14y agoFeels like there has to be a way for them to authenticate the paid-for copies that's cheaper than refunding all of their customers.
- sandfox 14y agoIf only the App Store / iOS has a way to verify receipts that are installed with the app... http://developer.apple.com/library/ios/#documentation/NetworkingInternet/Conceptual/StoreKitGuide/VerifyingStoreReceipts/VerifyingStoreReceipts.html http://developer.apple.com/library/ios/#documentation/Networ...
- josephlord 14y agoIf only that worked for paid apps rather than just in-app purchases.
- suhastech 14y agoThen, they could release it as free and then charge in-app as soon as they launch?
- josephlord 14y agoThey could have done that but they didn't so they seem to need to dig themselves out somehow.
- Spoom 14y agoWould Apple allow a product in the App Store that didn't have any functionality in its default form without a required in-app purchase?
- josephlord 14y agoNo but some limited functionality could be possible I think. Maybe a limited free play period or the ability to watch others play but not take part until they have subscribed.
- k-mcgrady 14y agoIf they refund the customers full price they're actually refunding 30% more than they received due to Apple's sales cut. Disappointing to see this happening but there has to be someway they can authenticate users who have purchased the app. Seems easier than just shutting down and wasting so much money.
- pascal_cuoq 14y ago42% more than they received.
- farhanpatel 14y agoThis is also another reason why developers choose to go the freemium route. With apps that have their own backend its trivial to verify receipts with your server. It's hard(impossible?) to verify actual purchases with your server but In App purchases can easily be verified.
- lucian1900 14y agoAfaik there is no way to verify purchases (since Apple never sends you a receipt for it). It's trivial to verify in-app purchase receipts server-side, however. And that could be used to allow (or not) access to the multiplayer bits.
- duskwuff 14y agoAt this point, anyone who writes an iOS application should expect it to be pirated. Same as desktop applications, same as movies. The response here, though, makes me suspect that the app authors simply weren't doing a very good job of planning for load. If an influx of pirates was enough to make them decide to throw in the towel, how long would they have been able to commit to keeping the servers running after sales plateaued?
- marknutter 14y agoThis strikes me as truly bizarre. They control the servers, yet they allowed anyone who could get their hands on a copy of the game to authenticate and play regardless of whether or not they purchased it? Why on earth wouldn't they track actual payments for the game and check that against requests to the servers? Or better yet, make the game a pay-to-play service like World of Warcraft? Sounds like a huge missed opportunity.
- SoftwareMaven 14y agoGo find the Apple API that let's them know if this device belongs to a person who really bought the app. To my knowledge (not saying that is super-impressive by any stretch!), it doesn't exist. It's the same reason you basically have to "repurchase" IAPs when you get a new device. There is no way for the developer to track that information and get you your rightful bits. This has been going on long enough that I don't think Apple is going to do anything about it, either. I think they'd rather developers take the hit than have their customers get ugly interactions, even if they deserve it for pirating the games.
- josephlord 14y agoThere are different sorts of IAPs. Consumables need to be bought for each device but non-consumables are recoverable to any device logged into the account. If you try to purchase them again they are free and the developer SHOULD implement a 'Restore Purchases' UI to allow you to recover them all without accidentally buying ones you don't already own. With IAP the developer can also retrieve a receipt from the device that can be verified by Apple's servers (process different in the Mac App store). This does not apply to the original purchase of apps from the store, only in-app purchase.
- jrogers65 14y agoYou don't need to use the phone's identity for this. Force the user through a login screen on startup - if they have a paid for account, serve the requests, otherwise sever. It's how Steam does it.
- ynniv 14y ago
- josephlord 14y agohttp://news.ycombinator.com/item?id=4870313 http://news.ycombinator.com/item?id=4870313 Discussion earlier with about 70 comments if anyone wants to read them. This is my comment from that thread: Probably the best solution would be to switch to recurring in-app subscription to the online service. This is I think easier to verify and harder to pirate and should align the revenues with the costs (avoiding getting nice sales up front and not being able to sustain the servers in 18 months time). Some hacks might work if they don't want to go down this route like issuing an update that contacts the server for a unique ID on first run and treating those that don't update quickly as suspicious - request them to email the iTunes receipt or something. How quickly is regarded as suspicious could be worked out by looking for when there is a divergence between installs (and unique ID requests) and the daily update totals the app store provides. Duplicated IDs should be easy to detect it they access the service later.
- debacle 14y ago> The high load revealed technical issues which we don’t feel we can fix to the level that our paying customers deserve. That doesn't scream to me that piracy killed the game. Rather, piracy just revealed the reality that their server software was shit, and they didn't want to invest in fixing it, so they refunded everyone's money. No harm, no foul.
- TheCapn 14y agoMy interpretation was that they had a budget of $x to run their servers with from y paying customers. $x in no way could provide the services that y+z needed (z being the number of pirates) regardless of infrastructure or efficiency of code. Instead they decided to cut losses and refund without finding a way to block z or monetize it.
- debacle 14y agoI think you're trying to read between the lines of what the article stated.
- astar 14y agohuh? The costs of running a server with even 20x the expected traffic for a few weeks is more than all the time and moey it took to develop the game? This does not pass the smell test at all
- knowaveragejoe 14y agoThey could simply have adopted what games like Minecraft do - the game client is free(perhaps with free single player version too) and require people to have an account to play online.
- johnnyjustice 14y agoI am in favor of this line of thinking, there's a lesson to take out of this about finding a way to make sure you get paid.
- potatolicious 14y agoAh yes, and this is the part where common sense runs head first into Apple's walled garden. This is how almost every multiplayer game does it to great success - tie your copy of the game into an account that the game developer can verify (possibly via a third party, like Steam). This makes it such that it's pretty much impossible for a pirated copy to hit your server. Except, Apple does not allow you to take payments outside their channels for services provided in an App Store app. You don't have any personally identifiable information as the developer - nothing that can indicate if the user is a legitimate, paying user. Administering IAPs and subscriptions is a huge pain due to the opaqueness of Apple's APIs. When customer service gets a complaint, like, say "I subscribed to your shit but I don't have premium access!" you cannot do any verification whatsoever, since you don't know their Apple ID, and their Apple ID was never visible during the transaction, so there's no way for you as the third party to back-trace anything.
- jakejake 14y agoI think this is the only way to go if you have significant server expenses necessary to support the game. Still it sounds like Apple doesn't let you know who legitimately bought the app, and they also prohibit in-app purchases that don't go through their system. So I'm wondering how people actually deal with this?
- mchannon 14y agoSeems to me if I was in their boat, I'd change the server API to require some sort of passive token in order to get a response, push an update at the App Store(1), and force all legitimate users to upgrade. Maximum downtime, one week. The .ipa hackers/leakers will have to get into an arms race with the main company by putting new revs out every week. (1) along with code in the app to make it either highly annoying or completely unplayable unless you upgrade if it detects from the server that an upgrade is indeed available.
- furyofantares 14y agoThat seems like a poor use of time compared to making the service scale, which is something you'd probably need to do anyway if you expect to get more legitimate users. And it you don't expect to get more legitimate users then maybe ongoing development really doesn't make any sense.
- mchannon 14y agoMy way: 5 minutes, $0. Other way: >5 minutes, >$0.
- furyofantares 14y agoAn arms race (your description) is not actually 5 minutes, even if it somehow remains a case of simply revving every week. And my point was that you can't get out of making it scale for your paying customers anyway, unless you never expect to get them. So your way is however much effort your way takes plus however much effort my way takes.
- archagon 14y agoI am skeptical. Piracy exists on iOS, yes, but my understanding is that legitimate users far outnumber jailbroken users.
- bdcravens 14y agoI've explained to clients: never charge a fixed upfront price for an app with free ongoing server access. Doesn't matter if it's a game, social network, dating site, or anything else. Give the app away, and either subsidize server access with ads, or charge a subscription via IAP.
- deleted 14y ago[deleted]
- rje 14y agoTo all the people saying "use a cd key": On iOS a paid download is a transaction that is 100% managed between apple and the user, and as a developer you receive daily aggregate statistics. You don't receive any user identifiable information that you could use to limit accounts. There is no way to supply serial codes as part of a purchase. There is no way for them to create a single account as a part of the purchase. The only thing they could have done is to change their game to a free download and make multiplayer an in app purchase. This would, of course, require that they also make something that is playable outside of multiplayer (since apple won't allow you to ship something that is non functional in the default state). Also, the server-side verification of IAP receipts can fail, which if they do strong checks can block potentially valid users from playing, through no fault of either the player of the developer. (notably, there have been cases of apple's verification server going down or incorrectly reporting receipts as invalid) So please, before you eviscerate the devs, please realize they were trying to do the best they could for the consumer, and as a result got thoroughly screwed over. I wish them the best and hope they recover.