I for one think that this looks incredibly impressive. A solution to reduce what needs to be written while giving ruby developers a powerful way to build a mode

I for one think that this looks incredibly impressive. A solution to reduce what needs to be written while giving ruby developers a powerful way to build a modern frontend, making it possible to stick with pretty much Ruby. And the website explains the concept very well. It's pretty much contrary to the route I took for my current project (and Rails instead of Ruby :( ), but something to bookmark and consider next time. Excited to see whether that concepts works as well in practice. That's a win in my book. One question though: In your diagram you are saying Infrastructure 1, 2, 3 for the classical/current approach going into one API vs Matestack sitting on top of one infrastructure, right? Why? If there is an API sitting between backend and the UI there should not be a need for three backend infrastructures. I feel like you mean something else there, and the text also does not fit to the diagram as I understand it. Maybe something to double check. The comment below how Matestack maps to native apps is warranted though. You are planning alternative renderers to web/vue, targeting native apps?