Friday, August 10, 2018

Google isn’t sure how to spell “Fortnite Battle Royale”

The launch of Fortnite Battle Royale has left Google in a slight predicament. While Google is in no way hard up for cash, Fortnite Battle Royale for Android certainly represented the potential for a relatively big revenue stream for an app. That is, until Epic Games decided it would launch Fortnite for Android from its own website, circumventing the Play Store.

But revenue aside, there’s also the matter of Google probably not liking the idea of huge titles circumventing the Play Store as a precedent. Plus, the lack of Fortnite Battle Royale within the Play Store poses a slight security risk to users, as there are quite a few V-bucks scams and malicious clones looking to capitalize on the popularity of Fortnite.

That’s why the Google Play store now displays a message to users in response to searches for “Fortnite,” “Fortnite Battle Royale,” and other similar search queries.

“Fortnite Battle Royal by Epic Games, Inc is not available on Google Play,” reads the message.

That’s right. Google mispelled the “Royale” in Battle Royale. It was likely an honest mistake, but given the fact that Epic Games is making upwards of $300 million in revenue a month, which Google is not getting a cut of, it makes for some fun back-and-forth for us spectators.

Google lists PUBG Mobile, Fortnite’s biggest competitor, at the top of all Fortnite Battle Royale queries, but doesn’t include anything in its message around how to actually find the real Fortnite Battle Royale for Android.

While Google Play’s app review process should catch the vast majority of malicious clones, the message is at least moderately helpful for folks hearing about the Android version of Battle Royale without knowing the details around Epic’s launcher.

For what it’s worth, Fortnite for Android isn’t yet available to everyone. The game launched yesterday as a Samsung exclusive for folks with a Galaxy S 7 or higher, and will become available to all Android phone owners on August 12.

[via 9to5Google]



Source: TechCrunch http://j.mp/2MzEO10

No comments:

Post a Comment