3 ms·
I'm the author of this framework. I think Matcha has a really cool approach to building UIs. Everything is built on top of interfaces, so its very easy to reuse
by overcyn 9y ago
I'm the author of this framework. I think Matcha has a really cool approach to building UIs. Everything is built on top of interfaces, so its very easy to reuse and customize components and layouts. Its not quite production ready but I can any answer any questions.
- codesternews 9y agoThanks overcyn great framework. How you are bridging between iOS and Android. Can you provide simple example code that make me understand how you make things working and internal details. It will help me to understand better. Any future plans to write blog.
- overcyn 9y agoThe bridging happens through Cgo and JNI. bridge/matchaforeign.h contains the functions that Go implements that can be called by ObjC/Java and bridge/matchago.h are the functions that Java/Objc implements that can be called by Go. Everything else is built on top of that.
- dcu 9y agohow does it compare with gomobile?
- overcyn 9y agoRepasting my comment from below, but Matcha is actually based on top of gomobile, albeit with a bunch changes to fit the needs of this framework. Gomobile provides language bindings and Matcha adds a usable component library on top of that. It serializes Go data structures into protobuf, passes it through to iOS/Android and creates the necessary views. Matcha also does all the layout, event handling etc.
- therealmarv 9y agoI really like using go for writing e.g. the logic part of an Android/iOS/Desktop app. Would not it make more sense architecture wise to write UI real native and do the interfaces really well to the logic binary go parts? Are there good examples/libs for this approach?