The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
"Designed and handcrafted a table lamp using thin wood slats arranged in a spiraling, organic pattern around a central light source. The staggered slat construction creates a warm, diffused glow with dynamic shadow patterns."
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Manifestation apps have an audience problem most teams don't talk about: the same interface has to work for a teenager building a vision board and a retiree tracking daily affirmations. Design for one and you alienate the other.
For Manifestie, that meant treating the visual language as functional, not decorative. The color palette and animation aren't there to look calm they're there to lower the barrier to a daily habit that most people abandon within a week. Progress tracking and feature navigation had to stay simple enough that neither age group hits friction, while the aesthetic still signals "this is a space for reflection," not a productivity tool wearing soft colors.
The harder design question wasn't the interface it was building something that feels personal to two very different life stages without splitting into two products.
Anyone else designed for an audience that spans generations in one build? Curious how you handled the tone split. Check it out.
this is sooooo dreamy, i love the collectible aspect you've incorporated!
Which style wins for you? 🤔
We’re testing out two theme directions for Avenra’s dashboard component cards; featuring real-time spending breakdowns, project progress metrics, and time-off tracking.
Curious to hear your thoughts! 💬
8 voted
42%
11 voted
58%
19 votes
Closed
Building a platform that covers scheduling, customer records, communication, and appointment booking means designing across very different use cases. The risk is that each use case starts pulling in its own direction and the product ends up feeling fragmented.
We established a consistent way to use components early and applied it at two levels.
1/ At the page level, consistent text sizes and layout logic.
2/ At the component level, the interaction patterns show whether you are filtering technicians, service types, or job durations.
The result is a system where you don't need many text sizes, components, or colors because everything follows a coherent logic.
The filter panel is one example of that direction.
