Homesteading and food preservation · Food, batch logging, and pantry tracking

How Brandon Whiteleather Launched Freeze Dry Buddy in 28 Days

We took Brandon Whiteleather's freeze-drying workflow and turned it into Freeze Dry Buddy — live on the App Store 28 days after our first conversation, then on Android, and still getting updates from us. On July 20, Google Play publicly showed 1K+ installs and a 4.8 rating across 61 reviews; Apple showed a 4.6 across 32 ratings, with a fresh production release from the day before.

Written by Weston Bell-GeddesFacts checked 2026-07-20
Freeze Dry Buddy app by Brandon Whiteleather
Independent proofApple App Store listing

The public record · 2026-07-20

From first conversation to App Store in 28 days

Everything below is checkable: both public store listings and one customer's review history. We don't publish private numbers — no revenue, no conversion data — so what's here is only what anyone can verify themselves.

28 days

First call to iOS launch

28 days from our first conversation with Brandon on April 24 to Apple's May 22 release date.

Our dated record + Apple App Store metadata
1K+

Android installs (public range)

Google Play publicly showed the 1K+ install range on July 20.

Google Play public listing
4.8

Google Play rating

A 4.8 across 61 public reviews on July 20.

Google Play public listing
4.6

Apple rating

A 4.6 across 32 public ratings on July 20, rounded to one decimal place.

Apple public app metadata

The problem that became the app

A freeze-dry batch finishes days after it starts. By then the settings, duration, prep, weight, and outcome are scattered across notebooks and memory. Owners needed one reliable place to keep all of it.

Brandon's description of the problem, condensed.

What we shipped, and when

  1. Brandon told us the problem

    A freeze-dryer owner comes back days after starting a batch and can't reconstruct the settings, duration, prep, weight, or outcome. That moment became the product.

    Our dated record
  2. Freeze Dry Buddy shipped on iOS

    Apple's public metadata records the first release — 28 calendar days after that conversation.

    Apple App Store metadata
  3. A customer complaint became a fix

    A reviewer reported wrong pantry labels and no way to correct a finished batch. Two days later, the same reviewer publicly thanked the team and said the app was working better.

    Google Play public review history
  4. Fresh releases on both stores

    Google Play showed a July 18 update, and Apple's metadata showed version 26.7.19, released July 19.

    Google Play and Apple public metadata

From user feedback to a shipped fix

What we heard

On July 15, a Google Play reviewer reported that four named batches all showed up in the pantry as strawberries — and that there was no way to correct a completed batch.

What we did

We treated the report as accurate and built the fix into the next release.

Shipped

The next update fixed the pantry labels, made completed batches editable, carried final weights through correctly, and made support easier to reach.

Public result

On July 17, the same reviewer updated their public review: 'Thank you for the fixes. Now working better.'

See the review for yourself on Google Play

What the evidence does not prove

  • We don't publish revenue, conversion data, retention data, or internal product analytics here — those stay private.
  • Store ratings and review counts are real, but they aren't proof of long-term retention or product-market fit.
  • Google Play's 1K+ is a range, not an exact download count — that's all Google shows publicly.
  • The 28-day figure runs from our first conversation with Brandon to Apple's public release date. It tells you how fast we shipped, not how the work happened behind the scenes.

The opportunity

A freeze-dry run takes days, and the details live wherever they landed — a notebook, a masking-tape label, a half-remembered video. Brandon's followers had his knowledge; they just couldn't get at it while standing in front of the machine wondering what worked last time.

The app we built

Freeze Dry Buddy puts all of it in one place: log a run as it happens, pull up what worked before, start from Brandon's own guidance, and watch the pantry fill up batch by batch.

What the app does

  • Batch logging that captures the settings, prep, weight, and outcome of every run
  • Brandon's own recipes and guidance to start from, plus reusable settings of your own
  • A searchable batch history, so you can compare runs and repeat what worked
  • A visual pantry that grows as batches finish — a record of what you've actually put away

What Built by Foundry handled

  • Turned Brandon's freeze-drying routine into a product his audience could actually use mid-run
  • Designed the batch log, recipes, history, and pantry around the way a real run unfolds over days
  • Built and shipped the app — iOS first, 28 days after our first conversation, then Android
  • Keep running it after launch: reading reviews, shipping fixes, and keeping both store listings current

Public evidence

Everything below is a fact you can check without taking our word for it. We deliberately leave out private revenue claims and projections — the links go to public pages that show the app is real, live, and genuinely this creator’s.

  • Apple's byline on the listing reads 'By White Pepper Farms.'
  • The App Store names BUILT BY FOUNDRY, INC. as the developer of record.
  • Apple's own description says the app was built with White Pepper Farms.
  • Google Play publicly shows 1K+ Android installs, along with dated creator responses to customer reviews.
  • Both stores showed fresh production releases in the two days before this evidence review.

Sources and verification

How we wrote this

We went back to our dated records and checked them against the public Apple and Google listings and the public review history on 2026-07-20. Anything you’d have to take our word for stays out: the creator’s finances, conversion and retention numbers, user-level analytics, and our internal production notes. Where the proof stops, we say so on the page itself, not in fine print. If we got something wrong, ask us to correct it — anytime.