I disagree with two of your three points: (paraphrasing, fairly I hope) > Objective-C is too much work/too low-level for your app/required because the hardwar

I disagree with two of your three points: (paraphrasing, fairly I hope) > Objective-C is too much work/too low-level for your app/required because the hardware is limited. Disagree. I wouldn't be disappointed to see solid Cocoa bindings in another approved language, but any programmer can learn C, and should. ObjC is a superset of C, and Cocoa is a beautifully consistent framework. The brackets might take a day or two to get used to, but they pretty much disappear after that. The much talked-about memory management model is not nearly as daunting as bloggers make it sound. > Designing hugely complex monolithic apps is difficult on the iPhone. Well, OK. I don't disagree with that entirely. But design is always serious work, information architecture is an art and science, especially for highly complex applications. That said, your app is not Photoshop and a good designer can solve your problems. Photoshop on an iPhone would be Difficult. So would XCode. > App store discoverability is poor, marketing around launches is unpredictable, betas and limited releases are complicated or unworkable, audience feedback is a big problem. Agreed 100%...! :) Good luck with your dev!