One deck of cards, and each one closes with a tap

Common questions

I planted mint yesterday and it told me to harvest it. What?

**Fixed on 24 August 2026, and the reason it happened is worth knowing, because it explains a whole family of odd answers.** Some plants come back every year — mint, sage, chives, lemon balm, rhubarb, a raspberry cane. For those, what we know is the shape of a normal year: leaves from spring, cutting through summer, dying back in autumn. That is a description of an **established** plant, and it is genuinely useful for one. It is nonsense for a plant you put in yesterday. The app was reading the established plant''s year and applying it to a seedling — so a mint planted in June landed in the middle of "cutting season" and got told to go and cut it. **What it does now is ask how long the plant has actually been in the ground.** We hold, for most crops, how many days from planting to something worth picking. Until a new plant has had those days, the harvest job is held back. From its second year on, the normal-year description is about your plant and we use it. **Two things we deliberately did not do.** We did not write down that mint takes a year to become cuttable. It does not — you can cut mint the summer you plant it, just not the day after. Recording a false year to silence a wrong message would have made the database lie to fix a screen. And if you have told us the fruit is sizing or the plant is ready, **you win.** Our day count is a catalog figure for a good season; you are looking at the actual plant. Answering the question always beats our arithmetic. **Still not perfect:** a handful of crops have no day count in our records yet — mint, rosemary, lemongrass, mulberry, raspberry and strawberry — so those can still do it. We are sourcing them, and the last two kinds need different numbers: a raspberry genuinely takes a year or two to bear, while a mint just needs a few weeks. **Three more crops joined that fix: lavender, sweet potato and tarragon.** These count their picking season from the day the plant goes out rather than from a seed, and for those three we have no date for that step at all — so the app was falling back on when the step usually happens in your area. Sweet potato is the clearest one: our figure of 90 to 120 days is right, but hung on a borrowed date it could land on any day of the year, including tomorrow. **The number was correct and the calendar was somebody else’s.** Now the app asks first whether your plant has actually been in the ground that long.

It kept asking whether something had come up, months after the plant was finished.

**Changed again on 23 August 2026, and this is the version that reaches every plant.** The first fix, in August, stopped the question two weeks after the plant's whole season closed. That worked for a bean and reached nothing else: it counted days from the day you sowed, while more than a third of our crops have their stages worked out from your frost dates instead. Two different clocks, so the stop never arrived. **We measured 55 crops still being asked whether they had sprouted three years after planting** — every fruit tree, every berry, asparagus, rhubarb, garlic. **The question now stops when the plant is visibly past it, on the plant's own calendar rather than on a day count.** Three things end it: the app telling you to pick something, every window that plant has being behind it, or the sprouting checkpoint itself running out — the same point the overdue warning stops, because *should you have seen this by now* and *have you seen it* are the same question from two ends. **And a crop we hold no sprouting figure for is not asked at all now.** Garlic, potatoes, sweet potatoes, mint, horseradish and 29 others have no sourced answer to *when should this show*, so the question was one we could ask and never read. Your plant's own page has always stayed quiet about those; the daily list now agrees with it. **A plant still inside its window is asked exactly as before**, including one that is running late — that is the moment we know least about it, and going quiet then would be the wrong way round. **Nothing you recorded is affected**; this only stops a question.

It asked whether my seed had come up on the day I sowed it.

**Fixed on 17 August 2026, and it was asking a question that could not have a yes.** Broccoli sown at 9:35 in the evening got "Any sign of the broccoli yet?" nineteen minutes later, with "a quick look at the row settles it" — in the dark, on bare soil. Radish and basil did the same thing. What makes it worse is that the app already knew better: the plant's own page said "First sprouts in 5–10 days", and the explanation behind the question itself quoted the same window. It held the right number, used it to decide when to STOP asking, and ignored it when deciding when to start. The question now waits until the first day a yes is actually possible for that crop — the early end of its sprouting window, not the late end, because plenty of seeds come up at the fast end and waiting for the slow one would miss them. A crop we have no sprouting window for is not held back at all: not knowing when something sprouts is not a reason to assume it sprouts instantly.

