No sooner did we ask (twice) whether the iPhone 3G S will speed up the splitting of the iPhone OS platform than Mobility Today finds the little pop-up alert, above, just chock-a-block full of confirmation.

Not the most elegant or user friendly of solutions, so perhaps this ultimately lies more with how developers handle different hardware options than the existence of the options themselves?

Could a video/camera button not disappear for a current iPod touch, default to launching only the camera for iPhone 2G and iPhone 3G, or launch the camera with a video switch (like Apple’s built in Camera app will have) for iPhone 3G S?

This morning we wondered aloud about whether the iPhone 3G S would be splitting Apple’s mobile OS X platform. Looks like we weren’t the only ones wondering.

Engadget‘s Chris Ziegler takes a look at the new hardware’s PowerVR SGX graphics-core‘s support for OpenGL ES 2.0, and that led him to this language in Apple’s iPhone SDK documentation:

“When designing your OpenGL ES application, the first question you must answer is whether your application will support OpenGL ES 1.1, OpenGL ES 2.0, or both… Your application should target OpenGL ES 1.1 if you want to support all iPhones and iPod touches.”

Sure, with 40,000,000 iPhones and iPods touch on the market, many developers will want to stick with OpenGL ES 1.1 support, but like with any generational transition — even slow ones — eventually more and more might just want to push the new hardware and see what it can do…

Apple has begun their direct email campaign for the iPhone 3G S saying:

Phone 3G S features a remarkable new video camera and hands-free Voice Control. It’s a revolutionary phone, a great widescreen iPod, and a breakthrough Internet device in one. And it opens up a whole new world of applications. All that and more makes it the best iPhone yet.

It’s that second to last sentence that drew our attention. New world of applications? What does that mean for the old world? More after the break…

Up until now, pretty much every application released for the iPhone worked on all models of the iPhone, 2G and 3G. Sure, 3G had GPS where 2G did not, but thanks to CoreLocation, apps could fall back on cell tower triangulation or Wi-Fi router mapping to get by.

Things are a bit trickier when we include iPod touch, as both generations also lack GPS (but have Wi-Fi router mapping at least) and a built in microphone (though a headset mic will get you by), the first gen lacks Bluetooth (3.0 will unlock the previously hidden Bluetooth in the second gen), and the second gen adds Nike+.

iPhone 3G S also adds Nike+, to the aforementioned video recording and voice control, along with faster processors, accessibility options like VoiceOver, faster processors, and the digital compass.

Video will still downgrade to still camera, voice control to physical screen taps, and the digital compass to accelerometer and CoreLocation voodoo, and the faster processor to, well, slower processing. But the question becomes, when will the differences be enough?

So far we haven’t seen developers or users have to worry too much about app compatibility between devices, but at some point that will change more significantly. For example, if some developers — especially game developers — start targeting the faster processors to get better quality games, will that encourage users to upgrade to the latest hardware or just p!$$ them off?

It’ll happen eventually. One year Apple will release a future iPhone that’s so different from the original iPhone 2G that — like with the Mac today — we’ll see “only compatible with…” start to appear even on iPhone OS firmware. Heck, Apple already says iPhone 2G and iPhone 3G hardware are different enough that they’re not devoting resources to putting MMS or A2DP Stereo Bluetooth on the original iPhone.

Is iPhone 3G S one more step down the platform splitting path?