- What do you think makes Subform different, and in comparison to what other tool, specifically?
The fact that it behaves like box-model/auto-layout is the key difference. Every object aware of its surrounding, and every text is actually a box. I wish that Sketch has a “button” tool that behave like this —in Keynote every text object is a box— so the box and text object is not a separate entity.
- What elements within Subform made your workflow easier than using X (X being the tool you normally use to build a screen like this)?
It forces me to think of how things laid out in a structure, whereas with a layer model the object size and position, are irrelevant.
- What elements within Subform made your workflow more difficult than using X?
Lack of drawing tool, oval, polygon, line, etc. But I get that they want to build something simple first and then expand from there.
- Did anything in particular take you out of 'the zone', assuming you got in one at some point?
Whenever I change child layout axis things breaks, and kinda freaks me out a bit. Also the default
background-position should be centered at
50% 50% and
- What are your thoughts regarding either the layout engine and/or components as two potentially key capabilities that make Subform a superior design tool?
Component with multiple data set and overwrite-able datum is a killer feature for me, but the GUI need more polish. Subform’s layout engine is easy enough for me to wrapped my head around, but I don’t know how others with no front-end dev experience feel about it.