BetterLife AI Coach

Bug fixes for chat auto-scrolling, keyboard dismissal, and improved button touch areas. BetterLife App Bug Fixes Walkthrough I have successfully resolved all the substantial flaws reported during the iOS app testing. Here is a detailed breakdown of the fixes and improvements made. 1. App State Persistence Bug Fixed The app was previously forgetting the user and showing the "Begin your journey" login screen after every app launch. Fix Applied: Removed the aggressive UserDefaults.standard.removeObject calls from the AppState initialization logic. The app will now correctly persist user profiles, active goals, coaching sessions, and streaks across launches and background states. 2. Text Input, Auto-Scroll, and Keyboard Improvements The chat interface had several interaction issues: the text didn't clear, the keyboard couldn't be dismissed, and the screen flickered while the AI replied. Fix Applied: Implemented @FocusState in the CoachView to gain programmatic control over the keyboard. Keyboard Dismissal: Tapping anywhere outside the text field now explicitly dismisses the keyboard, allowing the user to read the AI's reply clearly. When a message is sent, the text box clears immediately and the keyboard drops. Flickering Fixed: Removed the scrollToBottom() command from the onToken streaming loop. The aggressive auto-scrolling was causing the severe screen flickering. The view now naturally expands as the AI types, providing a buttery smooth experience. 3. Redesigned ADHD & CBT Buttons The tester noted the bright red and yellow buttons were "loud" and "intrusive". Fix Applied: Redesigned both buttons to be much more subtle. They now use a deep blue blSurface background with thin colored borders and colored icons. This significantly reduces their visual weight while keeping them accessible for users who have these features enabled. 4. Button Touch Targets Resolved The large "Begin your journey" button (and all other primary/secondary buttons in the app) only responded to clicks directly on the text, not the button's edges. Fix Applied: Refactored the underlying blPrimaryButton and blSecondaryButton design system components into native SwiftUI ButtonStyle structures (BLPrimaryButtonStyle and BLSecondaryButtonStyle). Result: The padding and background are now correctly applied inside the button's tappable area. You can now tap anywhere on the button (even the very edges) to trigger the action. This fix was deployed app-wide, resolving the issue on all screens simultaneously.