Nonna's Figs: The App Tracking Assunta's Road to the Blue Ribbon

Every September in Ceglie Messapica, the sagra judges taste jams in small white cups and hand out ribbons. Nonna Assunta has placed second twice. Her sister-in-law Zia has won twice. The margin between them, judged last year at 82 versus 88, is six points and roughly a question of how much sugar goes into a pan and how long it sits on the flame.

The frustrating part is not that Assunta cooks badly. It is that she cooks by feel, and feel does not keep records. A batch she called Ferragosto last August came out nearly perfect, but by the following June she could not reconstruct it. Was it 700 grams of sugar or 750? Did she squeeze one lemon or two? Did she take the pot off after 40 minutes or 45? The answer was somewhere in her head, mixed up with a dozen other Sundays. So she built a small app to hold it for her.

A notebook that speaks her world

The app opens already full. There is no blank screen asking Assunta to set up an account or define a project. She sees her own batches listed by name, each one tied to the tree it came from: Ceppa Vecchia, the old trunk near the wall, whose figs run darker and sweeter; the younger tree by the gate, whose fruit sets firmer. The names are hers. The data is hers from the first tap.

Each log entry captures exactly what matters for a preserve: the sugar weight in grams per kilogram of fruit, the number of lemons squeezed in, the boil time in minutes, and the cold-saucer result, the old test where a spoonful dropped onto a chilled plate tells you whether the jam will set or stay liquid. Nothing more. The form does not ask about pectin brands or altitude or moon phases. It records what Assunta actually controls every Sunday morning.

The two lines she is chasing

Scroll down past the batch list and you reach the chart. It plots every recorded score across the season as a line climbing, or dipping, Sunday by Sunday. Two horizontal lines cut across it: one at 82, her own best sagra score from last September; one at 88, Zia's ribbon. The goal is visible. The gap is visible. If a batch drops below 82, that Sunday's choices made things worse. If a batch crosses 88, she has something worth repeating in competition.

What makes this useful rather than decorative is that the scoring is not arbitrary. The app compares each batch against those two benchmarks and tells Assunta directly where she stands: below her personal best, between the two scores, or above the ribbon. Over a season of ten or twelve Sundays, that chart becomes a story of what worked and what did not, written in the language of sugar ratios and boil times rather than vague impressions.

Try scrolling through the chart in the demo above. The batches Assunta logged earlier in the season cluster around her old score. A couple of Sundays where she pushed the sugar higher and held the boil a few minutes longer start to pull the line upward. The pattern is subtle but it is there, and it would have been invisible without the record.

What the numbers reveal about fig preserves

Preserving is more variable than it looks from the outside. The difference between 640 grams of sugar per kilogram of figs and 800 grams is not just sweetness: it affects how quickly the mixture reaches setting temperature, how long the finished jam will keep, and how the judges at a sagra read its texture on the spoon. A 40-minute boil and a 45-minute boil produce visibly different results when you drop a spoonful onto a cold saucer.

Assunta knows this from years of practice. What the app gives her is the ability to link those variables to outcomes across more than one Sunday. Before, each batch lived only in her memory, which is lossy and blends details together. Now a batch called Ferragosto has a permanent record: 740 g sugar, 1 lemon, 42 minutes, saucer set firm after 3 seconds. If it scores well, she can repeat it exactly. If it scores poorly despite tasting right to her, she has something to bring to the judges and ask about.

Built for a kitchen, not a data center

The app works offline. This matters more than it sounds. Assunta's kitchen on a Sunday morning is not a place for troubleshooting a wifi connection while a pot boils. She picks figs, weighs fruit, starts cooking, and at some point sits down to log what she did. The app is there when she needs it, with or without a signal.

Nothing is ever lost between sessions. She can log a batch mid-morning, close the phone, come back after lunch to check the saucer result, and add it then. The chart updates. The scoring updates. The record is permanent. After a full season of Sundays, she will have twelve or fifteen data points that no one can take away from her, and she can walk into September's sagra knowing exactly which version of her recipe she wants to reproduce.

The demo embedded above is a live copy of the app. Tap through a batch entry, adjust the sugar or the boil time, and watch the score change relative to the two target lines. The interaction is the point: this is what Assunta sees every Sunday, not a mockup.

One idea, one Sunday morning, one real tool

This app did not come from a product team. It came from a specific problem that one person described clearly: she makes fig preserves, she enters competitions, she loses to her sister-in-law by six points, and she has no record of what she did differently in the batches that came closest to winning. That description was enough to build something real and usable.

The tool is small by design. It does not try to be a general recipe manager or a social sharing platform for jam-makers. It does exactly what Assunta needs and nothing else: log batches, score them against two targets, show the season's progress. If she wins the ribbon in September, it will be because she had better data than the year before. That is the only claim the app makes, and it is a reasonable one.