One Good Acre

A farming game about depth, not size

One Good Acre is a single-player farming game with a simple twist: the farm never turns into a sprawling empire.

You look after one small homestead with a cottage, vegetable beds, a well, an old apple tree, a shed, a compost heap and space for a few animals. Progress comes from learning how that place works and building a history with it.

The same tree can become a gathering place, a grafting project or a shelter for bees. A crop can be eaten, shared, cooked or saved for seed. Villagers remember what you chose, and the game keeps track of the small routines that make your version of the acre different from somebody else’s.

There is no perfect route and no pressure to make the farm endlessly bigger. The aim is to make one small place feel properly lived in.

What is in the game

• Crops that grow according to daylight, weather, season and soil condition.
• Seed saving, composting, watering and tools that improve through use.
• Four seasons, each with different daylight hours, crops and farm activity.
• A cottage kitchen for cooking meals from what you grow.
• An old apple tree, bee hive and chicken coop with their own routines and unlocks.
• Villagers who visit, trade and respond to earlier choices.
• A record of decisions, discoveries, relationships and seasonal rituals.
• Short real-time farm days designed to work well in brief sessions.

The first spring

The opening spring is built around a series of choices rather than a checklist of upgrades.

You choose which keepsake was left in the cottage, decide whether to preserve the wild edge of the first bed, work out what to do with the first harvest and choose how to restore a branch lost from the apple tree. Those decisions change later conversations, projects and the first spring supper.

Important moments wait for you rather than disappearing because the game was closed. The farm clock also stops at the next morning after a long absence, so coming back should feel welcoming rather than like returning to a disaster.

How I’m building it

The game is being built in Flutter from one shared codebase for iOS, Android and the web. The simulation and story state are written in Dart, with Drift handling local saves so the game continues to work offline.

I’m using AI coding tools throughout the project, but the interesting part is keeping the game coherent as it grows: making sure choices are remembered, saves remain safe, the interface works across different screen sizes, and all the small systems still feel like parts of the same place.

Current state

There is a working build with the core farming loop, seasons, crops, cooking, villagers, bees, hens, the farm record and the first-spring story. I’m still refining the game, testing it on real devices and working towards a public playable release.

Screenshots