Rainbow’s End Provisioning — Support

It turns a meal plan into a grocery list. You plan a voyage — dates, crew, which meals are aboard and which ashore — and fill its calendar with meals from the galley’s library (or your own). Every meal carries per-person quantities, so the app multiplies by the crew aboard each day, adds it all up, subtracts what’s already in the lockers, and rounds up to the packs a store actually sells. You adjust the result, shop from it on your phone, or print it for the crew. It works entirely offline.

Yes, until version 1.0.5. The new name says what the app is for: provisioning a boat. Nothing else changed — the same app and the same icon, and your voyages, meals and lists come through the update untouched. The Galley tab keeps its name; it is the galley aboard, where the meals and the stores live.

A voyage, on the Voyage tab: a name, the first day, how many days, the crew aboard, and the provisioning pattern. Then the Calendar tab shows one card per day with breakfast, lunch, dinner, and snacks to plan. The List tab is live from the first meal you plan.

Full plans every meal of every day aboard. Split is the charter pattern: every breakfast and lunch aboard, up to three dinners aboard — first night, midweek, last night — and the rest ashore, the way a charter week actually runs. Custom starts like full and leaves every meal to you. Whatever you choose, every meal stays editable on the calendar.

Tap the meal. Aboard means the galley cooks it and its ingredients join the list. Ashore means a restaurant does — add a note (“Foxy’s, Jost Van Dyke”) and it prints on the calendar. Off is for a travel day’s trimmed end: you boarded after breakfast, or you’ll be gone before dinner.

Each aboard meal says for itself whether it’s eaten at anchor or underway — a charter often sails through breakfast and drops the hook for lunch. A meal underway steers suggestions to one-pot meals a cook can manage in a seaway. A dinner underway means a passage running into the night, so night-watch snacks come along: bars, jerky, hot chocolate, soup cups. And any meal underway adds a 20% margin to the water check, because passages wait out weather.

No. A suggestion is the galley’s own library, filtered and ordered: the right meal type, the appetite you asked for (light or hearty), one-pot when the meal is underway, and fresh first — meals whose ingredients spoil soonest are offered early in the voyage, cans and dry goods late. It never repeats a meal within a voyage until it has to. Ask again and you get the next candidate; choose from the galley to pick by hand.

How long a meal’s freshest ingredient keeps aboard: days 1–3 for berries, lettuce, tomatoes, fresh chicken; a week for citrus, peppers, apples, deli meat; weeks for carrots, onions, potatoes, hard cheese; keeps for cans and dry goods. Plan a days-1-to-3 salad for day 6 and the calendar warns you before it becomes compost in a locker. The windows are estimates from cruising practice — an icebox in the tropics keeps different promises from a fridge on shore power.

On the Voyage tab, under Food allergies aboard, mark which of the common allergens are aboard — shellfish, fish, peanuts, tree nuts, dairy, eggs, wheat, soy, sesame — and, if you like, whose. Every meal in the library carries the allergens of its ingredients, so any planned meal that conflicts is flagged on the calendar with who can’t eat it and an alternative of the same type, and suggestions steer around crew allergens when they can. Nothing is removed from the menu: the rest of the crew still eats it, and the cook plates something else for the one who can’t. The flags print on the calendar too.

It shouldn’t, once you tell it who drinks. Beverage rates are per drinker per day, and the Voyage tab’s Drinks aboard card asks how many of the crew drink each one — some want beer, some wine, some neither. Until you say, beer and wine assume half the crew; water and coffee assume everyone. And think about how many drinks will be drunk ashore — on a charter, most are.

By a cruiser’s rule of thumb rather than a rate: a crew of eight rarely gets through more than a bottle in a week aboard, so you switch a spirit on, say how many share the bottle, and the app plans about a bottle per eight sharers a week. A fortnight at sea with eight sharing gets two.

Whether the crew will drink from them. On a charter the tanks serve showers and dishes and everyone drinks bottled water — leave it on Showers and dishes only and bottled water stays on the grocery list, a liter per person per day. On a passage the crew drinks from the tanks: choose Drinking water too, give the tank capacity and the gallons each person will draw per day for drinking, showers, and dishes (2.5 is a comfortable starting point; a gallon is the bare minimum), and the calendar checks the plan against the tanks — and says plainly when it doesn’t fit.

The Galley tab’s Already aboard list: an item and how much, or Have plenty for the spice rack and the like. Name the item the way the meals do (“Rice”, “Pasta”) and every list subtracts it — the line shows what’s aboard and buys only the shortfall, rounded up to a real pack. It stays between voyages; the lockers don’t empty when you come home.

