OneSummer · UX Journey Map · 2026

The Summer
They Remembered

How two very different parents — Derek, the exhausted single dad on a 30-minute lunch break, and Lisa, the spreadsheet-wielding power user — find, choose, and book camps without losing their minds.

D
Derek — 38, single dad, hourly worker, phone-first, 15 min to decide
L
Lisa — 40, 3 kids, 40-row spreadsheet, 8+ camps/year, power user
D
Derek
The Squeezed Parent
💼
38 years old. Warehouse shift supervisor. Hourly pay means no browsing on the clock.
👪
Single dad of Marcus, age 7. Primary caregiver. No co-parent to delegate research.
📱
Phone-only researcher. Browses on lunch breaks (30 min) or after Marcus is in bed (exhausted).
⏱
Defaults to Parks & Rec every year — not because it's best, but because it's the only thing he can find in 15 minutes. Forms take 45+ min each.
💰
Budget-conscious. Needs to see cost clearly upfront. Financial aid eligibility matters.
"I just want Marcus to have a great summer. I don't have time to figure out which forms go where — I just need something that works before my break ends."
L
Lisa
The Power Planner
👔
40 years old. Marketing director. Organized, research-driven, high standards.
👪
3 kids: Emma (6), Noah (9), Olivia (12). Each needs a different type of camp. Scheduling conflicts are a nightmare.
📊
Maintains a 40-row spreadsheet tracking camp names, dates, costs, registration links, deadlines, and confirmation numbers.
💻
Desktop-primary. Expects keyboard shortcuts, bulk actions, and data export. Will find workarounds if the tool doesn't fit.
📋
Fills the same insurance, allergy, and emergency contact fields 8+ times per year. Each camp has a different form.
"By February I'm already coordinating 8 camps across 3 kids and a shared custody schedule. The data entry alone takes a full weekend. There has to be a better way."
15min
Derek's entire research window before his break ends
8+
Camp applications Lisa submits each year, each with duplicate forms
1
Time a parent fills out their child's profile on OneSummer — ever
0
Forms to re-fill when applying to a second, third, or eighth camp

The Stakes

Before OneSummer — After OneSummer

