My understanding is that you "describe" your project using XML or JSON or code (which can be written against libraries in "the language of your choice"). Then, Kozo spits out a skeleton project based on that description in the tech stack of your choice.

So, you would (optionally) write code in unspecified languages to describe your project, and then you would have to actually finish the skeleton project, of course.

That's already quite accurate. However, you can also bind against external APIs and deploy Docker applications to fill the skeleton application.

The structure can be written in a JSON or XML format or alternatively be constructed using one of our libs, which are planned to be written in D, Python, Java, Ruby, PHP and possibly/almost certainly others.

We generate client & server side code and you can get the source code out in one of the supported stacks. Alternatively, we can host for you on a scalable stack, so you wouldn't need to care about setting up your own environments. If you deploy on your own stack, you obviously can have full control, if you deploy with us, we'll provide a number of configuration options, but generally it's a compiled server app running on a auto-scaling stack.

FWIW, I think this is a really cool idea. When I was trying to imagine use cases, most of them involved a project being generated on only one stack. Mobile apps are the only exception I can think of. Do you expect that most people will only generate their project once, on a single stack?

Right now, mobile seems to be the "exception". However, when you're thinking of other, "less common" stacks, like cloud-based Desktop applications or Browser extensions, new use cases become evident.

Furthermore, we're getting more and more stacks right now, such as wearables and sooner or later AR/VR devices/platforms - hence, the need for such as cross-platform tool will certainly increase. Plus, we also make developing single stack apps easier/less painful, so even then it will (hopefully ;) ) be helpful for people.