For the ones that need telling. Every dinner, and every breakfast or lunch that is more than assembly, carries the cooking: a few numbered lines written for a two-burner galley — one pot where it can be, what to prep at the dock, what needs calm and a grill. Open a meal on the Galley tab to read them; they also print under the calendar, once per planned meal with the days it’s served, so the crew’s copy carries the how as well as the what. Sandwiches and cereal carry none — you know. It is not a recipe app: no photos, no scaling, no importing; just the galley remembering how the dinner goes.

Yes — Add your own meal on the Galley tab opens a recipe card: the meal, its appetite, whether a cook can manage it underway, each ingredient with its per-person amount, unit, pack size, category, where it stows, and how long it keeps, and the cooking if you want to write it down, one step per line. Saved, it joins the library permanently, wearing a “Yours” pill, and gets suggested like any other.

Each meal’s per-person amount, times the crew aboard that day, summed across every day the meal is planned, merged with the same ingredient from other meals, minus what’s already aboard, then rounded up to the packs a store sells. That last step is why the list buys 18 eggs when the math says 16: eggs come by the dozen and the eighteen, and 18 is the smallest that covers. Snacks add a modest daily allowance per person; beverages add per drinker per day. The spreadsheet export shows every step — needed, already aboard, to buy.

Yes — the list is a starting point and the shopper has the last word. Adjust the list makes every quantity editable, lets you strike a line the crew won’t use (it moves to a “Struck” section with Restore), and lets you add an item the meals never knew about, like ice. Adjusted lines wear a pill so the override stays visible; adjustments stay with the voyage and flow into the cart, the PDF, and the spreadsheet. Undo all adjustments returns the list to the app’s numbers.

Tap a line to put it in the cart; it drops to the bottom, struck through, and the count at the top keeps score. Empty the cart resets for the next store. The “Check aboard before you shop” section is the invisible half of provisioning — cooking oil, paper towels, the propane check — with a box to tick once you’ve looked.

Yes. On the List tab, under Split the shopping, set how many are shopping and give each a name if you like. The list divides into one share per shopper, each a run of neighboring aisles — produce for one, meats and dairy for the next — so nobody walks the store twice. Small aisles are combined into one share; an aisle too big for one share is divided between two shoppers and marked part 1 and part 2. The shares come out even by count of items, give or take a few, and an aisle is divided only when keeping it whole would leave the shares uneven.

Send hands a shopper their share as a message through the share sheet, for crew on their own phones; Print the list gives each shopper a page of their own; the spreadsheet gains a Shopper column. The split follows the list, so adjusting the list divides it again — but checking items off never moves them from one shopper to another. Set the shoppers back to one for a single list.

Print the list and Print the calendar make PDFs — a page the crew can hold — and hand them to the share sheet: AirDrop, Files, Mail, or a printer. List as a spreadsheet and Calendar as a spreadsheet make files that open in Excel, Numbers, or Google Sheets, with the columns cruisers use: item, category, stowage, needed, already aboard, to buy. Nothing leaves the phone any other way.

Voyages save forever. Duplicate on any saved voyage makes a copy — meals, drinks, allergies, adjustments and all — to rename and re-date. Delete asks twice.

Everything lives in the app’s own storage on your device. There is no account and no server of ours, and with iCloud sync off (its factory setting) the app makes no network requests at all. The only things that leave are the files you print or export and the shopping shares you send, yourself, through the share sheet, each time you tap the button — and, if you switch it on, the copy iCloud sync keeps in your own iCloud (below), readable only by your Apple ID. The privacy policy says the same thing at greater length. Deleting the app deletes the data on that device; a synced copy stays in your iCloud until you remove it.

Yes — through your own iCloud, and only if you ask. At the foot of the Voyage tab, under iCloud sync, switch on Sync your voyages across your devices on each device. Every device signed into the same Apple ID then keeps the same galley: your voyages with every meal planned, the cart and your adjustments to the list, what’s already aboard, your beverage rates, and your own meals. Edits push a few seconds after you make them and arrive when the other device next opens the app (or on Sync now). The copy lives in your iCloud’s private database — no account with us, no server of ours, and we cannot read it. The privacy policy said it would describe any online feature plainly before it shipped; its iCloud sync section is that description.

The newer edit keeps that whole voyage. Sync merges voyage by voyage: whichever device changed a voyage most recently carries it entirely — its meals, its cart, its adjustments — and does not stitch two devices’ edits together meal by meal. In practice the window is small because devices sync within seconds of an edit; the habit that makes it a non-issue is finishing on one device before picking up the other. Different voyages never collide, and a voyage deleted on one device stays deleted — unless the other edited it afterward, in which case the edit wins and it’s back. What’s already aboard and the beverage rates are kept the same way, each as a whole; your own meals merge one by one.

They’re siblings from the same shop and share the family look, but each stands alone. Anchoring sizes and manages your ground tackle; Manifest keeps the book of the boat; Provisioning feeds the crew.