It kept asking whether my radish had come up, when the radish was ready to pull.

**Fixed on 17 August 2026.** While the app is waiting to hear that a seed came up, it holds back anything that talks about parts of the plant — including picking it. For most crops the point where it gives up waiting and assumes the plant is there comes well before anything is ready. **For a radish it did not:** ready in about three weeks, assumed up at four, so there was a week where it would not tell you to pull a radish that was sitting there. Now the waiting stops as soon as your own sowing date says the crop is pickable. **Some plants work differently and still wait** — sage and anise hyssop have picking seasons worked out from your local frost rather than from the day you sowed, and a season being open tells us about the year rather than about your seed.

Two jobs on my list say exactly the same thing. Which plant is which?

**The plant is in the job itself now, from 23 August 2026 — not in a line under it.** The first go at this, in August, put the plant's name on a third line beneath the job. That was better than nothing and it was still the wrong size: measured on a phone, the job read at 16px and the name underneath at 12.8px, with the bed smaller again at 9.9px. **The largest words on the row were the ones every row shared, and the only part that told you which plant it was about was the smallest text on the screen.** Two watering rows still opened with the same seven words. So the job says it: *Feel the soil where you sowed the carrot*, *Feel the soil in the tomato pot*. Where one job covers two crops in the same bed it names both, and past two it names two and counts the rest — watering a whole bed is still one trip and one job. **The bed is still there, underneath, and it is no longer the thing you have to read to tell two rows apart.**

It rained overnight. Will it still ask me to water?

**No, not after real rain — from 25 August 2026.** Before that it would, and it was wrong to: the app had the forecast on the screen and never once looked at it when deciding whether a plant needed water. Rain is now counted as a watering, because that is what it is. About four tenths of an inch in a day is enough, and a few smaller days running together add up the same way — three days of drizzle really does soak a bed. Below that it stays on the list, because a shower that darkens the surface has not reached the roots, and telling you a dry plant is fine is the one mistake worth avoiding here. **It knows how long the rain lasts, because that part was already right.** A pot dries out in a day and a mulched bed holds a week, and the app already worked in those terms — rain simply goes in as the last watering and everything downstream follows. **Anything under cover is left alone:** a greenhouse bed or a tray on a windowsill got none of that rain, so its job stays exactly where it was. **And if you watered anyway, your own record wins.** Logging a watering this morning always beats rain from last night.

The watering job used to explain itself at length every time. Where did that go?

**Behind a line reading "How to check", from 23 August 2026.** A plant's page gave you the whole lesson on every visit — how far to push a finger in, what half an inch of soil is doing, why a hard jet of water moves seed about, how often to look. Ninety-seven words, on a job that comes round every two or three days from May to September. It is all still there and none of it was cut. The page now shows the job and the two answers — **Still damp** and **Watered it** — and everything else is one tap away under *How to check*. **The first time you meet a crop you want the lesson; the fortieth time you want the two buttons.** Opening it once does not mean you never see it again either: it is a fold, so it is there whenever you want to look.

I am halfway through my jobs and I only want to do one of them. Do I have to tap through the rest?

**No — and from 24 August 2026 the way out finally looks like one.** Working through your jobs one at a time, the small *1/7* at the top opens the whole list: every job with its plant and its bed, so you can jump straight to the one you came outside for. **It always did that, and nothing said so.** It had no border, no background and no underline, and it was the same muted color as the label next to it — and a fraction is exactly the shape that reads as a readout rather than a button. It was also 23 pixels wide, against the 44 we hold ourselves to for anything you tap. **There were really two buttons up there doing the same job**, the progress bar and the number, and only the bar had a name — so if you use a screen reader it announced the same door twice, once as *see all of today's jobs* and once as *1 slash 7*. They are one control now: the whole strip is pressable, a chevron says it opens something, and it announces itself as *Step 1 of 7. See all 7 jobs for today.*

Can I tick something off without opening it?

