David Aerne

@meodai
3 Followers
3 Following
8 Posts
Self employed Design & Interaction developer
Websitehttps://elastiq.ch/
Githubhttps://github.com/meodai/
Xhttps://x.com/meodai
Codepenhttps://codepen.io/meodai/

Maybe that’s what all these tools are: ways to be lazy more intelligently.

Automate the boring parts so I can focus on what actually matters: the logic, the relationships, the unexpected combinations that appear when systems start talking to each other.

If you’re into this kind of exploration systems that shape color, tools that spark surprise, and the experiments that happen along the way, feel free to follow along.

( https://albers.elastiq.ch/ )

I keep circling back to this: maybe we should spend less time making individual decisions and more time designing how decisions get made.

Less manual picking, more relationship building. Less fixed outcomes, more intelligent systems.

https://meodai.github.io/color-name-api/

Color Name API

Get human-readable color names from hex codes using our simple REST API.

Color Name API

Change one variable, the whole system responds. It’s not just about speed. It’s about creating conditions for discovery. Encode relationships, not results, and you get combos you’d never try manually. Coherence across complexity. Emergence.

(https://meodai.github.io/pro-color-harmonies/)

All of this (plus my generative-art obsession) pushed me toward a bigger idea: relationships matter more than individual choices. Lately I’ve been exploring dynamic palettes. Color Router treats color decisions as formulas: “darken primary by 15%,” “pick highest-contrast brand color.” (https://meodai.github.io/color-router/)
Then RYBitten, translating colors through Johannes Itten’s subtractive wheel: an attempt to make digital color behave a bit more like paint. (https://rybitten.space/)
That led to Poline: https://meodai.github.io/poline/, where you place anchors, define relationships, and let math do the blending.
Color is my lab of choice. Picking colors one by one always felt slow and brittle. So inspired by Pixel Artist, I built RampenSau (https://meodai.github.io/rampensau/): exploring ramps by cycling hues and easing curves, surfacing palettes I’d never have tried manually.
Hi! I’m David — impatient with repetition and fascinated by surprise. That mix pushed me toward building systems with internal logic that create new outcomes, instead of curating static collections. Kind of like Karl Gerstner’s “visual programs”: not fixed solutions, but frameworks that keep generating solutions.