This is a tricky balancing act - while Android is lax at the beginning and capricious (that’s the word - i.e. at any moment can do anything out of the blue) later on, Apple is careful at the beginning and thus less tension later.
However, with Apple a problem remains - since bulk of effort is making the first version of your app, you STILL have to commit time to make the app, and then submit to Apple (so here the “nail-biting” part STILL comes AFTER you have done the bulk of the effort).
I suppose a way to reduce the risk in this Apple process maybe to initially submit a very rudimentary version of your app - and if that gets approval then work on improving it (knowing that Apple approves of the app and doesn’t see any copyright issues etc.).
However, the allure of Android initially was that (in a way it is a “bait and switch”) that early entry is easy - you can be on the market for some time - then something changes at Google and they may act (OR more often - your apps may not encounter any issue with Google - but you see cases of apps being banned - and that creates a bad feeling about Google “fairness” - since there is never an examination of what/why from Google - to protect it’s business processes presumably - while we only hear of the developer view). So in this environment of low information, all sorts of “perceived threats and risks” are created in the minds of developers (esp. since they see no response from Google).
The situation is a CLASSIC psychological study of how HORROR movies are made, or how a feeling of “dread” (i.e. a persistent feeling of antcipation of danger) can be created in psychological test subjects when they are put in a darkened room with sensory deprivation (eyes blindfolded) - and perceived threats (and the IMMINENT arrival of a threat can sometimes break people).
Example from a TV show recently - in one of the episodes of “Brain Games” (National Geographic - Brain Games - Season 2 - Episode 3 of 12 - title: “Don’t Be Afraid” - see latter part of show) they blindfold and secure a person to a chair - prior to blindfolding they show them mice, snakes etc. - then while blindfolded they touch the person’s hair etc. with hands or throw a rope on their lap - so person THINKS it could be mouse/snake etc. - but then they leave them be so the person ANTICIPATES something about to happen. For some subjects this is enough to break them - even though nothing is ever done after that. The episode illustrated the damaging effects of “dread” i.e. where a subject EXPECTS something to happen at any moment, and that anticipation exhausts their inner stores of strength until they are unnerved and cannot take it any more.
Basically this is similar to Chinese torture (dripping water droplets on forehead etc.) - basically the PERCEPTION of a “sword over the head” can break subjects as the ANTICIPATION of a possible dangerous event creates a persistent feeling of (what is technically also called) “dread” in the subject - which can “break” some subject even though nothing is done to them. This is the type of environment Google is creating for developers (even the ones not deliberately working to circumvent Google policies).
Earlier I have referred to Google behavior as “Kafkaesque” - however, what I have pointed out above much more faithfully captures the FEELINGS that Google behavior tends to evoke in developers.
http://en.wikipedia.org/wiki/Hooding
Hooding is sometimes used in conjunction with beatings to increase anxiety as to when and where the blows will fall.