The main thrive for starting Boxary development is that platforms, in general, are too complicated to learn. Some float on code and the addiction it generates, other ones push forward with their designs and smooth interactions, some nourish the argument of the MVC pattern, some claim to be dead simple. And they all come with a learning curve, be it steep or flat.
Boxary starts with a metaphor that resembles desktop publishing, spreadsheets, photoshopping (ouch!). The Canvas.
Boxary knows about Apps, but different. Read about the things that Boxary does the Boxary way. The App.
Boxary maps entities and relationships onto graph models. The Structs.
Boxary separates its applications in a Box. That's why the name.
Boxary defines a canvas, a working area, that contains the data model, its viewable face and the domain rules it supports, as the central paradigm.
In a certain sense the learning curve of Boxary is overcome; well, if you know modern IT. Boxary applications make use of a graph notation, not to introduce a new approach, but alone to create a visual aspect to the application in the process of creation. The name canvas is one of them.
Now, if you dare to expect the shortest path algorithm, a breadth-first or depth-first transversal you will get disappointed.
But Boxary defines vertices, edges and planars. You draw the application onto a canvas and at some point, you render it in the context of a browser.