## Interface design research

* TOC
{: toc }

### Pure UI

I picked up today where I left off yesterday, reading about Pure UI and Pure UI control. Excited to continue exploring this way of thinking, and statecharts, David Piano, etc, here: [https://statecharts.github.io/use-case-statecharts-in-user-interfaces.html
](https://statecharts.github.io/use-case-statecharts-in-user-interfaces.html
)

### Kevin Lynagh

I then clicked on Kevin Lynagh's name in the Pure UI Control essay and fell into a hole about him and Subform, [some notes here](./notes/kevin-lynagh).

Excited to reach out to him for the podcast. Ditto with Adam Solove. Will reach out now...

Author: Steve Krouse

notes/kevin-lynagh.md

@@ -0,0 +1,34 @@
+---
+title: Kevin Lynagh
+---
+
+# [Kevin Lynagh](https://kevinlynagh.com/)
+
+## [Finda](https://kevinlynagh.com/datatron/)
+
+At first I thought this was silly, but the demo was great. It is crazy that you can't explore all your open tabs in the same interface, and that you have to cycle between both apps and tabs within apps. This is something I don't have too many problems with in Chromebooks, luckily ;)
+
+## [Subform](https://subformapp.com/)
+
+Seems like a really cool tool. Similar to Webflow or FramerJS, in that it's for designing with different sized layouts in mind. 
+
+Interesting how they don't have free trials - seems like they are good about focusing well. Also, they ran a successful Kickstarter.
+
+### [Subform Layout](https://github.com/lynaghk/subform-layout)
+
+Really interesting, and quite similar to my thoughts around "throwing out HTML and CSS and building a layout engine / renderer from scratch." They also note in [the Alternatives](https://github.com/lynaghk/subform-layout#alternatives) section that [Facebook's Yoga](https://github.com/facebook/yoga) is related here...
+
+Kevin explains the motivation for this library in [this video](https://www.deconstructconf.com/2017/kevin-lynagh-choosing-features). Instead of margin, padding, absolute-positioning, and flexbox, they simplify laying out content with two concepts: 1) position before, size, position after, and 2) stretch pixels, which can be used to define relationships between the quantities in (1). This is a clever way to avoid making designers specify relationships with algebra but still ahve a lot of expressivity.
+
+<script>
+
+(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
+(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
+m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
+})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
+
+ga('create', 'UA-103157758-1', 'auto');
+ga('send', 'pageview');
+
+</script>
+<script repoPath="stevekrouse/futureofcoding.org" type="text/javascript" src="/unbreakable-links/index.js"></script>