Yes — today's jobs are listed on the home screen, each with its own button, so a job you have already done takes one tap and no screens. **If there is anything left to fill in, it appears right there** rather than sending you somewhere: log that you watered and the how-much question opens on the same screen. The only jobs that move you are the ones where the moving IS the job — a photograph of a leaf, or letting us send you an alarm — and those buttons say what they will do rather than a bare word like Open. **Everything you tap can be undone** from the same line. And the list is ordered by what cannot wait: a tray that has to come in tonight sits at the top with a mark, because that is the one job where being late costs you the plant.

What is the difference between app tasks and garden tasks?

**Garden tasks are things you do outside** — water, prune, pick, stake. They are time-sensitive, they depend on the weather, and they come round again. **App tasks are things you tell us** — which variety you planted, what kind of space a bed is, your ZIP code. They take a moment, they are done once, and they are what makes every garden task accurate. **App tasks sit above garden tasks** because they feed them: with no ZIP, every date underneath is your zone's average rather than your garden's. Once they are finished they disappear until there is something new to sharpen.

Why is the setup list above my jobs for the day?

Because it feeds them. **A garden with no ZIP code gets the typical dates for your zone, so every deadline underneath is an average wearing a date's clothes** — fixing what the app knows about you outranks working through what it worked out. It is only above your jobs because it shrinks: once there is one thing left it is a single line, not a checklist, so it cannot push the morning's work off the screen. Finish it and it disappears until the next round, which is about accuracy rather than basics — which variety, and what kind of space each bed is.

How do I get to my week without waiting for a link to appear?

There is a **Today / This week** switch at the top of both screens now, so you can flip between them whenever you like. Before this, the week had exactly one way in — a line on Today saying how many jobs were left — which meant **the moment you cleared everything, the screen became unreachable.** You had earned the right to look at your week and the way in disappeared. They are two views of the same question at different ranges, so they sit side by side rather than one hiding behind the other.

The home screen changed. Where did everything go?

It is one screen now instead of four and a bit, and **nothing was deleted — everything moved somewhere it makes more sense.** The big number used to be everything you had to do this month; it is now just today, with the actual job named under it. The rest of the week is one line you can tap. **The season charts, the will-not-ripen warning, the tree jobs and the pollination note all moved to your week screen** — tap the week line to reach them — because they are things to look at rather than things to do this morning, and they were sitting above the one thing you opened the app for. **Your plants moved to the Garden tab**, which already listed every one of them grouped by bed. The setup checklist stayed put, because that is what tells you what the app still needs from you.

A frost job used to just say "cover plants when frost is forecast". Why does it name a temperature now?

Because we had the number and were not showing it. From 8 August 2026, sixteen crops say the actual temperature — cover the beans when nights head toward 32°F — so you can check it against tonight's forecast instead of guessing what counts as cold. Some crops still get the plain sentence, and that is deliberate: where the figure we hold does not answer the question the job is asking, the job stays general rather than becoming confidently wrong. An orange tree was the case that proved it. The only figure we had for one was the temperature it is still fine at, not the temperature that hurts it, so "cover it at 20°F" would have told you to wait for a night the tree does not mind — the app said nothing instead, and then we went and found the right number rather than leaving it at that. The same care applies to numbers that only hold while a tree is in blossom: those say so, so nobody goes out to cover a bare apple tree in November.

Why is a job I never set showing up on my list?

Because the app worked it out from the plant. It knows what you planted and when, so it knows roughly where that plant is in its year and what usually comes next. Those are suggestions and they sit below anything you asked for yourself. If one is wrong for your garden, closing it teaches it nothing yet. It costs you a tap. Nothing dies over it.

My tomato is still covered in fruit and the app went quiet on it. Why?