Without OneSummer
✕
Derek Googles "summer camps near me" and gets a mix of ads, Yelp pages, and the Parks Dept website. He picks Parks because it's the only one with an obvious button. His lunch break is over.
✕
Lisa opens her spreadsheet. She visits 12 different camp websites over 3 evenings to compare dates, ages, and costs. Nothing is in one place.
✕
Every camp application demands the same information: child's full name, birth date, allergies, emergency contact, immunization records, doctor name, and a signed waiver — typed from scratch each time.
✕
Lisa manually tracks waitlist positions for 4 camps across different websites. She has to email each camp individually for status updates.
✕
Derek misses the early-bird discount for an art camp because the deadline was buried on page 3 of the camp's website. He finds out in June.
✕
Next year, both parents start from zero. Derek's back at Parks. Lisa rebuilds her spreadsheet.
→
With OneSummer
✓
Derek searches "summer camps near me" and OneSummer surfaces in results. He finds 12 verified camps within 5 miles, filtered by cost, dates available during his work schedule, and age. Done in 8 minutes.
✓
Lisa's visual calendar shows all 3 kids' camps side-by-side with overlap detection. She plans the full summer in one session. The spreadsheet retires.
✓
Profile Vault stores each child's data once. Every subsequent application pre-fills in seconds. Lisa applies to 8 camps in 18 minutes. Derek applies in under 5.
✓
Waitlist position is tracked automatically. A push notification tells Derek when a spot opens. No emails, no checking, no guessing.
✓
Deadline alerts surface 2 weeks in advance, directly in Derek's dashboard, with a one-tap "apply now" action. He never misses early-bird pricing again.
✓
Next year, both accounts are ready to go. Marcus's profile is one year older — updated with one tap. Lisa's calendar resets with camp suggestions based on last year's ratings.
1
Stage 1 of 7
Discovery
View Mockup → 01-discover.html
Derek's Entry Point
Lunch break, phone in hand, 29 minutes left
It's February. Derek opens Google on his phone during his break and types "summer camps near me." He gets ads, Yelp results, and the Parks Dept website. He's been here before. He knows Parks opens in March. He bookmarks it, again, and goes back to work.
1
Google search on mobile → ambiguous results
2
OneSummer appears in organic results with rich snippet: "Search 200+ camps in Austin with no signup"
3
Taps link → loads Discover screen. No login gate. Search is immediate.
Lisa's Entry Point
January planning, desktop, spreadsheet open in another tab
Lisa starts camp research in January. A friend in her parents' group mentions OneSummer. She searches it. The homepage promises a visual calendar and one-profile-for-all-camps. She creates an account immediately, already thinking about how to retire her spreadsheet.
1
Word-of-mouth referral from parent network
2
Lands on homepage → feature highlights visible above fold
3
Clicks "Create Account" immediately (doesn't need to browse first)
Pain Points Eliminated
No more dead-ends
✕
Google returns camps with no uniform data — no prices, no dates, no ages
→
✓
OneSummer shows structured data in search snippet before clicking
✕
Most camp discovery requires creating an account just to see results
→
✓
Full search available without login — Derek can validate in 8 minutes
Emotional State
Anxious → Cautiously Hopeful
Derek arrives stressed — he's been failing at this task for two years. The no-login search changes something. He doesn't have to commit. He can look without risk. That single design choice reduces his anxiety enough to actually engage with results.
OneSummer Design Principle
Zero friction before value
The Discover screen (01-discover.html) shows the search bar as the dominant element. No splash screen, no modal asking for email, no "tell us about your child" before results. Value first, account second. Derek doesn't create a profile until he's already seen something worth returning for.
2
Stage 2 of 7
Browse
View Mockup → 04-search-results.html
Derek on Mobile
Filter by what matters: cost, distance, age
Derek types "art camps" and his zip. Results show 14 camps. He immediately taps the filter icon. He sets max cost to $350/week, age 6–8, and date range to June 9–Aug 15. Results narrow to 6. He taps the first card. 11 minutes have passed. He sends the link to himself to revisit tonight.
1
Mobile filter panel slides up from bottom (thumb-friendly)
2
"Save search" prompt appears after filtering — Derek taps it
3
Saved without account (email capture only). Returns that evening.
Lisa on Desktop
Multi-child, multi-camp, parallel research
Lisa opens three browser tabs — one per child. She uses the "Research mode" toggle to save camps to a comparison tray without applying. She exports her comparison to CSV. She's effectively rebuilt her spreadsheet inside OneSummer, but now it's live and interactive.
1
Desktop sidebar shows active filters and saved count per child
2
"Compare" tray shows up to 4 camps side-by-side
3
Calendar overlay shows scheduling conflicts in real time
Pain Points Eliminated
Apples-to-apples comparison
✕
Each camp website uses different formats — no consistent pricing, date, or age data
→
✓
All camps normalized into the same card schema: cost/week, age range, session dates, spots remaining
✕
No way to check scheduling conflicts without a calendar open in another tab
→
✓
Camp cards show conflict badge if dates overlap with a saved camp
Emotional State
Hopeful → Engaged
Derek feels something unfamiliar: momentum. He's actually comparing camps, not just looking at one. The save-without-account feature is critical — he commits to returning. Lisa feels the spreadsheet starting to dissolve. She's moved from skepticism to evangelism by the end of this stage.
Screen Referenced
04-search-results + 05-camp-detail
Search results (04) handle the filtering and card layout. Camp detail (05-camp-detail.html) provides the individual deep-dive with photos, reviews, age/skill breakdown, and the "Save to Calendar" and "Start Application" CTAs. No dead-ends — every action leads somewhere useful.
3
Stage 3 of 7
Profile Vault
View Mockup → 03-profile.html
Derek's Vault Moment
"Fill this out once and never again."
After saving a camp, Derek is prompted to create an account and fill out Marcus's profile. OneSummer is explicit about why: "Fill this out once — we'll pre-fill every application from here on." Derek takes 9 minutes to complete Marcus's profile — name, DOB, allergies (peanuts), emergency contact, his mom's number. He uploads an insurance card photo. Done.
1
"Continue to save" triggers account creation (Google Sign-in or email)
2
Guided profile flow — one field group per screen (mobile-optimized)
3
Progress bar shows "4 of 5 groups complete — almost done"
4
Confirmation: "Marcus's vault is ready. Your next application takes under 2 minutes."
Lisa's Vault
Three children, one session
Lisa adds Emma, Noah, and Olivia. Each child gets their own profile. The platform auto-carries shared data (family address, insurance, primary emergency contact) to each new profile, so she only enters unique data per child. She realizes she just eliminated 40% of her annual data entry in one afternoon.
1
"Add another child" inherits shared family data
2
Document vault: upload insurance card, immunization record, photo once per child
3
Camp-specific supplemental questions flagged separately — not buried in the main profile
Pain Points Eliminated
The form problem, solved permanently
✕
Fill out the same 30-field form for every single camp, every single year
→
✓
Profile created once. Every application auto-fills. User reviews and taps "confirm".
✕
Documents (insurance, immunizations) re-uploaded per camp per year
→
✓
Vault stores documents. Camps receive them automatically on application submission.
Emotional State
Skeptical → Committed
This is the pivotal moment for Derek. He's been burned before — he's skeptical that any app will actually save him time. The explicit promise "fill once, pre-fill everywhere" is the hook. But the product must deliver on it at Stage 5 (Apply) or he churns permanently. The vault is a contract between OneSummer and the parent.
Data Architecture Note
Vault fields vs. camp-specific fields
The profile screen (03-profile.html) distinguishes between core vault data (always pre-filled), optional vault data (pre-filled when present), and camp-specific supplements (prompted at application time). This prevents the vault from becoming an overwhelming 60-field form while still covering 90% of any camp's requirements.
4
Stage 4 of 7
Calendar
View Mockup → 02-calendar.html
Derek's Calendar
Single child, visual clarity, no overlap anxiety
Marcus's calendar shows the 3 camps Derek has saved, laid out across June–August. The calendar shows his work schedule in gray (synced from a basic iCal link) so he can immediately see whether camp pickup times conflict. He drags one camp to a different week. An "apply now" button floats at the bottom of each camp block once he commits.
1
Default month view (familiar, low cognitive load)
2
Saved camps appear as color-coded blocks with status badge
3
Deadline badge pulses orange on camps with closing applications
Lisa's Calendar
Multi-child, collision detection, summer as a whole
Lisa's calendar has three swimlanes — one per child, color-coded. Overlap detection flags week of July 4th where all three kids have camps with no coverage gap. She adjusts Noah's camp selection. The calendar also shows school end/start dates pulled from the district's public calendar. Summer planning as project management.
1
Toggle between "per-child" and "family" views
2
Yellow conflict highlight when two camps overlap by child
3
"Apply all pending" bulk action triggers from calendar header
Pain Points Eliminated
The scheduling puzzle, made visible
✕
Lisa cross-references 8 camp PDFs against a shared family calendar to find conflicts
→
✓
Visual calendar with real-time conflict detection. All camps visible at once, per child.
✕
Derek can't visualize the summer without manually writing dates on a paper calendar
→
✓
Saved camps automatically appear on the calendar. No manual entry required.
Emotional State
Engaged → In Control
The calendar is where OneSummer shifts from "useful tool" to "command center." Derek has never seen his son's entire summer laid out like this. The feeling is unfamiliar: control. Lisa describes this screen as "the moment I stopped being a camp logistics coordinator and became a parent again."
Design Consideration
Calendar as the hub, not a feature
The calendar screen (02-calendar.html) must be reachable from every other screen. It is not a feature buried in settings — it is the primary workspace. All actions (save, apply, track) are accessible from within it. The calendar is the product's north star, the single place where both Derek and Lisa measure success.
5
Stage 5 of 7
Apply
View Mockup → 06-apply.html
Derek's Application
The vault delivers on its promise
Derek taps "Apply" on the Blue Ridge Art Camp card. The application screen opens. Marcus's full name, DOB, allergy information, emergency contact, and insurance details are already filled in. There are two camp-specific fields: "Does Marcus have previous art experience?" and a t-shirt size selector. Derek answers both. Total time: 3 minutes and 47 seconds. He submits from his phone while waiting for his coffee to brew.
1
Application screen opens pre-filled — vault data displayed in read-only review mode
2
Camp-specific fields rendered below vault review section
3
Payment: sliding scale visible if financial aid applied for; one-tap Apple Pay / Google Pay
4
Confirmation: "Application submitted. You'll hear back by March 15."
Lisa's Bulk Application
8 camps, 18 minutes total
Lisa uses the "Apply all pending" action from the calendar view. A review queue opens showing 8 applications, each pre-filled from the relevant child's vault. She steps through each one, reviews the camp-specific fields, and submits. Camp 4 (STEM Explorers) has a new "learning accommodation" field — she flags it for later rather than blocking the rest. All other 7 are submitted in sequence.
1
Bulk review queue: one application per screen, prev/next navigation
2
"Flag for later" on any field without blocking rest of queue
3
Payment queue: grouped by child, single checkout where possible
Pain Points Eliminated
From 45 minutes to under 5
✕
Each camp application: 30–60 minutes of form filling from scratch
→
✓
Vault pre-fills 90% of fields. Application time: 2–5 minutes per camp.
✕
Separate payment flows across 8+ camp websites (each with their own portal)
→
✓
Unified payment flow with Apple Pay / Google Pay. Saved cards. Single receipt.
Emotional State
Hopeful → Relieved → Delighted
This is the payoff moment. The vault promise made at Stage 3 is delivered here. Derek submits his first application in under 4 minutes and sits for a moment, genuinely surprised. For Lisa, the bulk flow completing 8 applications in 18 minutes — versus her previous full-weekend effort — produces a kind of incredulous delight. These are the moments that drive word-of-mouth referrals.
Screen Referenced
06-apply.html
The application screen must show the vault pre-fill visually — users need to see that their data was remembered. Showing fields in a distinct "from your vault" state (read-only with edit option) reinforces the product's core value prop rather than making it invisible. Trust is built by making the magic visible.
6
Stage 6 of 7
Summer
View Mockup → 07-dashboard.html
Derek During Summer
Waitlists resolved without manual tracking
Derek applied to 3 camps. Camp 1 confirmed immediately. Camp 2 put Marcus on a waitlist (position 4). Camp 3 confirmed 2 weeks later. A push notification arrives on a Tuesday morning: "A spot opened at Pinecrest Science Camp — Marcus is next on the waitlist. Accept by Friday." Derek taps Accept on his phone during his commute. Done.
1
Dashboard shows all camps with status: Confirmed / Waitlisted / Pending
2
Waitlist position tracked automatically — no checking required
3
Push notification when spot opens with 48–72 hr accept window
4
One-tap accept from notification → payment if not pre-authorized
Lisa During Summer
Logistics, dropoff reminders, and mid-summer adds
The dashboard becomes Lisa's ops center once camp season starts. It surfaces dropoff/pickup times and addresses each Sunday evening. She adds a last-minute tennis clinic for Noah in mid-July (found via in-app search) and applies in 3 minutes using his existing profile. She leaves star ratings for completed camps — feeding data for next year's recommendations.
1
Weekly summary card: "This week for Noah: STEM Camp, Mon–Fri, 8am–3pm, 412 Oak St."
2
Mid-summer add: search → save → apply in under 5 min (vault still intact)
3
Post-camp: 5-star rating + notes per child. Feeds next year's shortlist.
Pain Points Eliminated
Summer managed, not survived
✕
Check each camp website individually to track waitlist status
→
✓
Unified dashboard shows all statuses. Push notification when waitlist moves.
✕
Scramble for dropoff address and start time on first day of camp
→
✓
Weekly digest with all logistics sent Sunday evening. One tap to add to calendar app.
Emotional State
Confirmed → Calm → Confident
The anxiety that dominated the beginning of the journey — will Marcus have a good summer? will everything work out? — resolves here. Derek has a full summer planned, confirmed, and visible on his phone. He's no longer reacting to chaos. Lisa's "command center" metaphor becomes reality. Both parents arrive at summer feeling like they've actually done it right.
Screen Referenced
07-dashboard.html
The dashboard (07) is the post-application home base. It shifts from "discovery mode" to "management mode" after applications are submitted. The primary view changes: instead of "find and save," it's "track and prepare." The calendar remains visible but the focus moves to confirmed camps and upcoming logistics rather than exploration.
7
Stage 7 of 7
Return
View Mockup → 07-dashboard.html
△
Next year, they come back.
Both Derek and Lisa open OneSummer the following January and find the product still knows them. Marcus's profile is there, still accurate. Lisa's three kids have updated ages auto-calculated. Last year's camps have ratings they left. The platform surfaces recommendations based on what their children loved.
0
Profile fields to re-enter
+1yr
Ages auto-updated
★ ★ ★
Prior camps rated and remembered
Jan
Return visit month, ahead of deadlines
Derek Returns
The second year is a different person
Derek opens OneSummer in January. His notification: "Camp planning season is starting — Marcus's profile is ready." He browses the same art camp he loved last year (Marcus came home covered in paint and happy). He also notices a soccer skills camp in his zip he didn't know about. He saves it. He applies to both before his lunch break ends. He doesn't check the Parks Department website at all.
Lisa Returns
The spreadsheet is gone for good
Lisa opens OneSummer and sees last year's camp ratings. STEM Explorers got 4 stars from Noah — it's already in her shortlist for this year. Olivia is now 13; the age filter has updated automatically and a new set of teen-appropriate camps appears. Emma aged into a swim level she didn't qualify for last summer. The platform noticed. Lisa plans the entire summer in a single two-hour Saturday session. She tells three parents about it that week.
Retention Flywheel
Why they never leave
✕
Every other tool starts from scratch each year — data doesn't persist or improve
→
✓
OneSummer compounds: each year the platform knows more about the family's preferences
✕
No record of which camps were great vs. mediocre
→
✓
Post-camp ratings feed a recommendation engine. Year 2 discovery is materially better than Year 1.
Emotional Arc — Full Resolution
Anxious → Delighted → Loyal
Derek arrived frustrated and time-starved. He leaves year two as an advocate — he's mentioned OneSummer to two co-workers with kids. Lisa arrived organized but exhausted. She now describes planning summer as "fun, actually." The emotional arc completes not with a transaction but with identity: these parents now think of themselves as OneSummer users.
Business Outcome
The network effect
Year 2 retention drives the product's growth engine. Derek's two referrals have the same profile: time-poor, phone-first, single-parent or dual-income households with limited research bandwidth. Lisa's referrals are power users who will add 8+ camps to the platform. Both cohorts are high-value. The product's defensibility is the vault — the longer a parent uses OneSummer, the more irreplaceable it becomes.
Emotional Arc Across 7 Stages
Composite sentiment score — 1 (frustrated) to 10 (delighted). Both personas plotted.
Delighted Relieved Neutral Anxious Anxious Hopeful Committed In Control Relieved Calm Loyal
1. Discovery 2. Browse 3. Vault 4. Calendar 5. Apply 6. Summer 7. Return
Derek — single dad, phone-first, high-stakes emotional journey
Lisa — power user, starts higher, peaks at Apply, stays high

Summary

All 7 Stages at a Glance

Stage Derek's Path Lisa's Path Derek's Emotion Lisa's Emotion Key Pain Eliminated Mockup
01
Discovery
 Google on phone, lunch break. Finds OneSummer via organic search. No login required to see results. Word-of-mouth referral. Lands on homepage, creates account immediately. Anxious Curious Forced account creation before browsing. No-login search removes the biggest entry barrier for time-poor parents. 01-discover.html
02
Browse
 Mobile filter panel. Saves search without account. Returns that evening. Desktop compare tray. Multi-child tabs. Conflict detection. CSV export. Hopeful Engaged Inconsistent camp data across 12 websites. OneSummer normalizes all camps into a single, comparable schema. 04-search-results.html
03
Profile Vault
 9 minutes to set up Marcus's profile. Explicit promise: fill once, pre-fill everywhere. 3 children added in one session. Shared family data auto-carried to each child profile. Committed Relieved Re-entering identical data for every application. Vault stores it once — insurance, allergies, emergency contacts, documents. 03-profile.html
04
Calendar
 Single-child month view. Work schedule synced. Deadline badges visible. 3-child swimlanes. Collision detection. School calendar integration. "Apply all" from calendar. In Control In Control Manual conflict checking across paper calendars and PDFs. Visual calendar with real-time overlap detection. 02-calendar.html
05
Apply
 3:47 total time. Vault pre-fills 90% of fields. 2 camp-specific answers. Apple Pay. 8 applications in 18 minutes. Bulk review queue. Flag-for-later on edge cases. Grouped payment. Delighted Delighted 45–60 min per camp application. Now 2–5 min with vault pre-fill. This is the product's defining moment. 06-apply.html
06
Summer
 Waitlist notification accepted from phone commute. Dashboard shows all confirmed camps. Weekly logistics digest. Mid-season add in 3 min. Post-camp ratings submitted. Calm Confident Manual waitlist checking across multiple websites. Scattered logistics info. Automatic tracking + Sunday digest. 07-dashboard.html
07
Return
 Opens in January. Profile intact. Applies before lunch break ends. Never checks Parks Dept. Ratings from last year feed recommendations. Ages auto-updated. Full summer planned in one session. Loyal Advocate Starting from zero every year. OneSummer compounds: Year 2 is materially better than Year 1. Network effects follow. 07-dashboard.html

Screen-to-Screen Flow

How the 7 Mockups Connect

🔍
SCREEN 01
Discover
Stage 1 · Discovery
Derek's first screen
📍
SCREEN 04
Search Results
Stage 2 · Browse
Filter + compare
🏖
SCREEN 05
Camp Detail
Stage 2 · Browse
Save or apply
🔒
SCREEN 03
Profile Vault
Stage 3 · Vault
Fill once, use everywhere
📅
SCREEN 02
Calendar
Stage 4 · Plan
Visual summer plan
✅
SCREEN 06
Apply
Stage 5 · Apply
Vault pre-fills everything
🌞
SCREEN 07
Dashboard
Stage 6–7 · Summer + Return
Track, manage, return next year
↻
Stage 7 Return Loop: Dashboard → Search Results (with year-over-year recommendations pre-populated) → Calendar (reset for new year, ages updated) → Apply (vault intact, zero re-entry). The loop shortens each year as the platform learns more about each family.