Bug Report: Critical Sync Issues & UI Feedback (Nov 4, 2025)

by Admin 61 views
Bug Report: Nov 4, 2025 - Critical Issues and UI Feedback

Alright, guys, here's the lowdown on the bug feedback from November 4, 2025. We've got some critical issues to tackle, especially around syncing and security, plus a bunch of UI/UX tweaks to make things smoother, particularly on mobile. Let's dive in!

  • Test Environment: iPhone 16 Pro Max

🛑 Critical Bugs & Tasks

Let's start with the stuff that's really broken. These are the critical bugs that need our immediate attention. We're talking about features that are completely failing or causing major roadblocks for users. These critical bugs need to be addressed before we move on to the smaller stuff. It's all hands on deck to get these fixed, like, yesterday!

  • [ ] Sync Failure (Critical):
    • Issue: Sync testing failed between two browser instances. This is a major problem because syncing is fundamental to how our app works. Without reliable syncing, users can't trust that their data is consistent across devices.
    • Steps: Shared code from Browser 1, used code in Browser 2.
    • Result 1: "Successful" message appeared, but no data was synced. This is misleading and gives the user a false sense of security. They think their data is syncing, but it's not, which can lead to data loss or inconsistencies.
    • Result 2: After a page refresh, login was no longer possible. This is a showstopper. If users can't even log in after a failed sync, the app is essentially unusable. We need to figure out why the sync failure is causing login issues and fix it ASAP.
  • [ ] Security Lock (Critical):
    • Issue: The app sometimes fails to unlock from the safety lock after the user tabs out and back in. This is a major security concern. If the app isn't properly locking and unlocking, user data could be exposed. We need to ensure the safety lock is functioning reliably.
    • Task: Investigate console.log output to trace this unlock failure. The console.log output should give us clues as to why the unlock is failing. We need to analyze the logs to identify any errors or unexpected behavior.
  • [ ] Test Data Not Loading:
    • Issue: Transactions present in the test data file are not appearing in the app. If the test data isn't loading correctly, we can't properly test the app's functionality. This makes it difficult to identify and fix bugs.
    • Task: Add enough connected test data to also populate the Analytics page. We need to ensure the test data is comprehensive and covers all aspects of the app. This includes adding data that populates the Analytics page, so we can test its functionality.
    • Task: Ensure data connections are correctly mapped (e.g., Debt > Bills > Envelope > Transactions, etc.). The data connections need to be properly mapped so that the data flows correctly through the app. If the connections are broken, the data won't be displayed correctly.
  • [ ] Debt Page - Payoff Strategies:
    • Issue: This feature is currently disabled due to an error in the old codebase. The Debt Page's Payoff Strategies feature needs to be addressed as it is currently disabled. Getting it back online is important for users. This is a valuable feature that helps users manage their debt. We need to investigate the error, fix it, and re-enable the feature. Let's get those payoff strategies back on track, stat!

📱 Mobile-Specific UI/UX

Now, let's talk about the mobile experience. We want to make sure our app looks and feels great on smaller screens. These mobile UI/UX issues are all about making the app more user-friendly on iPhones and other mobile devices. We want to create a seamless and intuitive experience for our mobile users. So we want to make sure the UI/UX is perfect for our mobile users. Let's make it shine!

  • [ ] Settings Menu: The entire settings menu feels too tight on mobile. It needs a UI/UX revision for smaller screens. A cramped settings menu can be frustrating to navigate. We need to make sure the settings are easily accessible and spaced out appropriately for mobile users. This is important for user satisfaction.
  • [ ] Supplemental Accounts: Change the header to display on two lines ("Supplemental Accounts") instead of truncating to "Supp. Accounts". Truncated text can be confusing and unprofessional. We need to make sure all text is fully visible and easy to read, even on smaller screens.
  • [ ] Bottom Nav Bar: The mobile navigation bar is too compact.
    • Suggestion: Space out buttons to only show full, complete items. Implement a "ratcheting" scroll (one item scrolls out of view as a new one scrolls in). A compact navigation bar can be difficult to use, especially on smaller screens. Spacing out the buttons and implementing a "ratcheting" scroll would make it easier for users to navigate the app.
  • [ ] Bill Manager Tabs: The tabs for "Upcoming," "Paid," etc., are too compact.
    • Suggestion: Apply the same "ratcheting" scroll logic from the nav bar, only showing full tabs. Just like the navigation bar, the bill manager tabs need to be more user-friendly. Implementing the same "ratcheting" scroll logic would make it easier to switch between tabs.

