[rolae]

As a UX Designer with limited coding abilities this looks very interesting. I tried to describe a little feature that we will need to build soon. That was pretty straightforward, but I also felt very limited as there was no way to comment anything in the spec.

But it can be really helpful to think through all the states that the application can be in, something I often neglect. Not sure if I will automatically think through the non-happy paths, but it might help.

With a more fleshed out syntax, I could very well see myself using this. But I don't see myself using the Javascript / prototype part, if I actually to that I could probably just create a prototype in Vue.js, which then also would describe all the states. I would focus on the spec part and make that more powerful.

[lynaghk]

Thanks for trying it out, and I 100% agree with you that it's helpful to "think through all the states that the application can be in".

I'd consider Sketch.systems a huge success if the only thing it achieves is teaching UX designers how to think of behavior in terms of states. (And reminding programmers, since coding sometimes makes easy to skip thinking about states and just keep nesting callbacks =P)

Re: Syntax --- the spec language does support comments: all characters following an octothorpe (`#`) will be ignored.

See this "egg timer" sketch for an example: https://sketch.systems/lynaghk/sketch/32bb376ee5c9dc9bf26012...

I'll add comments to the default spec so that they're more discoverable.

Can you be more specific about what else you'd like to see "fleshed out" in the syntax? Thanks for the feedback, I appreciate it!

[irq-1]

The transition names aren't scoped.

Typing breaks the diagram until you've correctly typed the line. It should ignore the line if it's not syntacticly correct, or you could have the diagram show an error.

It needs functions, or at least function names, that lead to different states.

Interesting though.