**It should not any more, as of 17 August 2026.** Every plant stage has a typical end date, and when the picking window passed, nothing took over — so a tomato you were still eating from every other day got "nothing scheduled right now" for about 54 days. Cucumbers went quiet for 88, summer squash and leaf lettuce for 83, pole beans for 48. There is now a standing state for exactly that: the window has closed, the plant is still producing, keep picking on the rhythm the crop already has — every two to four days for a tomato. It runs until the first frost in **your** garden, because for a tender plant that is the real end, rather than a date we would have had to make up. 25 crops get it. **Not every plant qualifies, and that is the point.** Some crops you pick over and over; some you pull once and they are done. A tomato keeps cropping. A radish does not, and telling you to keep picking a radish for three months would be a worse answer than saying nothing. Which leaves one gap we have not closed and are not going to pretend we have: a radish that finished six weeks ago still gets silence, when what it deserves is "this one is done — pull it, or sow something else". That is a separate job.

I added something I am planting next month and it gave me jobs for it today. Why?

**That was a bug and it is fixed.** You can add a plant with a date in the future and plan a bed before you dig it, and the app was treating that plan as a plant already in the ground — telling you to water it, watch it for pests, and on plenty of crops to harvest it. It would even tell you the seeds had never come up, on a packet still sitting on your counter. Nothing appears now until the day you said you were planting. On that day everything starts properly, including the reminder to go and plant it. **The one thing kept on purpose is the chart:** you still see the whole year ahead for something you are only planning, because that is the useful part of adding it early. And a tray of seedlings you are hardening off still asks to be watered every day of the two weeks before it goes out — a planting-out date in the future means the plant has not been moved yet, not that it does not exist.

I asked for a reminder. Where did it go?

Into the list, as an ordinary card. There used to be a separate section for things you asked for and it is gone. A reminder is a job, so it queues with the rest, counts on the door, and closes with the same tap as everything else. That includes reminders you create by talking — say you want to prune the apple in December and it becomes a card in December.

Why can I not see a reminder I set for next month?

It only comes onto the daily list within about a week of being due. A job six weeks out is not what you opened this screen to find out. It is still there — it lives on that plant's own page until its week comes round. One rough edge worth knowing: a reminder with no plant attached and no near date will not surface anywhere until it comes within the week.

What order are the cards in?

Overdue first, then due today, then the rest of the week. Inside that, anything you asked for outranks anything the app suggested. Two things jump the whole queue: frost coming tonight, and seedlings still outside that need bringing in. Those two are there because they are the only ones where waiting until tomorrow costs you the plant.

A card wants a photo. What happens if I back out?

The job stays done. It is marked complete the moment you tap it, before the camera opens, so changing your mind about the photo cannot un-finish something you actually did. Take the picture later from the plant's page if you want it.

I have garlic in the ground. Why did the app act like winter was empty?

Because until 7 August 2026 it could not count past New Year. A plant's stages are stored as day numbers, and garlic that goes in during October is still going the following July — day 544 of a year that only has 365. Every check said that day had not arrived, so the app showed a countdown to the planting you had already done: on 15 January the row read "Taking root in 237 days". Thirty-three of our 151 crops were affected and garlic was the worst — invisible for 227 days of the year, including the whole of its harvest. It now works out which year the plant is in before it compares anything, so garlic reads "Dormant" in January, "Growing leaves" in April and "Ready to pick" in July.

What does the app have to say in the middle of winter?

Whatever is actually in the ground. Garlic sitting through the cold, a cover crop holding a bed, rosemary or sage or thyme going dormant, straw to put round the strawberries, and the winter jobs on fruit — the bare-wood prune on apple, peach, currant, gooseberry and kiwi, and peach's dormant spray, which can only be done while the tree has no leaves on it. **And from 23 August 2026, one thing that does not need anything planted at all: what to start indoors.** If your beds are empty in February the app used to say nothing, which is the wrong answer at the exact moment the year starts — *it's time to start tomato, pepper and cabbage indoors, plus 30 more*, counted from your own last frost rather than a national date. It names the crops and says when the first window closes. It shows up on a screen that would otherwise be blank, and **it goes quiet the rest of the year**, from about the middle of May until the new year. There is nothing to sow in August, and inventing something to fill the space would be worse than the silence.

The app called my plant something I would never call it.

