Blog

I was not building random projects. I was following the bottleneck.

Creatillo, Once UI, Magic, Aveiro, and Chirio are not disconnected ideas. They trace how digital creation moved from design to code, publishing, and distribution.
Avatar
Updated by lorant.one 5h ago
Once UIAveiroSketches
© lorant.one // All rights reserved.
Built with Aveiro
At first glance, my projects might look like a trail of unrelated ideas. An art platform. A design system. A Next.js component library. A collection of templates. A publishing platform. A social media API. But they are not separate bets. They are one project evolving as the bottleneck moved.

It started with Creatillo

Creatillo was an art platform—a social network for visual creators. It launched with roughly zero users. The easy conclusion would be that it was simply a failed product. In practice, Creatillo gave me the design language that became Once UI. The platform did not find its audience, but the system underneath it had value beyond the original idea. So I extracted it. First, Once UI became a Figma design system built from Creatillo's foundations. At the time, design tokens and systematic design were still early concepts for many teams. The problem was no longer drawing individual screens. It was creating a language that could keep an entire product coherent. Then attention shifted from design files to implementation. Once UI became a component system for Next.js, around the time AI-assisted coding started becoming genuinely useful. Tokens became components. Components became code. The design system stopped being a reference developers had to translate and became something they could use directly. From there came Magic: a growing collection of templates built on Once UI. We launched several products from the same underlying system—blogs, portfolios, documentation sites, galleries, journals, and other focused experiences. The question changed again. If the system could generate good starting points, why should every person still have to host, configure, maintain, and update them like a traditional website? That question became Aveiro. Most of those Magic templates are now available as hosted sites. The design system, components, and templates are still there, but they have moved into the background. Instead of assembling a website, you choose a useful structure and focus on the content. AI can help maintain it, but publishing remains reviewable and under human control. Then another bottleneck appeared: distribution. Publishing something on a site is only part of sharing it. Every social platform has its own API, formats, validation rules, media requirements, and strange edge cases. So I built Chirio, a unified social media API now used by Aveiro itself. Creatillo became Once UI. Once UI became code. Code became templates. Templates became hosted publishing. Publishing expanded into distribution. The projects changed because the constraint changed.

I was following attention

Creatillo happened too soon. Once UI for Figma was early for its time. Once UI for Next.js was early for its time. Aveiro is early for its time. That sounds like a convenient story to tell after the fact, but there is a consistent movement underneath it. First, attention was on tokens. Then components. Then code. Then systems. Then templates. Now it is moving toward autonomous publishing systems that can understand ongoing work and help turn it into useful communication. I have not been jumping between random ideas. I have been following where attention is spent—and where it becomes unnecessarily expensive. For years, the hard part of digital creation was making something look good. That is changing quickly. Today, generating beautiful visual content is easy. Making people care about it is becoming harder.

Beauty is no longer the bottleneck

The signs are fairly clear: the bottleneck is not design. The most successful digital presence will not necessarily belong to whoever uses the slickest technology or builds the most impressive eye-candy animation. Those things can be viral. People enjoy reacting to them and sharing them. But design does not equal value. Beauty without meaning is decoration. As visual quality becomes abundant, it becomes less differentiating. A polished landing page can attract a glance, but it cannot create a reason to return. Meaning comes from the work behind it: a useful idea, an honest observation, a real project, a skill being developed, or an experience worth sharing. The emerging design problem is not how to make content more beautiful. It is how to reduce the distance between living something and sharing it.

Publishing should fit into life

I think the next shift will happen when we realize that good, authentic content can be distributed easily without turning our lives into content factories. Maintaining a blog about a hobby should not feel like maintaining a Myspace page. You should not need to think about hosting, layouts, content management, responsive behavior, SEO, newsletter software, or five different social dashboards before sharing something you learned. The flow should be embedded in the activity itself. You go bouldering and notice why a certain hold feels difficult. You cook a simple meal and learn which ingredients work together. You draw something and discover a technique worth remembering. Those lived experiences are already content. AI does not need to invent a dramatic personal story around them. It can help structure the notes, clean up the language, prepare the formats, and distribute the result. The source remains human. Imagine launching small sites about bouldering, cooking, art, plants, repairs, local history, or whatever else you genuinely care about—instead of spending the same hour doomscrolling through other people's lives. Not because everyone needs to become a creator. Because creating a small body of useful knowledge is a much better relationship with the internet than feeding an endless timeline. That is the curve connecting all of my projects. I started by trying to build a place where people could share visual work. Years later, I am still working on the same problem: making it easier for people to turn what they create, learn, and experience into something meaningful for others. The interface changed. The intention did not.