RhinoMobile is a C# .NET library for the development of 3D, cross-platform, mobile applications. RhinoMobile - like RhinoCommon - is based on the Xamarin Mono framework, a fully-functional .NET runtime that works on Android, iOS and OS X. RhinoMobile uses openNURBS (the 3dm NURBS library) and RhinoCommon (the .NET SDK for Rhinoceros and Grasshopper) and handles file IO, gesture recognition and 3D display (OpenGL ES 2.0). It's not the entirety of RhinoCommon, but a subset.
Who should use RhinoMobile?
Anyone interested in developing, prototyping, or just experimenting with 3D mobile development. Though there are many good 3D libraries out there for mobile games, none are focused on 3D modeling and design. RhinoMobile seeks to fill that gap. If you want to develop in C# and target as many devices as possible, this is the library for you. No experience with mobile development necessary…just familiarity with C# and .NET.
Great, how do I begin?
Required libraries and samples:
Is RhinoMobile free? Yes.
Can I sell the apps I develop with RhinoMobile? Yes.
Will apps built with RhinoMobile work on Mac and Windows computers as well as mobile devices? No, with one caveat: Though we have yet to add it to the library, we plan on supporting Windows Phone, which uses a DirectX as a display pipeline and can be run (with some limitations) as a Windows Store App (aka: Metro UI app).
Does McNeel use RhinoMobile to develop iRhino 3D? We sure do.
Wait, is this all of RhinoCommon? No. RhinoMobile uses a subset of RhinoCommon (rhino3dmio), the limits of which are defined by the symbol: MOBILE_BUILD. There's a lot there: Rhino.DocObjects, Rhino.Geometry, Rhino.FileIO…pretty much everything you'd need to read, write, and draw Rhino 3dm.
So I probably can't perform Meshing or run a Make2D command? Sorry, not yet. Given the CPU constraints of mobile platforms, you'd probably consume all your battery life doing so anyway.