Ogre limitations on iOS/Android?

[Kryogenik]

I've been thinking about getting into mobile app development, but I want to know what I would be getting myself into. I've heard certain things like CG aren't supported on mobile devices, are there any other things that aren't supported? I also noticed that there is an iOS Ogre SDK, but not one for Android. Does this mean that porting Ogre to Android is more "hacky" or less functional?

How much of iOS/Android development can be in C++? I want to be able to make an Ogre game and port it to iOS/Android without rewriting the whole game, just the functions used to get input from the different devices and such.

What are some things to keep in mind when it comes to mobile app development in general? As mentioned, I don't have any experience with it.

For iOS development, I need a Mac, XCode, and the iOS Ogre SDK, correct? For Android, I need the Android NDK, but which Ogre SDK would I need?

I'm asking all these questions because I don't own a Mac computer or an Android device and would have to buy both before I could develop for iOS/Android. I want to get into mobile development because as a one man game developer, I would probably have more success making games for mobile devices than I would making PC games, as mobile games can be simplistic and still be popular. Thanks for any help.

[TheSHEEEP]

What are some things to keep in mind when it comes to mobile app development in general? As mentioned, I don't have any experience with it.

One thing you have to keep in mind is that...

I want to be able to make an Ogre game and port it to iOS/Android without rewriting the whole game, just the functions used to get input from the different devices and such.

... is not going to work.

User experience on mobile platforms is vastly different from the one on desktop machines/laptops. Just compare how you are browsing on PC to how you are browsing on a tablet or smartphone (how you use your fingers). It's two different worlds, really. And good applications know and mind that.
You will have to re-structure how users are going to interact with the application.
If you know that you'll do something for both desktop and mobile, and you don't want to restructure completely, I would advise using the mobile-style interface also for desktop (with slight adjustments).
A desktop user can more easily use something designed for mobile than the other way around.

The best thing is to optimize the experience for both user groups, which means that you'll end up with two interfaces, that do not only use different system commands, but also look different.

Also, processing power is obviously very different, as well as graphical performance. So if you're going for the lowest denominator, your app will probably look unoptimal on desktop platforms.
This may be something you do not really want, so your version will probably differ in graphical quality already (better assets for desktop). If so, you should also do the interface adjustments.

TL;DR version: desktop <-> mobile development done right is a lot more than just porting function calls.