Also, it’s not appropriate for some things even if it’s technically possible…the RSS reader, for example: I’m not sure it makes much sense to have the overhead of a 3D engine hanging around for that.
You didn’t say anything about iPhone development. Because of the extra limitations and expectations of that platform, as great as Unity is, I wouldn’t recommend it for “standard” applications.
ofcourse non iphone theres is already C#.NET/WPF/Silverlight
But for iphone it still doesnt seem like a bad idea since wethere its 3d gfx or calling a webservice I am under th eimpression its all easier to code with unity than anything else…
Maybe in the future Unity can work more on the GUI side and have Datagrids etc… with the idea to make creating applications more attractive
Not really, since you don’t have direct access to the standard iPhone UI API. You can hack various things with links to native Objective-C code in Unity, but then it would be easier just to do it all natively in the first place.
Or do what he realized himself: Invest in MonoTouch if one does not want to learn objc or just has a keyboard layout where the total overdriven use of [ ] actually wastes a lot of time, especially as apple is not following the correct keyboard layouts for non us keyboards at all and actually never has.