dog-training-plan

byMOHIT Chawla

Yes — combining your **original business strategy** with the uploaded **CALM WALKS master prompt**, the UI should revolve around one core loop: **Dog assessment → personalized plan → real-world walk → weekly check-in → adaptive re-plan.** The uploaded spec specifically makes the **weekly re-plan + “what changed and why” diff** the product moat. ## CALM WALKS — Complete UI Plan ### 1. Landing Page **Hero** > **A training plan built for your dog's triggers. Rewritten every week.** Subtext: > Tell us what your dog reacts to, where it happens, and what your walks actually look like. **CTA:** `Build My Plan — $59` Immediately underneath: > **$59. One payment. Not a subscription.** Then: **How it works** `01` Tell us about your dog `02` Get your personalized plan `03` Report your week → your plan adapts The uploaded prompt specifically calls for this three-step structure and immediate price transparency. --- # 2. Intake UI Use a **5-step progress flow**, with autosave. ### Step 1 — Your Dog **“Let's start with your dog.”** Fields: * Name * Age * Breed / mix * Size * Walks per day Bottom: `← Back`  `Continue →` Progress: `●────○────○────○────○` --- ### Step 2 — Triggers **“What sets them off?”** Selectable chips: `Other dogs` `People` `Bikes` `Skateboards` `Joggers` `Cars` `Mail carriers` `Other` Then a large text field: > **Tell us exactly what happens.** Placeholder: > “The off-leash Chihuahua near Maple Street…” This free-text detail is important because the plan is supposed to use the owner's **actual triggers**, not generic categories. --- ### Step 3 — The Street This should be one of the most visually distinctive screens. **“Where does it happen?”** Fields: **Your usual route** > Describe the streets you normally walk. **Problem spots** > “The corner near the park…” **Usual trigger distance** `5m ─────●──────── 20m` Then: ### Your walking environment Cards: `Quiet residential` `Busy street` `Apartment complex` `Park` `Mixed` CTA: `Save my route →` --- # 3. History Screen ### “What have you already tried?” Cards: **Trainer** `$400–$600` **Behaviorist** `$600–$1,200+` **Training app** `Used one` **Online course** `Tried one` Then: > **What worked? What didn't?** Large text box. This reinforces the positioning that the owner isn't being introduced to dog training for the first time—they're looking for something more specific. --- # 4. Safety Gate This needs a completely different visual treatment. Use the **clay/terracotta safety color**, not the normal amber CTA. ### “One important question.” > **Has your dog ever bitten someone and broken skin?** `Yes` `No` Also ask about: * bite to a person * repeated snapping with contact * serious aggression history If flagged: ## The Right Call Is A Vet Behaviorist No checkout. No sales pitch. No upsell. Instead: > A veterinary behaviorist can assess the situation properly and help you build a safe plan. CTA: `Email My Intake Summary` The uploaded specification explicitly says the safety route ends the funnel and should make no sales attempt. --- # 5. Checkout This should feel extremely clean. ## Choose your plan ### $59 **Personalized 4-Week Plan** ✓ Personalized intake ✓ Trigger-specific exercises ✓ Your walking environment ✓ 4-week training plan ✓ Progress criteria **$59 — One payment** --- ### $79 **Plan + Weekly Re-Plans** ✓ Everything in $59 ✓ Weekly check-ins ✓ Updated training plan ✓ “What changed & why” ✓ New trigger adaptations **$79 — One payment** Under the buttons: > **No subscription. No auto-renewal. No cancellation maze.** The $79 version should be framed as a **one-time upgrade**, not recurring billing. --- # 6. Plan Generation Screen After payment: ### Building your plan… Use real progress states rather than a fake infinite spinner. ```text ✓ Reading your dog's triggers ✓ Mapping your walking environment ● Building your first week ○ Creating progression rules ``` Then: > **Your plan is ready.** CTA: `See My Plan →` --- # 7. Main Dashboard This becomes the user's home screen. ### Good evening, Sarah. **Milo's Week 2** `██████░░░░ 60%` ### Today's focus > Stay below Milo's reaction threshold when passing dogs. **Today's exercises** #### 01 — Calm observation 🐕 Other dogs **Starting distance:** 20 ft **Duration:** 5 min **Goal:** Milo notices the dog and can still take a treat. `Start Exercise →` --- #### 02 — Check-in walk **Duration:** 15 min `Start Walk →` --- ### This week's progress `3 / 5 walks logged` `View Progress →` --- # 8. Exercise Detail UI When they tap an exercise: ## Calm observation **Trigger** Other dogs **Start distance** 20 ft **Duration** 5 minutes ### Success looks like > Milo notices the dog, remains able to think/eat, and returns attention to you. ### If a trigger suddenly appears > Increase distance calmly. Don't force the interaction. Resume only when Milo is back below threshold. ### Why this works A short explanation tied to the user's actual intake. CTA: `Start Exercise` The plan schema requires trigger, distance, duration, success criteria, progression rule, unexpected-trigger handling, and a personalized “why.” --- # 9. Walk Check-In This is where the app starts collecting the data needed for adaptation. ## How did the walk go? ### Other dogs `Better` `Same` `Worse` **Closest comfortable distance** `20 ft` ### Did anything unexpected happen? ☐ Loose dog ☐ Construction ☐ Crowded street ☐ New trigger ☐ Nothing unexpected ### Biggest win? Text field: > “Milo looked at the Labrador and took the treat.” CTA: `Save Walk` --- # 10. Weekly Review This should feel rewarding without becoming a gamified streak app. ## Your Week ### 5 walks logged ### 3 wins > “Looked at the lab, took the treat.” > “Passed the corner without lunging.” > “Recovered faster after seeing a bike.” **No streaks. No guilt.** The source specifically calls for a timestamped Win Log without streaks or pressure mechanics. --- # 11. THE MOAT — Weekly Re-Plan This should be one of the **best-designed screens in the entire app.** ## Your next plan is ready. ### What changed? **01 — Starting distance changed** `20 ft → 15 ft` > Milo stayed calm at 20 ft during three walks. **02 — New environment added** > We're introducing the quieter side of the park. **03 — Progression slowed** > Construction increased reactions this week, so we're keeping difficulty steady. Then: ## Why we changed it > Based on your Week 2 reports, Milo is consistently recovering faster around dogs but still struggles when the distance closes quickly. CTA: **View Week 3 →** The spec explicitly defines this **“What changed and why” diff** as the moat and requires plan versions to remain preserved rather than overwritten. --- # 12. $59 User Upgrade UI If someone bought the $59 plan: ## Want your plan to keep adapting? > Your current 4-week plan is ready. Weekly re-plans let us adjust it based on what actually happens during your walks. ### Unlock weekly re-plans **$20 one-time upgrade** > You already paid $59. You'll only pay the $20 difference. `Upgrade for $20 →` And importantly: > **Still one payment. Nothing renews.** The source explicitly specifies this one-time $20 upgrade and says the offer should not use dark patterns. --- # 13. Win Log Navigation: `Home | Plan | Walks | Wins | Account` Win screen: ## Wins `Today` > Milo saw a dog and stayed under threshold. `Yesterday` > Calm walk past the park entrance. `Sept 28` > Recovered quickly after a surprise bike. Each item: **What happened → Date → Trigger** No points. No XP. No streak counter. --- # 14. Plan History This is another important differentiator. ## Plan History **Week 3 — Current** `View` **Week 2** `View` **Week 1** `View` Then: > **Plans aren't overwritten.** This allows the owner to see how their plan evolved over time. --- # 15. Account Keep it extremely simple. ### Account **Milo** Dog profile **Your plan** $79 — Paid **Receipt** View receipt **Your data** `Export my data` `Delete account` **Important:** > Your plan is yours. One payment. Nothing renews. There should deliberately be **no “Manage subscription” section**, because there is no subscription. --- # Overall UI Architecture ```text CALM WALKS │ ├── Landing │ ├── Intake │ ├── Dog │ ├── Triggers │ ├── Street │ ├── History │ └── Safety │ └── Vet Behaviorist │ ├── Checkout │ ├── $59 │ └── $79 │ ├── Dashboard │ ├── Today's Focus │ ├── Exercises │ ├── Walk Check-in │ └── Weekly Progress │ ├── Plan │ ├── Week 1 │ ├── Week 2 │ ├── Week 3 │ └── Week 4 │ ├── Re-Plan │ ├── Weekly Review │ └── What Changed & Why │ ├── Wins │ ├── Plan History │ └── Account ├── Receipt ├── Export Data └── Delete Account ``` ## Visual Direction Use the **Maple Street** system from your file: * Background: warm cream `#FAF7F0` * Primary: forest `#1F4A31` * CTA: amber `#E29A38` * Safety: muted clay `#C25E4C` * Cards: cream `#F4EFE5` * Borders: sage `#A7C4B0` * Headlines: Fraunces/Lora * UI/body: Inter * Rounded 12–16px * Lots of whitespace * Soft borders instead of heavy shadows * Mobile-first, thumb-friendly These exact design tokens and interaction rules are specified in the uploaded master prompt. ### The most important UX principle Don't make it feel like: **“Here is another dog-training content app.”** Make it feel like: > **“I told this thing exactly what happens with my dog, and now it actually remembers and adapts.”** That is the product. Everything in the UI should reinforce that loop: **MY DOG → MY STREET → MY WALK → MY DATA → MY NEXT PLAN.**