Frank – depending on your view point it is (a) incredibly simple or (b) unbelievably frustrating! That doesn’t really help you does it? If your app has a straightforward (formulaic / forms type UI) then it is reasonably OK. If it doesn’t really involve much algorithm development to do smart stuff it is reasonably OK. If it runs all on the App and doesn’t need to exchange data with a server it is reasonably OK. If it is for your own use and doesn’t need to be fast, crash resistant, constantly updated to cope with OS variation it is reasonably OK. If it doesn’t require too much clever hardware interaction (e.g. camera, accelerometer, etc) it is reasonably OK. If it is only for one phone OS (and even better one screen size) it is reasonably OK. If you have some idea of the language you are developing in it is reasonably OK. If you have some experience of the IDE you are using it is reasonably OK. If you don’t have to dance through the apple restrictions to make releases to your beta users it is reasonably OK.
If some of the above are not true then take the pain involved in each one and multiply them together. The chances of making money directly from Apps are almost non-existent, even Apple users are accustomed to most functions being free now.
On a more positive note, if you think it will be easier employing a professional App developer – it might not be unless you can clearly define exactly what you want it to do, and how. In that regard at least making a prototype yourself has a lot going for it. Someone who could hold your hand through the painful bits would be good though.