**Fixed on 24 August 2026.** Every plant in our records is filed under one name, and it is often not the one you would use. We file zucchini under *Summer Squash*, collard greens under *Collard*, green beans under *Bush Bean* — so somebody who typed **Zucchini** was being asked about a summer squash. **It was worst on the one sentence where it mattered most.** The question asking whether something has come up exists to sound like it knows your garden, and it was the sentence reading from our records instead of from you. Now every card about one of your plants uses your word for it: the question, the running-late note, the reminder to sow it, and the one asking whether it ever went in. **If you picked a variety, that is your word too.** A plant recorded as Beet · Chioggia is asked about as *Chioggia*. And if you never gave it a name of its own, it still uses ours — a question with no plant in it would be worse than one with the wrong name. **One place still says the crop, on purpose:** the pest card. That is one row covering every bed growing the same thing, so there is no single plant of yours it could honestly name.

The same question about my seed was on my list twice, in two different wordings.

**Fixed on 24 August 2026, and it was two cards that could not see each other.** Two separate parts of the app had each grown a way to ask whether a seed had come up — written months apart, sitting 250 lines apart, neither one aware the other existed. On the crops where both fired you got *“Any sign of the broccoli yet?”* and *“Any broccoli sprouts?”* on the same screen, about the same bed, on the same morning. **We swept every crop at every age and it happened on 147 of them.** There is one question now, with one set of words and one place it comes from. **Nothing about when it arrives has changed**: it still starts on the first day a yes is possible for that crop, and still stops when the plant is visibly past it. **What made this worth doing carefully rather than quickly** is that deleting one of the two was the obvious fix and the wrong one. They did not overlap everywhere — on most crops the older card covered the early weeks and the newer one only spoke up late, so removing either would have left a silence. Measured on broccoli, deleting the older one on its own would have meant nothing asking between day five and day twenty-four, on a plant whose own page says first sprouts in five to ten days. The surviving card took over that window before the other one came out.

It asked me "Any bean sprouts?" — why is the app asking ME?

**Because we cannot see your bed and you can, and until 17 August 2026 we never asked.** Every plant carries a rough window for when the seed leaves should be up. **The question arrives on the first day a yes is possible** — day five for broccoli, not day twenty-five — because that is the stretch where looking is worth more than counting, and it stays until you answer. If the window closes and you still have not seen anything, the wording changes with the situation: it stops asking and starts saying, *“the broccoli should be up by now”*. A cold spring, deep sowing or old seed all push it later, and none of them are your fault. It asks once, and **it calls the plant what you call it** — if you typed Zucchini it asks about your zucchini, not about a summer squash. **Answering yes stops it asking about that plant, for good.** It is not a chore we invented; it is the app admitting the calendar has run out and you are the one holding the information. **Saying "not yet" logs nothing at all** — there is no such thing as a plant that failed to come up on schedule as far as we are concerned, and we are not going to record one on your behalf. **Some plants will never ask.** The question only exists where there is a yes-or-no thing to look at — seed leaves, flower buds, tiny fruit forming. Where the plant record is waiting on something like "growing fast", there is no answer you could give, so we do not put a question mark on a phrase and call it one.

I added a plant for today and it is asking me to plant it. Is that not obvious?

It is, and that is rather the point — it is the one job the app should never be silent about. **Until 17 August 2026 only three crops out of 152 ever offered it**, which was an accident rather than a decision: the reminder depended on the plant record happening to list "sow" as a care step on a stage that happened to be open that day, and almost none of them do. So somebody who added beans the night before, planning to sow them in the morning, opened the app standing over the bed and saw nothing about beans. **Now it comes from your own date instead.** You said today, so it is today's job, on every crop. Ticking it is also what starts that plant's clock — every date afterwards is counted from the day it actually went in rather than from an average, so this is the tap that makes the rest of the year about your plant.

Why is "say when you planted them" sitting above my watering, and why will it not go away?

