![[Patreon Exclusive] The LOOPY Beta!](https://img5.saketami.com/storage/12/vr/ij/9a2cd0-019e79cf-bfd5-725a-9822-0c2dd5cc6bba.png)
[Patreon Exclusive] The LOOPY Beta!
Added 2017-02-24 14:29:58 +0000 UTCActually, you're getting to try out not just one beta version, but two! That's right – I totally can't decide between two different interfaces, so I'm passing the buck over to you:
That page has a video (ugh my voice sucks), with links to the two different versions of LOOPY. The first version shows cause & effect slowly, as "step-by-step". The second version shows cause & effect instantaneously, as "continuous".
I think "step-by-step" would be simpler to understand, but maybe doesn't feel as direct anymore. And I think "continuous" would feel more direct, but it's got too much hidden complexity that obscures understanding. I'm not sure how to make this tradeoff (or if I'm even accurately perceiving this tradeoff!)
So, I need your help! Which version do you like better?
Please leave feedback in the Patreon comments below, and/or, email me at n@ncase.me!
Thank you so much. Remember, I'm making this tool so that everyone can make their own explorable explanations! Or at least, a tool for peeps to think in systems, in feedback loops, more clearly.
<3,
~ Nicky Case
Comments
Haha, I wonder if that *discrete typo made it discreetly into my thesis :)
Jonathan Bobrow
2017-02-28 20:10:04 +0000 UTCThanks Jon! Yeah giving step-by-step a speed slider might be the best of both worlds! > discreet step-by-step the most subtle, secretive step-by-step
Nicky Case
2017-02-28 20:03:27 +0000 UTCSeems like it is preaching to the choir at this point, but yes, discreet step-by-step has a really nice aspect of allowing the user to digest the relationship. One possibility for bringing back the organic feeling of the continuous model could be to include a knob for the speed with which they update. i.e. slow is good for seeing discreet components, cause and effect, but fast can be good go for seeing the overall effects and potentially emergent behaviors of the system. It is true that the easiest point of entry is modeled more closely after what we are used to, with a mechanistic viewpoint, but this tool is definitely building a bridge to systems thinking and comprehension. Note: one fun aspect could be drawing to speed up, or speed down, really enjoy that interface decision :)
Jonathan Bobrow
2017-02-27 22:40:50 +0000 UTCComing up with it is much more involved than saying "yeah, I like that better" :P Hindsight 20/20 and all that jazz.
Emelin Ringuette
2017-02-27 17:52:28 +0000 UTCThanks Aimee! Yeah it seems like step-by-step is the crowd favorite by a landslide, dunno why it took me so long to finally come up with that new design
Nicky Case
2017-02-27 17:48:11 +0000 UTCI like Step-by-step better. It's much easier to understand where the changes are happening.
Emelin Ringuette
2017-02-27 16:38:01 +0000 UTCThanks Joe! And hm, charts may be a good idea! I'm thinking – to avoid multiple lines obscuring each other – maybe I could do something like Bret Victor did for circuit diagrams: show the graphs *IN* each node: <a href="http://www.smallapple.net/blog/pics/inventing_on_principle_demo4-med-auto.jpg" rel="nofollow noopener" target="_blank">http://www.smallapple.net/blog/pics/inventing_on_principle_demo4-med-auto.jpg</a>
Nicky Case
2017-02-25 16:51:22 +0000 UTCThanks for the feedback! And yeah, the "flipping" is still a bit weird, hopefully I can figure out a better way to convey it. (A tangential but similar problem: the phrases "positive feedback loop" and "negative feedback loop" are also confusing)
Nicky Case
2017-02-25 16:49:24 +0000 UTCThanks Philippe! That was my reasoning when I decided to try making step-by-step instead of continuous – the continuous version *did* feel more "organic", but it was just as opaque as real life, while still not being reasonably accurate. Glad to hear that step-by-step actually made a difference!
Nicky Case
2017-02-25 16:44:58 +0000 UTCThanks for the feedback on these feedback loops, Peter! :)
Nicky Case
2017-02-25 16:43:19 +0000 UTCI would love to see it paired with a line chart, one line for each node, x-axis for time/step, and y-axis for size. This line chart could work as a timeline scrubber, so when you say something like "causes a temporary increase" we can see it in the line chart.
Joe Mako
2017-02-24 23:12:42 +0000 UTCI like Step-by-step better as well, but being able to change the speed would be nice. Also the arrows changing colors and directions feels a bit weird. Maybe having (+) and (-) would be more clear? I really like Loopy and think it will be a great tool!
Making Play
2017-02-24 15:44:11 +0000 UTCIt's an awesome tool! For me, the step-by-step version is A LOT clearer and would avoid a lot of confusion as to what is causing what. By removing the arrows, it removes a visible causality, leading to a simple but completely opaque organic result (which is more true to life, but is also like life: puzzling and obscure).
Philippe Vallotti
2017-02-24 15:40:16 +0000 UTCLoopy looks great. I prefer the step-by-step version as it helps me understand how all the parts work together.
Peter M
2017-02-24 14:44:39 +0000 UTC
![[takeostudios]](https://saketami.com/istorage/106010.jpg)
