78Instagram likesOn the announcement post · 1 Jul 2025
01The invitation carried the challenge on its own, with no finished screens behind it to borrow credibility from
02One cover held across Dribbble, Behance and Instagram without a redraw per platform
03Fifteen days of daily posting had a front door before day one, so the series launched instead of drifting
Posted to the Graphique feed as the challenge announcement. The number is small and it is public. The link below goes straight to the post if you want to check it.
02Context
Launch key art for a self-initiated design challenge: fifteen days, one screen a day, announced into the usual design-community spaces on Dribbble, Behance and Instagram.
The concept
A launch asset really only has one job: stop the scroll before there’s anything real behind it to see yet. So I built the invitation first, and let it prove on its own whether the challenge was worth showing up for.
I designed the cover before day one of the challenge existed, mostly to find out for myself whether an invitation alone could actually stop a scroll.
05The system
15 Days of UI
Material
Figma-native elements (cursors, frames, component chrome) so the artwork stays visibly tied to the software the whole challenge actually lives inside.
Texture
Distressed concrete underneath everything, mostly so the stickers have a surface to feel stuck to instead of just floating on a flat background.
Density
Maximalist, on purpose. Stickers, arrows, overlapping layers. A quiet cover for a challenge post tends to read as an apology rather than an invitation.
Credit
Tool credit and my handle stay visible on it. A challenge post is a small brand launch whether you treat it that way or not, and a launch with no name on it doesn’t really go anywhere.
06Decisions
What I chose, what it cost, what changed.
D01
Went maximalist: sticker-heavy and loud.
Why
The cover is competing with an infinite feed, not with other posters pinned to a wall. Restraint just loses that particular fight.
Gave up
It’ll date itself hard. This reads like exactly the year it was made, on purpose or not.
Result
A cover that’s genuinely hard to scroll past without noticing it.
D02
Figma-native elements over generic UI illustration.
Why
The challenge itself happens inside Figma. Borrowing its own visual furniture makes the poster feel like it came from inside the work, not next to it.
Gave up
The reference only really lands for other designers. Everyone else just sees stickers.
Result
An announcement that reads as insider rather than advertised at people.
D03
Built the launch asset before any of the work it was launching existed.
Why
It isolates the actual question. If the invitation can’t earn attention on its own, no amount of good screens behind it later fixes that.
Gave up
The cover couldn’t reference a single real screen, because none of them existed yet.
Result
A real test of whether a launch asset stands on its own. It did.
07Out in the world
The cover came before the challenge, deliberately: a test of whether the launch itself could earn attention before a single real screen existed behind it. Stickers, arrows, a distressed concrete texture, loud enough that a quiet, minimal treatment would have read as an apology instead of an invitation.