**Because without it we cannot tell you much of anything about that plant — added 21 August 2026.** The planting date is the day every other date is counted from: when to expect it up, when it fruits, when it runs out of season. A plant with no date is given the jobs of one planted this morning, because that is the only thing left to assume. On a tree that means being told to stake it, mulch it and rub the suckers off something that has been in the ground for years. **It sits with the app tasks, not with the watering.** Those are two different kinds of job and they have been separate for a while: things you do in the garden with your hands, and things you tell the app so that everything else it says is about your garden rather than an average. The date is the second kind, and it goes above the first because it feeds it. **It does not have a Hide.** Everything else in that list does. This one stays because skipping it costs you something you cannot see happening — months of slightly wrong dates on a plant, which you would have no way to spot and no way to repair afterwards. The moment you answer it, it is gone for good. **And it never blocks you.** You can always add a plant without a date, from the chat or anywhere else. It just becomes a job afterwards instead of a wall in front of you.

I added something with a future date and it already has jobs. Is that right?

**No, and it stopped on 21 August 2026.** You can add a plant with a date in the future — that is deliberate, it lets you lay out a season before you dig anything. What should happen then is nothing: a plant that is not in the ground has no jobs, because there is no plant. **What actually happened was three cards.** A garlic dated three months out was asked *"any sign of the garlic yet?"* — about a seed still in its packet — and given a job to harvest it and a job to cure it. The part that stings is that the app already knew better: everything underneath had correctly worked out that the plant did not exist yet, in seven separate places. **The screen just never asked.** Now it does. A planting dated in the future shows nothing until its day arrives, and on the day it arrives you get the one job that matters: plant it. **Three things still show, on purpose.** Hardening off, because that whole routine happens in the two weeks *before* a seedling goes in the ground. Anything we are missing about the plan — where it will go, what date, what rootstock — because you can answer those from the sofa. And if you sowed something last week and have another sowing planned, we still will not tell you to sow more of it.

My garlic has no jobs at all, just a note about what garlic is usually doing. Why?

**Because the date you gave us says this plant is not on the calendar we would be reading from — corrected 21 August 2026.** A few crops are grown to a fixed time of year rather than to a clock that starts when you plant them. Garlic is the clearest one: it goes in around the first frost of autumn and its scapes come the following summer. So everything the app knows about garlic's year is pinned to your frost date, not to your planting date. That works perfectly for a garlic planted when garlic is planted. **It fell apart for one planted at the wrong time of year** — a garlic put in during May was asked, five days later, whether its scapes had emerged. The plant was fine. The question was about a different garlic, one planted eight months earlier, and nothing was checking. Now if your planting date is well outside the window that crop normally goes in, we stop giving you jobs for it and keep the general note instead — *garlic is usually scaping about now* is true about garlic, and *your garlic needs its scapes removed* would not be true about yours. Two weeks late still counts as on time; a whole season out does not. **Four crops are affected**: garlic, horseradish, cereal rye and hairy vetch. Everything else works from the date you gave us, so this never comes up.

I sowed tomato seed last week and it told me to harvest it. How?

**Because it was reading a calendar for a different tomato — stopped on 23 August 2026.** Most plants have two ways of starting: from seed in the ground, or raised indoors and set out later. Our records give the picking season for a tomato from the day it goes OUT, and a tomato you sowed straight into the bed never has that day. So the app quietly used the typical date for tomatoes in your area instead, and then said it about yours. In late August that typical season is wide open, so a seed sown on Tuesday was told to pick on Wednesday. **Now a date we borrowed from the season cannot give you a job.** The test is simple and it is the plant's own: if the season we borrowed had already opened before your seed went in, that season is not about your plant, and we say nothing about it. **Tomato, pepper, eggplant, tomatillo and ground cherry all stopped doing this.** **It changes nothing for a plant put in at a normal time.** We swept every crop, both ways of starting it, every age up to seven months: a plant sown or set out on its own usual date is not held back from a single harvest. That was the whole design problem — the obvious version of this fix silences a tomato you sowed in May for the rest of its life, and it is the tomato you are actually picking from. **And the season itself is still shown.** *Tomatoes around here are usually picked from mid-July* is true and stays on the chart. What has gone is the app turning that into an instruction about your plant.

