Comment by zero-st4rs

Great question. From what I understand of RubyMotion, it compiles directly to native, calling into Objective C APIs, and like DragonRuby the Ruby implementation is not MRI.

Since Hokusai uses MRI, one can pull in from that ecosystem of gems.

RubyMotion also appears to support (iOS, Android, OSX) whereas Hokusai intends to support OSX, Linux, and Windows.

Implementation-wise, the framework itself seems different. Looking at the following [RubyMotion app](https://github.com/HipByte/RubyMotionSamples/tree/master/ios...), the logic is spread out over separate files and it doesn't appear to have a templating language.

On the other hand, Hokusai UI components are just a class that inherits from Hokusai::Block, and are self contained blocks that can be stitched together.

Hokusai is more like Vue Single file components in this regard. Hokusai also doesn't make a distinction between a "component" and an "app", they are all just Blocks.

Does that answer your question?