📄 General UI & Page-Specific Fixes

Time to iron out some of the general UI and page-specific issues. These are the little things that can make a big difference in the overall user experience. We're talking about inconsistencies, layout problems, and visual tweaks that will make the app more polished and professional. Let's make sure everything is pixel-perfect!

App-wide

These are issues that affect the entire app. They're not specific to any one page or feature, but they impact the overall user experience. Addressing these issues will improve the app's consistency and usability.

  • [ ] Sync Menu: The sync menu modal opens attached to the header, not in the center of the app. This looks unprofessional and can be confusing for users. The sync menu should be centered on the screen so that it's clear it's a separate modal.
  • [ ] Pull to Refresh: The "pull to refresh" action appears inside the sub-page content, causing the UI to move.
    • Suggestion: Change this to a single, app-wide modal that overlays the entire screen. The current "pull to refresh" implementation is jarring and disrupts the user experience. A single, app-wide modal would be much smoother and more consistent.
  • [ ] Navigation Order:
    • Suggestion: Reorder the navigation to prioritize high-use areas: Dashboard > Envelopes > Bills > Transaction > (The rest). The current navigation order may not be optimal for all users. Reordering it to prioritize high-use areas would make it easier for users to access the features they use most often.

Summary Cards

Let's refine the layout of the summary cards to improve readability and visual appeal. These cards provide a quick overview of key financial information, so it's important that they're clear and concise. By adjusting the spacing and alignment, we can make the cards more scannable and easier to understand.

  • [ ] Layout: Reduce vertical spacing between "Total Cash" and "Click to Distribute". Reducing the vertical spacing will make the card more compact and easier to read.
  • [ ] Layout: Reduce vertical spacing between "Unassigned Cash" and "Click to Distribute". Similar to the above, reducing the vertical spacing will improve the card's layout.
  • [ ] Layout: Fully center-align the "Savings Total" text. Centering the text will improve the card's visual balance.
  • [ ] Layout: Reduce vertical spacing between "Biweekly Remaining" and "Total Allocation". Again, reducing the vertical spacing will make the card more compact and easier to read.

Savings Page

The savings page is a key area for users to track their savings goals. We want to make sure the layout is visually appealing and easy to navigate. By adjusting the size and arrangement of the savings goal sub-cards, we can create a more engaging and user-friendly experience. Let's experiment with different layouts to find the one that works best.

  • [ ] Layout: The savings goal sub-cards are too large.
    • Suggestion: Test a "two rows of two" grid layout for these cards. A "two rows of two" grid layout would make the savings page more visually appealing and easier to scan. It would also allow us to display more information on the page without making it feel cluttered.

Filters (Debt, Bills, Transactions)

Consistency is key when it comes to UI elements. By replicating the filter design from the "Debts" page and applying it to the "Bills" and "Transactions" pages, we can create a more cohesive and intuitive user experience. This will make it easier for users to find the information they're looking for, regardless of which page they're on.

  • [ ] Task: Replicate the filter design from the "Debts" page and apply it to the "Bills" and "Transactions" pages.
  • [Example - Debt Page]
  • [ ] Suggestion: Turn the "active filter" area into a master button to toggle all filters on/off. A master button to toggle all filters on/off would make it easier for users to quickly clear or apply filters.

Paycheck Page

Let's make sure the Paycheck Page is looking its best. We need to address the missing hard block outline in the "Paycheck History" section. This is a regression, meaning it was working before and now it's broken. We need to fix it to restore the page's original design and ensure a consistent user experience.

  • [ ] Theme (Regression): The "Paycheck History" section is still missing its hard block outline.

Okay, that's the rundown! Let's get these bugs squashed and the UI polished. Good luck, team!