Firstly, C kinda sucks. Undefined behaviour is unavoidable, and compilers see it as license to do whatever they please, so you can actually get a segfault becau

Firstly, C kinda sucks. Undefined behaviour is unavoidable, and compilers see it as license to do whatever they please, so you can actually get a segfault because the compiler decided to "optimize" away your null pointer checks. C is also dangerous, and Apple and Google don't want users getting segfaults. And even if the plan was to bind the C apis to high level languages, people would just write their apps in C. Secondly, for stateful graphics programming, the most common kind of application on mobile, OO works really well. So Apple and Google both picked languages that support OO. Finally, despite all this, both Apple and Google have native C apis. You can write C freely in Objective-C, which is a superset, and Android has its NDK.