Velluma Studio
"Complex motion, zero dependencies."
Hi everyone,
I’m Dave, and I just finished building Velluma.
I built Velluma to kill bloated libraries and tedious coding. It exports lean, native CSS and JS. No subscriptions, no fluff—just pure motion.
I’m a developer who values site performance and clean code, so I built this to solve my own workflow headaches. Now that it's live, my focus is purely on getting it in front of the right users.
A quick question for the community: I’m avoiding the social media "content treadmill" as much as possible. Does anyone here have experience getting initial traction for developer-focused tools without relying on constant social media posting? I’d love to hear what channels (directories, newsletters, or outreach) worked best for your first 10–50 users.
Any feedback on the tool is also welcome!
3 Comments
A lightweight implementation is valuable, but I'd keep validating what developers are actually switching for. They may not be replacing animation libraries—they may be replacing the maintenance cost that comes with them. That's a different positioning story.
Hi Aryan, thanks for the advice I really like this way of framing it, this is solid advice and I will defineitly take it on board. Thank you so much.
One thing I'd keep watching is whether developers describe the switch as "better animations" or "one less dependency to think about."
Those sound similar, but the second is much harder for competitors to take away because it's really about reducing long-term complexity, not adding another feature.