# User Feedback Log > Vibe Reader — Collected feedback from user testing sessions > Last Updated: 2026-02-06 --- ## Format Each feedback session follows this structure: - **User:** Anonymized identifier - **Date:** When feedback was collected - **Context:** Testing environment, device, session type - **Feedback Items:** Categorized observations and suggestions - **Action Items:** Linked to [[Feature_Backlog]] where applicable --- ## Session-001 **User:** User J **Date:** 2026-01-17 **Device:** Android (version not specified) **Session Type:** In-person observation + verbal feedback **Build Version:** Smart Capture v1 ### Context First external user test. User J tested the core capture flow including: - Starting a reading session - Using Smart Capture from lock screen - Defining words - Reviewing captures in Archive ### Feedback Items #### Usability Issues | # | Category | Observation | Severity | |---|----------|-------------|----------| | 1 | **UI/Legibility** | Font size in capture overlay prompts is too small; hard to read quickly | Medium | | 2 | **Flow/Friction** | Having to tap "Confirm" before defining a word adds unnecessary friction | High | | 3 | **Flow/Friction** | Definition screen requires manual "Done" tap; should auto-dismiss | Medium | | 4 | **Functionality** | No way to delete a mistakenly captured word or quote | High | | 5 | **Functionality** | Multi-word terms (phrases, concepts) always detected as quotes | Medium | #### Positive Observations | # | Observation | |---|-------------| | 1 | "The idea of capturing from lock screen is really cool" | | 2 | Smart Capture auto-detection (word vs quote) felt intuitive | | 3 | Archive metrics badges (5W \| 2Q) are helpful at a glance | | 4 | Resume book chips on start screen save time | #### Suggestions | # | Suggestion | Notes | |---|------------|-------| | 1 | Add timeout option for definition screen | User wanted to glance and return to reading | | 2 | Option to "define anyway" when phrase is detected | For terms like "cognitive dissonance" | | 3 | Consider haptic feedback on successful capture | Reinforces action without looking at screen | ### Action Items | Feedback | Action | Backlog Link | |----------|--------|--------------| | Font size too small | Increase heading sizes in `SpeechCaptureActivity` | [[Feature_Backlog#Increase Font Size]] | | Confirm step unnecessary | Skip confirmation for single-word definitions | [[Feature_Backlog#Skip Confirmation]] | | Manual Done tap | Implement auto-dismiss with countdown | [[Feature_Backlog#Auto-Dismiss Definition]] | | Can't delete captures | Add swipe-to-delete in Archive | [[Feature_Backlog#Delete Captures]] | | Multi-word concepts | Add "Define This Instead" button | [[Feature_Backlog#Multi-Word Concept Support]] | ### Session Notes User J is a regular reader (2-3 books/month) who currently uses Apple Notes to save quotes. Primary frustration: "By the time I unlock my phone and type, I've lost the moment." This aligns with our core hypothesis. User was testing during an actual reading session with a physical book, which provided authentic context. --- ## Session-002 **User:** User A **Date:** 2026-01-17 **Device:** Pixel 10 Pro, Android 13 **Session Type:** Extended dogfooding session + verbal feedback **Build Version:** Smart Capture v2 (pre-Library restructure) ### Context User A (the developer) ran an extended dogfooding session while reading *Hyperion* by Dan Simmons. Multiple capture attempts, edge case discovery, and navigation testing. Resulted in significant bug discoveries and UX feedback that drove the Library restructure. ### Feedback Items #### Usability Issues | # | Category | Observation | Severity | |---|----------|-------------|----------| | 1 | **Navigation** | "Archive" naming doesn't match mental model—it's a Library, not an archive | Medium | | 2 | **Navigation** | Sessions-first hierarchy is backwards; want to see all captures for a Book | High | | 3 | **Bug** | Capture doesn't retrigger from lock screen after closing/dismissing | Critical | | 4 | **Functionality** | Two-word phrases like "The hegemony" fail Dictionary lookup with no fallback | High | | 5 | **Functionality** | Speech recognition errors can't be corrected; only option is Retry | High | | 6 | **Functionality** | No way to cancel/dismiss from verification screen (word mode) | Medium | | 7 | **Functionality** | Swipe-to-delete too easy to trigger accidentally; no confirmation | High | | 8 | **Functionality** | Quote-to-word conversion crashes silently | Critical | | 9 | **Functionality** | Undefined words pile up with no easy way to clear them | Medium | #### Positive Observations | # | Observation | |---|-------------| | 1 | Smart Capture word/quote detection feels natural and accurate | | 2 | "Define This Instead" button solves the multi-word concept problem elegantly | | 3 | Swipe-to-convert (word ↔ quote) is intuitive once discovered | | 4 | Session pills in Book card provide good information density | | 5 | The "Clear All Undefined" banner is exactly what's needed | #### Suggestions | # | Suggestion | Notes | |---|------------|-------| | 1 | Book-first hierarchy in Library | Implemented same day | | 2 | Editable text field in verification screen | Implemented same day | | 3 | Wikipedia fallback for phrases/concepts | Implemented same day | | 4 | Delete confirmation dialog | Implemented same day | | 5 | Consider "tap to re-lookup" on converted words | Future backlog item | ### Action Items | Feedback | Action | Status | |----------|--------|--------| | Archive → Library naming | Renamed navigation tab and internal references | ✅ Complete | | Book-first hierarchy | Implemented `LibraryView`, `BookCard`, `BookDetailView` | ✅ Complete | | Capture re-launch bug | Added `onNewIntent()` and `onStop()` handlers | ✅ Complete | | Two-word phrase failure | Added Wikipedia API fallback + article stripping | ✅ Complete | | No text editing | Added `BasicTextField` in verification screen | ✅ Complete | | No cancel button | Added Cancel button in verification screen | ✅ Complete | | Accidental deletion | Added AlertDialog confirmation for swipe-delete | ✅ Complete | | Conversion crash | Wrapped in try-catch with error logging | ✅ Complete | | Undefined word cleanup | Added "Clear Undefined" banner + bulk delete | ✅ Complete | ### Session Notes User A is the developer, so feedback is technically detailed but may have blind spots a pure end-user would catch. The dogfooding approach proved valuable—real reading sessions with real books surface edge cases that synthetic testing misses. Key insight: "Shrike Church" (from *Hyperion*) was consistently misheard by speech recognition. The editable text field solved this, but highlighted that speech recognition quality may need attention in future iterations. The Library restructure (Book → Session → Captures) fundamentally changed how the app feels. This was a "why didn't we do this from the start" moment. --- ## Session-002 Addendum (End of Day) **Date:** 2026-01-17 (evening) **Context:** Post-implementation testing of Library restructure ### Additional Issues Discovered | # | Category | Observation | Severity | Status | |---|----------|-------------|----------|--------| | 10 | **Bug** | Book Detail view crashes the app on tap | Critical | [[Bug Tracker#BUG-003]] | | 11 | **Bug** | "Tap to look up" on converted words does nothing | High | [[Bug Tracker#BUG-004]] | | 12 | **UX** | Session rows inside Book Detail not obviously clickable | Medium | Backlog | | 13 | **UX** | "Define This Instead" button too subtle / easy to miss | Medium | Backlog | | 14 | **Missing** | Words and quotes have no visible timestamps | Low | Backlog | | 15 | **Missing** | Cannot edit/update saved words or quotes | Medium | Backlog | ### Feature Ideas for Exploration | # | Idea | Notes | |---|------|-------| | 1 | **Auto-Define After Delay** | Optional setting: Skip verification, auto-lookup after X seconds of silence | | 2 | **Speech Trigger Settings** | When should speech recognition auto-start? On screen open? After button tap? | | 3 | **AI Vibe Impressions** | End-of-session or end-of-book AI-generated summary of captured themes/vibes | ### Parking Lot (Tomorrow's Priorities) 1. 🔴 Fix Book Detail crash (BUG-003) — blocks all Library testing 2. 🟠 Implement tap-to-relookup for undefined words (BUG-004) 3. 🟡 Make session rows more obviously clickable (visual affordance) 4. 🟡 Improve "Define This Instead" button visibility --- ## Session-003 **User:** User B **Date:** 2026-02-05 **Device:** Android (unspecified) **Session Type:** Demo walkthrough + verbal feedback **Build Version:** Weekly Vibe Wrapped v1 ### Context User B reviewed the app with focus on visual design, navigation patterns, and the conceptual framing of session/capture data. Feedback centered on moving from quantified metrics toward qualitative, vibe-forward presentation. ### Feedback Items #### Usability Issues | # | Category | Observation | Severity | |---|----------|-------------|----------| | 1 | **Navigation** | Sessions within Book view are not obviously clickable or interactable | Medium | | 2 | **Discovery** | No clear way to see previous sessions or session history | Medium | #### Suggestions | # | Suggestion | Notes | |---|------------|-------| | 1 | Session metadata should be less quantified | Numbers feel like data tracking, not reading companion | | 2 | Descriptive session summaries over metrics | "What you learned" and "vibes achieved" as distinct moments | | 3 | Communicate insights without numbers | Poetic/qualitative descriptors instead of "5W \| 2Q" | | 4 | Co-Star design reference | "If the people that designed Co-Star are making this?" | #### Positive Observations | # | Observation | |---|-------------| | 1 | "Interesting foundations" | | 2 | Visual design has potential to make it shine | ### Design Direction The Co-Star reference is significant. Co-Star (the astrology app) is known for: - Poetic, vibe-forward copy instead of clinical data - Dark aesthetic with intentional typography - Treating abstract concepts (planetary positions) as personal insights - Never feeling like "data tracking" Applied to Vibe Reader, this suggests: - Session cards could show "A session of existential wandering" instead of "45 min" - Capture summaries could be "You lingered on power and mortality" instead of "5W | 2Q" - The Weekly Vibe is already moving this direction; extend to session-level - Consider AI-generated session "titles" or "moods" based on captures ### Action Items | Feedback | Action | Backlog Link | |----------|--------|--------------| | Sessions not clickable | Add visual affordance (chevron, ripple, card elevation) | [[Feature Backlog#Session Rows Visual Affordance]] | | Quantified metadata | Explore AI-generated session descriptors | New backlog item | | Co-Star aesthetic | Visual design pass with vibe-forward copy | Future exploration | ### Session Notes This feedback challenges the "metrics dashboard" mental model. The insight: readers don't care that they captured 5 words and 2 quotes. They care about *what* those captures meant, *why* they stopped to save them, and *what patterns* emerge over time. The Weekly Vibe Wrapped redesign is a step in this direction, but the same philosophy should permeate session-level and book-level presentation. Key question to explore: Can AI generate a one-line "vibe summary" for each session based on its captures? "A meditation on impermanence" hits differently than "Session 3: 8 captures." --- ## Session-003 Addendum **User:** User C **Date:** 2026-02-05 **Context:** Additional design direction feedback ### The Reference > "What if this app had the feeling of Journey (the video game) but had the look of Co-Star?" ### Design Implications **Journey (thatgamecompany, 2012):** - Wordless, meditative, emotionally resonant - Progression through environment, not explicit metrics - Companionship without intrusion - Discovery over instruction - The journey *is* the point, not the destination **Co-Star (astrology app):** - Dark aesthetic, intentional typography - Poetic/mystical copy, never clinical - Data presented as personal insight, not tracking - Treats mundane (planetary positions) as meaningful **Combined Vision for Vibe Reader:** - The reading session as a meditative journey - Captures as waypoints discovered, not metrics logged - Progress felt through accumulated meaning, not numbers - Companionship: the app as a silent presence, not a dashboard - End-of-session "arrival" that reflects on what was found This is a strong aesthetic and experiential direction. It suggests the app should feel like *accompanying* the reader on a journey, quietly noting what resonated, and reflecting it back in a way that honors the reading experience rather than quantifying it. --- ## Session-004 **User:** User D **Date:** 2026-02-05 **Session Type:** First impression feedback **Build Version:** Weekly Vibe Wrapped v1 ### Context User D evaluated the app without prior reading sessions. Feedback surfaced the cold start problem and a potential expansion of the product vision. ### Feedback Items #### The Cold Start Problem > "The usefulness doesn't seem very present without commitment to read with the app... or until I've done some reading over time with it." This is a legitimate barrier. The app's value proposition only materializes *after* the user has: 1. Started a session 2. Captured words/quotes 3. Accumulated enough data for patterns to emerge For a new user looking at an empty Library, the "why" isn't self-evident. #### The Suggestion: Vibe-Based Book Discovery > "What if I don't know what I want to read but I have an idea of a vibe that the reading page guides me toward? Helps me find a book with the vibe?" Proposed interaction: - Describe in one sentence the vibe you're seeking - Or tap floating options: "whimsical" "funny" "dark" "romantic" "esteemed" "classical" "popular" "short" - App suggests books that match the vibe ### Product Implications This reframes the app from: - **Current:** Capture companion for active readers (requires commitment) - **Proposed:** Reading discovery + capture companion (value from first interaction) The vibe tags could work bidirectionally: 1. **Input:** "I want something dark and short" → book recommendations 2. **Output:** "Your captures this week were dark and philosophical" → Weekly Vibe This creates a loop: ``` Vibe Discovery → Book Selection → Reading Session → Captures → Vibe Reflection ↑ ↓ └──────────────── "More like this" ────────────────────────────┘ ``` ### Considerations **For:** - Solves cold start problem - Creates value before first capture - Natural extension of "vibe" branding - Could integrate with Goodreads/Open Library APIs for recommendations **Against:** - Scope creep from core capture hypothesis - Book recommendation is a crowded space - Requires significant new functionality - May dilute the "frictionless capture" focus **Middle ground:** - V1: Stay focused on capture - V2: If vibe reflection proves valuable, extend to discovery - The vibe tags from Weekly Vibe could seed future recommendations ### Action Items | Feedback | Action | Priority | |----------|--------|----------| | Cold start problem | Consider onboarding that demonstrates value with sample data | P1 | | Vibe-based discovery | Park for V2 exploration; document in [[Product Explorations]] | P3 | ### Session Notes This feedback challenges the assumption that users arrive with a book in hand. Some readers are *looking for* the next book. If Vibe Reader could help with that moment, it becomes valuable before the first capture. The floating vibe tags ("whimsical", "dark", "esteemed") are evocative. They match the Co-Star/Journey aesthetic direction from earlier feedback. Worth exploring whether the start screen could feel more like "choosing a vibe" than "entering a book title." --- ## Session-005 **User:** User E **Date:** 2026-02-05 **Session Type:** Interaction exploration **Build Version:** Weekly Vibe Wrapped v1 ### Feedback > "It's not obvious when something can or can't be interacted with, like dragging quotes or words in the session view, or clicking on a session within the book tile in the Library View." ### The Pattern This echoes Session-002 Addendum (#12) and Session-003 (#1). Three separate users have now flagged interaction affordances as unclear. This is a systemic UX issue, not an edge case. **Specific gaps identified:** - Session pills in Book cards (Library View): clickable but don't look it - Session rows in Book Detail: clickable but don't look it - Word/Quote items in Session Detail: swipeable but no visual hint - Drag interactions: users expect drag but it's swipe-only ### Severity Upgrade Given repeated feedback across multiple users, **interaction affordances** should be elevated to P1. --- ## Session-006 **User:** User J **Date:** 2026-02-06 **Session Type:** In-person ideation + product exploration **Build Version:** Post-Weekly Vibe Wrapped ### Context Extended feedback session exploring the conceptual foundations of "vibe" and how emotional/intellectual state capture could evolve beyond word/quote logging. Session included both User J's feedback and developer's own ideation. ### Framing: What is a Vibe? > "Once they have an image, they can help you get there." > "They don't want to hear it's not possible. They want to hear: here's what could make it possible." The session explored vibe as the crossover between: - Emotional response - Instinctive response - Aesthetic quality of an action, activity, or feeling ### Feedback Items #### Suggestions | # | Suggestion | Notes | |---|------------|-------| | 1 | **Vibe on where you are** | Kindle-style contextualization; inputs inform your experience of the reading | | 2 | **Session closure vibe** | Prompt to capture emotional/intellectual state at session end | | 3 | **Timeline animations** | Transformations as you scroll through sessions; help you *re-feel* what you felt | | 4 | **2D Vibe Selection UI** | Pleasantness (x) vs Tension (y) plane; tap/drag to select feeling; word under finger changes | | 5 | **Idle session / background vibe** | Bucket for captures outside active reading; grouped by day/week | | 6 | **"Your vibe was..."** | Session summary framing; what caught your eye | | 7 | **Wavy timeline** | Meandering journey lines between sessions and captures | | 8 | **Future inputs** | Snap a photo, voice beyond words | #### Research Direction | # | Area | Notes | |---|------|-------| | 1 | **Russell's Circumplex Model** | X-Y axis for emotion (pleasantness × arousal); established research | | 2 | **Emotional vocabulary grid** | Populate 2D plane with feeling words at geometric positions | | 3 | **Color wheel metaphor** | Map color rectangle on phone to emotional plane | ### Design Implications **The 2D Vibe Selector** - Geometric position = vector for a feeling - Tap in space between labeled emotions - Drag around, word under finger updates - Requires emotional research to populate grid **Not Just Projection, But Reflection** > "Not just for projecting vibes while reading, but for *reading* your vibe." A thought or word can be interesting any time of day. The idle session concept extends capture beyond active reading. ### Action Items | Feedback | Action | Backlog Link | |----------|--------|--------------| | Session closure vibe | Add vibe prompt at session end | [[Feature Backlog#Session Closure Vibe Prompt]] | | 2D vibe selection | Research + prototype 2D feeling selector | [[Feature Backlog#2D Vibe Selection UI]] | | Timeline animations | Design wavy, meandering session timeline | [[Feature Backlog#Animated Session Timeline]] | | Idle session | Background vibe bucket for non-reading captures | [[Feature Backlog#Idle Session Mode]] | | "Your vibe was..." | Reframe session summaries around vibe language | [[Feature Backlog#Vibe-Forward Session Descriptors]] | ### Session Notes This session pushed beyond capture mechanics into the emotional/experiential layer. The 2D feeling plane is a significant UX concept that could differentiate Vibe Reader from simple note-taking. Key insight: the same word ("tense") means different things at different positions on the arousal spectrum. The idle session concept challenges the assumption that captures only happen during reading. A background vibe mode could make the app useful throughout the day. See also: [[02.06.26 - What is a Vibe]] --- ## Themes from 2026-02-05 Feedback Sessions Five users provided feedback today. The following themes emerged: ### Theme 1: Interaction Affordances (P1) **Users:** B, E + prior (Session-002 Addendum) **Problem:** Interactive elements don't signal interactivity. Users don't know what's tappable, swipeable, or draggable. **Evidence:** 3+ users flagged session rows, session pills, and capture items as unclear. **Action:** Visual pass on all interactive elements. Add chevrons, ripples, drag handles, or elevation cues. ### Theme 2: Vibe-Forward Presentation (P2) **Users:** B, C **Problem:** Quantified metrics ("5W | 2Q", "45 min") feel like data tracking, not a reading companion. **Vision:** Poetic, qualitative descriptors. "A meditation on impermanence" over "Session 3: 8 captures." **Reference:** Co-Star aesthetic (poetic, never clinical) **Action:** AI-generated session vibes; replace numeric badges with descriptive summaries. ### Theme 3: Meditative Experience (P2) **Users:** C **Problem:** App feels like a dashboard, not a companion. **Vision:** Journey (video game) feeling. Wordless, emotionally resonant, discovery over instruction. **Action:** Design pass emphasizing the reading journey, captures as waypoints, reflection as arrival. ### Theme 4: Cold Start Problem (P1) **Users:** D **Problem:** Empty Library = unclear value proposition. App requires commitment before showing usefulness. **Action:** Onboarding with sample data, or alternative entry point that demonstrates value immediately. ### Theme 5: Vibe-Based Discovery (P3 / V2) **Users:** D **Problem:** Not all users arrive with a book. Some are searching for what to read next. **Vision:** Floating vibe tags ("whimsical", "dark", "esteemed") guide book discovery. **Action:** Park for V2. If vibe reflection proves valuable, extend to discovery. --- ## Feedback Summary Metrics | Metric | Value | |--------|-------| | Total Sessions | 6 (+1 addendum) | | Total Users | 6 | | Total Feedback Items | 46 | | Items Converted to Backlog | 31 | | Items Resolved Same Day | 9 | | Open Bugs Filed | 2 | --- ## Planned Sessions | User | Scheduled | Focus Area | |------|-----------|------------| | TBD | TBD | Lock screen reliability on different devices | | TBD | TBD | Archive navigation and Book Layer view | --- ## Feedback Collection Template ```markdown ## Session-XXX **User:** User [Letter] **Date:** YYYY-MM-DD **Device:** [Device + Android version] **Session Type:** [In-person / Remote / Async] **Build Version:** [Version identifier] ### Context [Brief description of what was tested and how] ### Feedback Items #### Usability Issues | # | Category | Observation | Severity | |---|----------|-------------|----------| #### Positive Observations | # | Observation | |---|-------------| #### Suggestions | # | Suggestion | Notes | |---|------------|-------| ### Action Items | Feedback | Action | Backlog Link | |----------|--------|--------------| ### Session Notes [Additional context, quotes, observations] ```