Google offers its Play Game Services library in three different formats. One for Android, which uses Java; one for iOS which is called from Objective-C; and a cross-platform variant, which uses C++ and can be access by both Android and iOS.
Google has just updated its Play Games Services to bring the C++ SDK to feature parity with the Play services SDK on Android and the Play Games iOS SDK.
The cross-platform library is important as it allows cross-platform app developers to maintain common code between the Android and iOS implementations of their software. Unfortunately the cross-platform library can sometimes get left behind as Google gives a greater priority to the native Android and iOS versions. One major piece of functionality that was missing from the cross-platform C++ SDK was support for Real-time Multiplayer gaming (RTMP).
The good news is that Google has just updated its Play Games Services to bring the C++ SDK to feature parity with the Play services SDK on Android and the Play Games iOS SDK. This means that game developers who have both Android and iOS versions of their games can now safely add Real-time Multiplayer support using a single C++ code base, rather than having to write one lot of code for Android and another load for iOS.
Now that Google has added multiplayer support across all of its SDKs, it has also released a new set of multiplayer stats. Developers can visit the Developer Console to see how players are using the multiplayer integration and see the overall usage trends.
At the same time Google has also updated a few other things in the Play Game Services. Specifically it has incorporated material design into the user-interface of the latest Play Games services SDKs for Android, cross-platform C++, and iOS.
Google also sees that “Quests” are a popular way to increase player engagement. Quests allow developers to add fresh content to a game without having to release an update. Accordingly Google has added some new features to quests to make them easier to implement and manage. First it has added out-of-the-box toasts for “quest accepted” and “quest completed” events. Secondly Google has removed the 24-hour lead-time requirement for publishing and allowing repeating quests with the same name. This means that developers are now free to publish quests whenever they want, with whatever name they want.
Via: Android Police;
Source: Google;
from Android Authority http://ift.tt/1y4Xfjs
No comments:
Post a Comment