bloom

what it is

one project instead of a pile of disconnected experiments. bloom is meant to be a place where different ambient systems can live together and still feel like the same piece of work.

what it had to do

hold multiple visual directions without becoming noisy, overdesigned, or random. the point is not showing every trick at once. it is making each scene feel intentional, soft, and worth exploring.

scene set

• petals reacting to cursor movement or scroll direction.
• soft blobs that merge and separate with section changes.
• background season shifts that gradually change the atmosphere.
• generative botanical shapes built from simple mathematical rules.
• music-reactive canvas ideas tied to Spotify playback state.
• a drifting dream-map made of moving nodes and soft connections.

what i built

the concept, the interaction direction, the visual system, and the public framing for how the scenes fit together. it is also where i can test motion, rendering, and idea selection without forcing every experiment into the main portfolio.

result

it gives me one stronger creative-coding project instead of six weak ones. it also acts as a better proof of range: animation logic, interaction design, scene structure, and visual restraint all in one place.

links