PlayStation 3
A single petal, a gust of wind, and a city remembering what it was to breathe.
Flower is a 2009 short-form adventure game developed by thatgamecompany and released exclusively for the PlayStation 3. In it, the player controls a single petal carried by the wind through a city slowly being reclaimed by overgrown nature, guiding it back to a field of wildflowers. The title was a free download on the PlayStation Network store and served as a showcase for thatgamecompany's philosophy of emotion-driven, minimalistic game design.
As the first major retail-facing title from thatgamecompany (founded by Jenova Chen and Kellee Santiago), Flower established the studio's signature approach: no text, no HUD, no score—just a sensory journey shaped by wind physics and a quiet, melancholic-to-triumphant emotional arc. It became a proving ground for the team's engine work and design language that would later define Journey.
- Developer
- thatgamecompany
- Director
- Jenova Chen
- Platform
- PlayStation 3
- Release year
- 2009
- Genre
- Adventure / Puzzle
- Distribution
- Free download, PlayStation Network (PS3)
- Playtime
- Approximately 20–30 minutes
Lore & Background
In the world of Flower, a once-bustling metropolis has been largely abandoned to the elements. Vines crawl up glass towers, rivers run clear through cracked streets, and the wind carries the memory of a world that was. The player is not a hero with a name or a quest log; they are a single petal, light and purposeless until the first breath of wind gives them direction. The city resists at first—tightly packed buildings, narrow alleyways, the cold geometry of human order—but as the petal pushes outward, the architecture softens, the palette warms, and the skyline dissolves into rolling hills and open sky.
The emotional grammar of the game is built entirely on physics and sound. There is no dialogue, no objective marker. The wind is the only guide: a subtle pressure that pulls the petal forward, a gentle nudge that says *this way*. When the petal slows or is caught in a still pocket of air, the music dims and the colors desaturate. When it catches a strong current, the screen blooms, the score swells, and the city seems to exhale. By the time the petal reaches the meadow and re-joins the flower it came from, the player has experienced a full emotional arc in under half an hour without a single word of exposition.
Flower exists in the canon of thatgamecompany as the studio's first public statement of intent: that a game can be a feeling rather than a challenge, that the player's body (the controller's subtle tilt, the patience of waiting for a gust) is the interface, and that brevity can carry as much weight as a hundred-hour epic.
In Their Own Story
The wind finds you in the alley behind the old clock tower, where the ivy has swallowed the face and the hands point to a time no one checks anymore. You are small. You are one petal, no wider than a thumb, and the concrete beneath you is cold and grey and smells of rain that fell three days ago. You do not choose to move. The air does. A gust rolls off the river, catches your edge, and you are *launched*—tumbling past a fire escape, threading between two lampposts, skimming the surface of a puddle that reflects a sky you will not see for another two blocks. The city is tight here, all right angles and glass, and the wind fights you, folding you into corners, pressing you flat against a wall. You wait. You wait. Then a longer breath, a deeper pull, and you are over the rooftop, over the last concrete ridge, and the world opens. The grass is impossibly green. The flower is waiting. You land, and the stem accepts you, and the meadow hums.
Reader's Guide
Thatgamecompany began Flower in 2007 as an internal proof-of-concept for their custom engine, with the goal of building a complete emotional experience in under thirty minutes. Jenova Chen has described the core inspiration as the feeling of riding a gust of wind as a child—weightless, directionless, joyful. The team wanted to translate that physical sensation into a controller-driven interaction without any traditional input mapping.
A recurring technical challenge was the wind simulation. The team built a layered particle system where the petal responded to multiple overlapping wind fields rather than a single vector, giving the movement an organic, almost alive quality. Early prototypes felt mechanical; the breakthrough came when they added turbulence and drag so the petal would tumble and settle unpredictably, mimicking real petal physics.
The art direction leaned heavily on a limited palette that shifted with progression: cold greys and blues in the city giving way to warm golds and greens in the countryside. The team deliberately avoided any on-screen text, icons, or HUD elements, relying on color temperature, music dynamics, and the petal's speed to communicate state.
Flower's design philosophy—short, wordless, emotion-first, physics-as-narrative—carried directly into Journey (2012), where the same studio expanded the wind-and-sand mechanic into a full-length experience. The title remains a reference point for indie developers exploring non-verbal storytelling and tactile, body-based gameplay.
Did You Know?
- Flower was designed to be a complete experience in a single sitting of roughly 20–30 minutes, a deliberate contrast to the long-form structure of most PS3 titles at the time.
- The game contains no text, no menus with instructions, and no scoring system; all guidance is conveyed through wind physics, color shifts, and music dynamics.
- Flower was the first publicly released title from thatgamecompany, the studio that would go on to develop Journey and other emotion-focused experiences.
- The petal's movement is driven by a multi-layered wind-field simulation rather than a simple directional input, making each playthrough's trajectory subtly different.
More in Production & Legacy
Elsewhere in the Flower universe
Spotted an error? Know more?
This is a living reference — every entry is fact-audited, and reader corrections feed straight into our audit queue. Suggest an edit · See this site's audit record
