[Mono-osx] MonoTouch vs Unity for iPhone
Miguel de Icaza
miguel at novell.com
Thu Nov 26 00:19:51 EST 2009
Unity in general is better suited for building games, in
particular 3D games and there is a large community of game developers
for it. The developer experience is mostly focused on the game side
of the code and you will do a lot of your tune-ups in Unity itself.
MonoTouch will work if you are planning on building your own
engine (like the SharpGames guys did with XnaTouch), and the
development experience is mostly focused on the code.
I think that MonoTouch is better suited for more business-y
application setups than games, for apps that need to use the native
CocoaTouch APIs day-in and day-out.
> - .NET 2.0 and 3.5 features (which, I take it, includes generics)
> - No more MonoTouch updates after one year
> - Specialized in game making, so good for me
> - .NET 1.1 (no generics)
> - Startup "Made with Unity" splash screen (unless you get the $1500
> rather than the $400 one)
> Am I overlooking anything? Has anyone tried either and can share their
> Is MonoTouch actually a good choice to make a game (something rather
> 2D)? I take it it can do everything plain Objective C can do? No
> idea what
> the graphics API is like, for example, but I assume it's iPhone
> View this message in context: http://old.nabble.com/MonoTouch-vs-Unity-for-iPhone-tp26521303p26521303.html
> Sent from the Mono - OSX mailing list archive at Nabble.com.
> Mono-osx mailing list
> Mono-osx at lists.ximian.com
More information about the Mono-osx