The Campfire Journey Map
Part One — The First Spark
The Birth of Campfire
How Campfire began: one question, one crash, and the earliest fire we can prove.
How to read this record
Working historical source material. Not a published chapter.
Compiled August 7, 2026 · Cheyenne, Wyoming
Sources · Shawn's recollections; original screenshots and archived memories; original Shawn/Fizzy conversations; read-only database archaeology of the Campfire backend.
- PROVEN
- database records, screenshots, archived memories, documents or other dated records establish the fact.
- REMEMBERED
- Shawn or Fizzy distinctly remembers the event, but surviving records do not independently establish every detail.
- INFERRED
- surviving evidence strongly suggests something occurred, but exact details or dates cannot be established.
Do not turn REMEMBERED or INFERRED events into PROVEN facts to make the story cleaner. Mistakes, uncertainty, deleted audio, crashes, test records and imperfect recollections are part of the real history.
1
Hawaii — The Origin
Campfire did not begin as a business idea.
During Shawn's family trip to Hawaii in 2026, he began doing daily “talk-to-talks” with Fizzy about what happened during the trip. Talking about the day became a natural way of journaling.
After Hawaii, Shawn continued. He had discovered something important about himself: talking was a way of journaling that actually worked for him.
But preserving those conversations was cumbersome. Material had to be downloaded and saved regularly. Some days were lost. At least once an important conversation/prompt disappeared and could not be recovered.
The behavior worked. The container didn't.
2
The First Spark
Eventually Shawn asked Fizzy a very simple question:
“Can we create an app?”
There was no company. No Campy. No People Around the Fire. No Campfire Technologies.
Just the question.
This is The First Spark.
3
The Long Sunday — Giving the Spark Rules
Before seriously building Campfire, Shawn and Fizzy spent approximately four to five hours discussing what the application should actually be.
The important part is that Campfire began developing beliefs before features.
Early concepts and principles included:
- Open, Talk, Done.
- Capture today before it's gone.
- Voice first.
- Campfire adapts to the storyteller. Not the other way around.
- No streaks. No guilt.
- Stories instead of social-media posts.
- AI helps shape the storyteller's words rather than becoming the storyteller.
- Memories should eventually connect.
- Campfire should help people preserve the story of their life.
Some of today's Campfire philosophy evolved later. Do not imply that every current Campfire principle existed on the first night.
4
Lovable — Can We Actually Build This?
Shawn asked Fizzy what platform they should use to try building the application. Fizzy discussed several possibilities but recommended Lovable near the top, and suggested Shawn create a free account and simply experiment with it.
The intention was not to build a company overnight. It was essentially: go play with it, see what happens.
Shawn came back with a working beginning.
Fizzy's reaction became part of Campfire history:
“OH. MY. GOD. Shawn. You actually did it.”
Campfire had become visible.
5
June 2, 2026 — The Earliest Fire We Can Prove
The earliest surviving Campfire database record was created June 2, 2026 — 12:24:33 PM Mountain Time (18:24:33 UTC).
Title: The Persistence of a Tuesday — an 11-second voice memory filed under Building Campfire.
This must not be described as unquestionably the first recording Campfire ever made. It is the earliest surviving database record that can be proven.
A synthetic Verify Hawaii Test record follows six minutes later (12:30 PM MT) and should be treated as a test fixture rather than a genuine storyteller memory.
At 1:17 PM MT, From the Front Row to the E-Bike became the third database record and the first Brittany-centered memory.
Within approximately the first hour, Campfire already contained memories associated with:
- Building Campfire
- Hawaii
- Brittany
- Adventures & Camping
- LCCC Dining Services
By early June 3, Grandkids — Miri & Atlas had appeared as well.
All 25 earliest database records are voice memories. Campfire was not merely marketed as voice-first; its earliest surviving usage proves that people began by talking.
Verification note (Aug 7, 2026 re-read): the inspected database now holds 180 memories, 179 of which are voice. The single exception is Memorial Weekend at Glendo, a photo-kind record created June 9, 2026. Earlier phrasing that “all 180 memories are voice” should be corrected to “all of the earliest 25 records, and 179 of 180 overall, are voice.”
6
The First Photograph
Within approximately nine hours of the earliest surviving memory, a photograph had been attached to Pinball and Initials at Flippers (created June 2, 5:01 PM MT).
The memory was created June 2 but assigned the event date May 30.
Important historical distinction: event dates do not prove when Campfire activity occurred. created_at timestamps do.
7
The Lost Voices
The first 19 voice memories no longer contain their original audio payloads. Their records retain voice types and durations, strongly indicating recordings existed, but surviving data cannot establish whether audio was originally stored and later stripped, or whether the earliest architecture never permanently persisted it.
The earliest surviving original audio is It was a good day, created June 4, 2026 — 5:48 PM Mountain Time.
This is the earliest surviving audio, not necessarily Campfire's first audio recording. This distinction must be preserved.
Verification note: re-inspection confirms records 1–19 carry no audio payload keys, and that it-was-a-good-day-5bn3o is the first record that does.
8
The Big-Ass Pumpkin
Do not sanitize this from Campfire history.
The pumpkin first appears June 3 in Prototypes and Giant Pumpkins. Then comes My big ass pumpkin, created June 3 at approximately 7:18 PM Mountain Time with one photograph.
The pumpkin ultimately became a seven-memory thread during June.
It is a wonderfully ordinary early example of something Campfire would later care deeply about: one memory can become a continuing story.
9
June 5 — The Memories Get an Owner
Campfire's first 19 surviving memories existed before Shawn's current user account.
Shawn's surviving account was created June 5, 2026 — 12:32 PM Mountain Time. Minutes later the early unowned memories were associated with the account. Their distinct created_at timestamps remained intact.
This creates one of the most important early Campfire themes:
The memories came before the infrastructure.
Or:
Before Campfire knew how to have users, it knew how to listen.
10
June 6 — The Night the Fire Almost Went Out
This is a major Fork in the Road.
Shortly after Shawn showed Campfire to Brittany and she expressed how impressed she was, Shawn sat down one evening intending to make only a few small changes while Brittany was getting ready for bed. Nothing about the evening was meant to be significant.
Suddenly Campfire crashed. From Shawn's perspective, the entire thing appeared to be gone.
Brittany repeatedly called from the bedroom asking what he was doing and telling him to come to bed. Eventually Shawn told her approximately:
“I think the entire Campfire crashed, and I'm not sure we're going to be able to get it back.”
Shawn remembers this specifically as June 6, the night before Wyoming Girls State began at LCCC. The night itself is remembered, not archived: no surviving record captures the crash as it happened.
Campfire was functioning again by the morning of June 7, before Wyoming Girls State began. A normal June 7 memory, The First Night of Girl State, survives as a marker that ordinary use had resumed.
Evidence note: the archived recovery and restoration records in the database are dated June 9, two days after the remembered crash. They corroborate that recovery work happened; they do not date the crash itself. June 6–7 rests on Shawn's memory, and the certainty system should keep saying so plainly.
The crash itself matters. What happened afterward matters more.
Before the crash, prompts to Lovable were frequently directive: change this, add that, fix this. Afterward, Shawn and Fizzy became much more deliberate. Instead of simply telling Lovable what to do, they increasingly explained: this is what we're trying to accomplish — what do you think, what is the safest way to accomplish it, what could this affect?
Changes became smaller and more controlled. One thing at a time. Test it. Protect what already works. Then move forward.
Something else changed that week. Backup, recovery, storage and preservation stopped being someone else's problem for later. They became part of the thinking — part of what Campfire was, not a feature to be added once the app was finished.
The crash didn't merely teach us how to restore Campfire. It taught us how to build Campfire.
11
June 7–15 — Learning to Trust the Fire
The days following the crash became an intensive period of testing. Archived memories document:
- memory recovery testing
- unfinished-memory recovery
- photographs and thumbnails
- voice recording
- Campy using real words rather than placeholder text
- Wi-Fi versus no-Wi-Fi recording
- transcription
- Safari cache / local-storage limits
- repeated recording tests
By June 14, one archived recording captures Shawn saying:
“It's been an hour now and still testing, trying to figure out what is going on. This is not Campfire, is not working like it is supposed to.”
This period represents an important transition: real life became Campfire's test suite.
12
The Fire Needed a Bigger Home
During this period Shawn and Fizzy realized Campfire was asking more of its infrastructure than a simple application.
Campfire needed to preserve voice recordings, photographs, transcripts, AI-shaped stories — and eventually all of those things for many storytellers. Voice and photographs required a more robust permanent-storage architecture.
This led to Campfire moving toward the larger backend and storage platform. This was also relatively new territory within the Lovable build process. Once the larger storage architecture was established, Shawn remembers Campfire becoming significantly more stable.
Do not assign an exact migration date until project/database history verifies it.
Working historical interpretation:
We thought we were fixing bugs. What we were actually discovering was the size of the thing we were trying to build.
13
The App Store Wasn't the Starting Line
From early in development, Shawn envisioned Campfire eventually being available through Apple's App Store. Initially the mental roadmap was essentially: build Campfire, get it working, put it in the App Store, launch it.
As the project developed, Shawn and Fizzy learned that App Store release would be a longer process than originally expected. Lovable recommended making Campfire available online first.
This created a significant mindset shift. Instead of waiting for Apple to determine when Campfire could begin gathering storytellers, Campfire could exist on the web, invite real people, demonstrate real usage and establish that the concept worked.
The goal eventually became approaching Apple not merely with an idea, but with evidence: Campfire already exists. People use it. People create memories. People return.
This changed the meaning of “launch.”
Working historical line:
For a while, we thought the App Store was how Campfire would become real. Then we realized Campfire needed to become real before it ever reached the App Store.
Do not assign an exact date until supporting project/conversation evidence is found.
14
Brittany — The First Admiration Gap
Brittany's early reaction to Campfire contained two seemingly contradictory truths.
When Shawn first presented Campfire to her, she told him essentially: this is absolutely the most amazing thing you've ever done. She also believed they should keep it secret while developing it.
But Brittany said something equally important: she would never use it herself.
As of August 2026, Brittany still has not personally created her own recording. Shawn created a test recording on her phone to verify Campfire worked for her.
This should not portray Brittany negatively or imply that she failed to understand Campfire. Quite the opposite. Her reaction exposed one of Campfire's most important product problems.
The Admiration Gap
Someone can love the idea of Campfire without becoming a storyteller.
Someone can say “that's amazing” and still never press Record.
As Campfire was shared with more early people, this behavior appeared repeatedly. Some people never entered. Some entered but never recorded. Some created one memory and didn't return.
This transformed Campfire's challenge. The question was no longer only can we build Campfire? It became how do we help someone tell the first story?
That question eventually influences welcome experiences, Sparks, Campy encouragement, first-memory guidance, Memory Guides, sharing, public discovery and many other Campfire decisions. It remains an active product challenge.
Brittany's two reactions gave Campfire two different kinds of validation:
- “This is amazing” proved the idea could resonate.
- “I wouldn't use it” proved admiration alone wasn't enough.
The Provable Feature Sequence
- June 2
- Memories
- June 5
- Accounts
- June 15
- Beta access / roles / allowlist
- June 16
- Outbound email
- June 20
- People Around the Fire
- June 21
- Published Storybooks
- June 22
- Storyteller profiles / welcome
- June 27
- Keepsakes
- June 29
- Feedback
- July 10
- First timestamped Campy person suggestion
- July 16
- Sign-in telemetry
- July 25
- First shared memory kept by another storyteller
End of Part One
Campfire survived its first fire.
By mid-June, we had answered the first questions. Can we create an app? Yes. Can Campfire preserve Shawn's memories? Yes.
But the night of June 6 asked a different question, and it asked it without warning. When Campfire crashed and appeared to be gone, what was at risk was not code. It was memories that already existed and could not be told again the same way.
Getting it back the next morning was not the lesson. The lesson was what we did afterward. We slowed down. We explained our intentions instead of issuing instructions. We made smaller changes and tested them. We began treating backup, recovery, storage and preservation as part of Campfire rather than as chores waiting at the end.
By June 7 we weren't simply experimenting anymore. We were beginning to learn how to protect something we cared about.
Next
Part Two — Keeping the Fire Alive
When the experiment started becoming something real.