Worst Parts of the Codebase
Known technical debt and areas for improvement
Worst Parts of the Codebase
Source: This page is based on docs/WORST_PARTS_OF_THE_CODEBASE.md
This document identifies areas of the codebase that require significant improvement, ordered by overall impact on development velocity and user experience.
Priority List
1. Session State Computation for UI Components
Status: ✅ RESOLVED (January 2026)
Major refactoring completed. See Session State Computation for details.
Improvements:
- 99% reduction in graph state operations
- 95% reduction in wasted progression computation
- Clean separation of concerns
2. Session Graph Node and Edge Styling Computation Flow
Status: ✅ RESOLVED (January 2026)
Optimized as part of session state refactor.
Improvements:
- Single-pass computation
- Pre-computed maps for O(1) lookups
- Eliminated redundant filtering
3. Builder Graph Node and Edge Styling Computation Flow
Status: ⚠️ Needs Improvement
Similar issues to session graph, but not yet refactored.
Issues:
- Multiple passes over data
- Redundant computations
- Could benefit from session graph patterns
4. Builder Page
Status: ⚠️ Needs Improvement
The main workflow builder page has accumulated complexity.
Issues:
- Large component with multiple responsibilities
- Complex state management
- Could benefit from decomposition
5. Sheet Components
Status: ⚠️ Needs Improvement
Sheet rendering and interaction logic is complex and performance-sensitive.
Issues:
- Performance concerns with large datasets (>1000 rows)
- Complex cell rendering logic
- See Sheets Audit for details
6. Group Invitation Flows
Status: ⚠️ Needs Improvement
User invitation and onboarding flows could be more streamlined.
Issues:
- Multiple paths for adding users
- Inconsistent UX across different invitation types
- Email delivery reliability
7. Tiptap Editor Components
Status: ⚠️ Needs Improvement
Rich text editing using Tiptap has some rough edges.
Issues:
- Complex configuration
- Styling inconsistencies
- Mobile support challenges
8. Builder Mobile Layout
Status: ⚠️ Needs Improvement
The workflow builder is primarily designed for desktop.
Issues:
- Limited mobile responsiveness
- Touch interactions not optimized
- Small screen UX challenges
9. Mobile Pages/Sheets in General
Status: ⚠️ Needs Improvement
Mobile experience across the app needs attention.
Issues:
- Inconsistent mobile layouts
- Performance on mobile devices
- Touch gesture support
10. Party Frames
Status: ⚠️ Needs Improvement
Collaborative presence features (user avatars, cursors) need refinement.
Issues:
- Performance with many participants
- Visual clutter in some scenarios
- Could benefit from better positioning logic
How to Use This Document
This list is intentionally brief and prioritized. When planning refactoring work:
- Check if already resolved - Several items have been addressed
- Consider impact - Higher items affect more users/developers
- Look for patterns - Many issues share common solutions
- Document improvements - Update this list when work is completed