Apple Drops Game Center For Older Devices

Updated CatRambo 0 569 Views

Developers downloading the third beta of , which became available yesterday evening, were disgruntled to find that in this release, Apple's dropped support for both the iPhone 3G and the second generation iPod Touch. The changes were made to Apple's Game Center, a social network centered are iOS games and its accompanying GameKit APIs.

The Game Center has been presented as one of the central changes in iOS4 since it was first announced in early April. New GameKit classes will allow developers functionality that includes technology for matching groups of users based on various criteria and in-application voice chat. On the player side, Game Center allows players to log in with their Apple ID in order to view score boards and achievements as well as to challenge other players and see what their friends are playing. The ability to match skill level will allow players to pick opponents who present a worthy challenge.

It still looks as though the Game Center and GameKit will make it into the release, but the limitations make it less useful to developers who want to tap the market of older devices. Indeed, Apple seems to be anticipating obsolescence with the decision to drop support for the second generation iPod Touch, which is still available for purchase.

The decision may be intended to force users to upgrade, particularly with the fourth generation of the iPod touch scheduled for release this fall.

Other features of iOS 4 include a control panel for location permissions on an app-by-app basis, the ability to encrypt e-mail using the iPhone's PIN code, CoreMotion to allow developers to use the iPhone 4's new Gyroscope, and support for limited multi-tasking in third-party applications. Over 1500 new APIs will become available to developers in the release.

gamecenter.jpg 8.55 KB

Dani AI

Generated

correctly flags the practical impact of the iOS 4.1 beta change: Game Center won’t be present on every device, so apps that assume its availability will break or offer a worse experience to owners of older hardware. The best approach is defensive design — detect Game Center at runtime, make the framework a weak link, and provide clean fallbacks so the same binary still works across the installed base.

Weak-link GameKit and check availability at runtime. In Xcode add GameKit.framework and set it to Optional (weak link). At launch or when showing Game Center UI, test for the framework/class before calling any APIs:

// In Xcode: add GameKit.framework and set it to Optional (weak link)
// Runtime presence check before using GameKit APIs:

if (NSClassFromString(@"GKLocalPlayer")) {
    // Game Center APIs are present on this device/OS — enable/attempt auth
} else {
    // No Game Center — hide related UI and use a fallback path
}

Fallbacks that keep users happy: implement local or server-side leaderboards and achievement tracking; degrade the UI so disabled features are hidden instead of throwing errors; or integrate a third‑party network if cross‑device social features are required (third‑party SDKs existed at the time as alternatives). Release-time options include raising the deployment target if Game Center is mandatory, or keeping a lower deployment target and gating Game Center behind runtime checks.

Testing notes and cautions: verify behavior on real devices (the Simulator won’t fully emulate Game Center/networking), confirm weak-linking is correct in build settings, and ensure any Game Center-dependent UI gracefully reflects the user’s signed-in state or lack of support. Designing this way preserves the app’s reach while still taking advantage of Game Center where it’s available.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.

Edit Preview