The weather at the top changed. What am I looking at?

**Seven days instead of three, from 23 August 2026** — and three things it was holding back. Before, it was one gray line: tonight's low and the next three highs. **We already had the whole week cached** and were showing a fraction of it. Now each day gets a column: an icon, the high, the night's low under it, and the chance of rain. **Rain chance is the addition that matters most.** It is the number that decides whether you water, it is the commonest garden decision there is, and we were showing none of it. It only appears where it is worth a glance — under about 30% it is noise. **The hottest day of the week is tinted**, so you can find the day something will bolt or scorch without reading seven numbers and comparing them. A week with no real spike gets no mark at all. **And it disappears entirely if the forecast is more than twelve hours old.** That is deliberate. A weather row showing yesterday is worse than no weather row — especially for a frost that has already been and gone.

One of the nights is in purple. What does that mean?

**That night is forecast at or below freezing** — 32°F. It is the same number your first and last frost dates are worked out from, so it is not a threshold we picked for this row; it is the one the whole app already runs on. It is on the night, not the day, because that is when it happens and that is when a tray has to be inside. **Tonight still has its own card** if you have something that a frost would end — this is the rest of the week, which nothing was telling you about.

The picture when I tap a day looks different, and where did the sun go on rainy days?

**That picture is drawn on your phone rather than downloaded**, which is why it works with no signal and why it can move through the day instead of being one fixed image. **The sun climbs and sinks across it with the real hour**, so a glance tells you roughly where you are in the day without reading a clock. **Until 26 August 2026 it was not drawn at all on cloudy, rainy, snowy, stormy or foggy days.** Not hidden behind the cloud — absent. So on five of the eight kinds of day the picture quietly stopped telling you the time, which is the one thing it was best at. It now shows through the cloud as a bright patch in the right place, the way an overcast sky actually looks. **After dark the moon does the same**, in its real shape for tonight. **The weather itself is redrawn too.** The clouds were a row of identical lumps with a straight edge along the bottom, the rain was one mark repeated at one angle, and the snow was made of small squares. Clouds are one soft shape now with a shaded underside, rain varies in length and weight, snow is round, and fog — which was a flat gray rectangle — is layered banks of haze sitting thickest near the ground. **None of this changes a single number.** The temperatures, the rain chance and what we say about your plants are exactly what they were; only the drawing changed.

Can I see the weather hour by hour?

**Yes — tap any day in the row.** It opens underneath rather than taking you to another screen, so the week stays in front of you, and the same tap closes it again. **It leads with when, because when is the only thing an hourly view can tell you that the daily row cannot.** *Rain from 2pm* is what decides whether you water this morning; *coldest at 5am, 29°* is what decides whether covering at nine in the evening is enough. On an ordinary day it says nothing at all and just shows the hours — a panel that always has something to announce teaches you to stop reading it. **It covers about six and a half days**, which is how far ahead the weather service publishes by the hour. The seventh day in the row will tell you it has nothing yet rather than showing you an empty box.

Why is there no wind on the weather row?

**Because the forecast never gives it to us as a condition of its own.** We looked at what the National Weather Service actually writes — 51 different descriptions harvested from sixteen cities in four climates — and wind only ever turns up appended to something else, as *"and Breezy"* or *"and Windy"*. There is no day whose weather IS wind. So an icon for it could never appear. We would rather leave it out than ship a picture nothing can ever draw, which looks like coverage and is not. If wind earns a place later it will come off the wind speed, which is a number, rather than off a description that never mentions it. **Same reasoning for what else is missing.** No humidity, no pressure, no sunrise, no feels-like. Your phone does all of that better, and a row that only repeats your phone is not worth the space it takes on the screen you open first.

Do I have to clear the whole list?

No. There is no streak, no score, and nothing goes red at you for stopping halfway. Close what you did, leave the rest, and the ones that still matter will be there tomorrow. The list answers one question: what should I do this morning. It was never meant to be homework.

More on this

• Your week
• When nothing is wrong
• Asking your garden a question
• Frost alerts
• What shipped and when