Family Shapes Roadmap
Development priorities and milestones spanning permissions, platform separation, donor portal, and quality/tooling work.
Source Summary
--- title: Development Roadmap description: Future development plans and milestones for Family Shapes status: evolving lastUpdated: 2025-10-03 00:00 ET owner: Product/Engineering Team --- # Development Roadmap Last updated: 2025-10-03 00:00 ET This document outlines the planned development roadmap for the Family Shapes project, organized by phases with cle
Imported Context
title: Development Roadmap description: Future development plans and milestones for Family Shapes status: evolving lastUpdated: 2025-10-03 00:00 ET owner: Product/Engineering Team
Development Roadmap
Last updated: 2025-10-03 00:00 ET
This document outlines the planned development roadmap for the Family Shapes project, organized by phases with clear priorities and dependencies.
๐จ Immediate Priorities (Next 2 Weeks)
These are the most urgent tasks that agents should focus on first:
-
๐ด [P1.1] Comprehensive Audit: Sharing/Permissions/Security/Privacy (Frontend + Backend)
- Due: 2 business days
- Owner: Product/Engineering (Architecture + Frontend + Backend)
- Dependencies: None
- Deliverables:
- Inventory of all sharing/permissions/privacy/visibility UI and backend endpoints
- Mapping of frontend-only vs backend-supported features (and vice versa)
- Deprecation/removal plan for redundant UIs (e.g.,
/sharepage) - Gap list and recommendations to align with
family_tree_collaboratorsand invitations
-
๐ด [P1.2] Family Tree Permissions UI: Implement proper role constraints and update RLS policies
- Due: End of Month
- Owner: Database Team
- Dependencies: Audit outcomes informing UI scope
- ๐ ACTIVE BUG: RLS 403 errors on
family_tree_collaboratorsINSERT operations persist after migration 0010 deployment.has_tree_role()SECURITY DEFINER function may not be bypassing RLS as intended, causing recursion or access denial. See CHANGELOG.md 2025-10-03 16:15 ET entry for details.
-
๐ด [P2] Implement Three-Platform Architecture: Complete separation of Family Platform components
- Due: Mid-next month
- Owner: Architecture Team
- Dependencies: None
-
๐ด [P1.3] Fix Sharing Links System: Implement persistent membership creation
- Due: End of next month
- Owner: Backend Team
- Dependencies: Family Tree Permissions fix + Audit outcomes
-
๐ด [P7] Family Tree Builder UX/UI Unification (No DB Changes): Unify add person + connect with staged drafts, quick actions, and drag-to-connect per WIP plan
- Due: Next 2 weeks
- Owner: Product Design + Frontend
- Dependencies: None
- Reference:
DOCS/PROJECTS/active/1003_tree_builder_ux_ui_plan.md
Priority Legend
- ๐ด HIGH: Critical features that block other work or provide core value
- ๐ก MEDIUM: Important features that enhance the product significantly
- ๐ข LOW: Nice-to-have features that improve the experience but aren't critical
Status Legend
- โ COMPLETED: Feature is implemented and deployed
- ๐ง IN PROGRESS: Feature is currently being developed
- ๐ PLANNED: Feature is planned but development hasn't started
- ๐ BLOCKED: Feature is blocked by dependencies
Program Index
- P1: Sharing/Permissions/Privacy
- P2: Three-Platform Architecture
- P3: Donor Portal
- P4: Multi-tenant SaaS Platform
- P5: Mobile Applications
- P6: International Expansion
- P7: Canvas & UX Unification
- P8: Quality & Tooling (Migrations, Testing, Docs)
- P9: Analytics & Reporting
- P10: Integrations
- P11: Community Hub
- P14: AI & Matching
- P15: Research Platform/Integration with existing Research Institutions
Key Milestones
| Milestone | Target Date | Status | Key Deliverables |
|---|---|---|---|
| Database Architecture Refactoring | Q3 2025 | ๐ง IN PROGRESS | Family Tree Permissions, Three-Platform Architecture, Sharing Links System |
| Enhanced Donor Portal | Q4 2025 | ๐ PLANNED | Advanced Privacy Controls, Health History Tracking, Secure Messaging |
| Multi-tenant SaaS Platform | Q1 2026 | ๐ PLANNED | SaaS Onboarding, Subscription Management, Donor Database |
| Mobile Applications | Q2 2026 | ๐ PLANNED | iOS App, Android App, Offline Capabilities |
| International Expansion | Q3 2026 | ๐ PLANNED | Localization, Region-specific Compliance |
Current Phase: Database Architecture Refactoring (Q3 2025)
In Progress
-
๐ง ๐ด [P1.1] Security/Sharing Audit: System-wide inventory and rationalization of sharing/permissions/privacy
Status: ACTIVE โ discovery and cataloging
- Identify all frontend screens/components:
src/pages/Share.tsx,src/pages/FamilyTreeSettings.tsx(sharing tab),src/components/family-trees/SharingSettingsPanel.tsx, org invites, etc. - Identify all backend artifacts: RLS,
family_tree_collaborators,family_tree_invitations,user_tree_access, functions (send-invitation,process-invitation,send-sharing-link) - Propose removals (e.g.,
/sharepage), consolidations, and gaps to fill
- Identify all frontend screens/components:
-
๐ง ๐ด [P1.2] Family Tree Permissions: Correct the fundamental confusion in the family tree members table
Status: Database migration applied to linked database; UI implementation pending
-
โ Database Migration Applied (Migration 0007 -
20251002162313_0007_fix_family_tree_permissions.sql):- Created
family_tree_collaboratorstable with user_id and role-based access (owner, admin, editor, viewer) - Created
family_tree_invitationstable for invitation workflow - Migrated existing tree owners to collaborators with 'owner' role
- Updated RLS policies to enforce role-based permissions on family_trees, persons, and connections
- Added helper functions:
has_tree_role(),has_sharing_link_access(),accept_tree_invitation() - Created
user_tree_accessview for easy permission queries
- Created
-
โ Applied via
make db/push;make db/checkreports โ No drift -
โ TypeScript types regenerated with
make db/types -
๐ Next Steps - UI Implementation (see
DOCS/PROJECTS/active/1001_family_tree_permissions.md):- Build service layer for collaborator management (CRUD operations)
- Create React hooks for permission checking and collaborator management
- Build UI components:
- Collaborator list/management panel
- Invitation creation form
- Invitation acceptance flow
- Role selector and permission indicators
- Update tree editing UI to respect collaborator roles
- Test end-to-end invitation and collaboration flows
- Deploy to production:
make db/push(after UI is complete and tested)
-
๐ Reference:
DOCS/PROJECTS/active/1001_family_tree_permissions.md- Single source of truth for this feature
-
-
๐ง ๐ด [P2] Implement Three-Platform Architecture: Separate the architecture for different user types
- Family Platform: For individual users and family communities
- SaaS Platform: For cryobanks and fertility clinics
- Donor Platform: For donors with privacy controls
Planned
-
๐ ๐ด [P1.3] Fix Sharing Links System: Ensure sharing links work correctly with tree visibility
- Implement persistent membership creation from sharing links
- Clarify interaction between sharing links and tree visibility
- Test and fix email functionality for sharing links
-
๐ ๐ก Rename Organizations to Communities: Clarify terminology for family groups
- Update database schema and references
- Update UI labels and documentation
- Ensure backward compatibility
Planning Horizon (6-12 weeks)
Status key: โ Done ยท ๐ก In Progress ยท ๐งญ Planned ยท ๐ค Backlog ยท ๐ Discovery
| Item | Status | Owner | Notes |
|---|---|---|---|
| Union/join nodes for family tree (XYFlow + D3) | ๐ | Frontend Visualization | See DOCS/PROJECTS/backlog/1004_union_join_nodes_plan.md |
| Analytics foundation & dashboards | ๐ | Product/Analytics | Define metrics, event taxonomy, and dashboard MVP |
| Organization onboarding enhancements | ๐งญ | Product Design | Expand waitlist + onboarding flows |
| Performance profiling of large canvases | ๐งญ | Frontend | Monitor render performance >1k nodes |
| Automated regression suite expansion | ๐งญ | QA | Extend Playwright coverage to donor portal flows |
| Documentation re-organization | โ | DX | Completed with DOCS restructure |
Next Phase: [P3] Enhanced Donor Portal (Q4 2025)
Planned
-
๐ ๐ด [P3] Advanced Privacy Controls: Granular privacy settings for donor information
- Per-field privacy settings (medical, personal, contact)
- Recipient-specific privacy rules
- Time-based privacy transitions
-
๐ ๐ด [P3] Health History Tracking: Comprehensive health tracking system
- Medical history questionnaires
- Periodic update reminders
- Health event timeline
- Notification system for recipients
-
๐ ๐ก [P3] Secure Messaging System: Policy-compliant communication
- Anonymous messaging options
- Template-based communication
- Message approval workflows
- Conversation history and archiving
-
๐ ๐ข [P3] Donor Profile Analytics: Insights for donors
- View statistics on profile views
- Geographic distribution of recipients
- Interest metrics and trends
Future Phase: [P4] Multi-tenant SaaS Platform (Q1 2026)
Planned
-
๐ ๐ด [P4] SaaS Onboarding Flow: Specialized onboarding for clinics and banks
- Organization verification process
- Legal agreement integration
- Administrator account setup
- Initial configuration wizard
-
๐ ๐ด [P4] Subscription Management: Seat-based billing system
- Tiered pricing plans
- User seat management
- Billing integration
- Usage analytics
-
๐ ๐ก [P4] Advanced Donor Database: Professional tools for clinics
- Bulk import/export
- Advanced search and filtering
- Matching algorithms
- Compliance reporting
-
๐ ๐ก [P4] White-label Options: Customization for organizations
- Custom branding
- Domain customization
- Email template customization
- UI theme options
Backlog (12+ weeks)
| Item | Status | Owner | Notes |
|---|---|---|---|
| [P10] Partner API integrations | ๐ค | Partnerships | Pending vendor outreach (Ancestry, 23andMe, clinics) |
| [P11] Public community hub iteration | ๐ค | Product | Build on generation-based visualization learnings |
| [P5] Mobile-first donor experience | ๐ค | Mobile | Evaluate React Native vs responsive web |
| [P9] Advanced analytics & reporting suite | ๐ค | Product/Analytics | Build after foundational analytics milestone |
Long-term Vision (2026+)
Planned
-
๐ ๐ด [P5] Mobile Applications: Native mobile experience
- iOS and Android apps
- Offline capabilities
- Push notifications
- Mobile-optimized UI
- iOS Contacts sync with
personsdatabase (import/update full contact info)
-
๐ ๐ก [P14] AI-powered Matching: Advanced connection suggestions
- Genetic similarity analysis
- Interest-based matching
- Relationship prediction
- Privacy-preserving algorithms
-
๐ ๐ก [P6] International Expansion: Support for global users
- Localization and translations
- Region-specific compliance
- International payment options
- Cultural adaptations
-
๐ ๐ข [P15] Research Platform: Tools for academic research
- Anonymized data exports
- Research participant management
- Survey integration
- Longitudinal study tools
Technical Debt and Infrastructure
Ongoing
-
๐ง ๐ด [P8] Database Migration System: Maintain and improve the migration workflow
- Enhance drift detection
- Improve type generation
- Streamline testing of migrations
-
๐ ๐ก [P8] Performance Optimization: Continuous improvement of application performance
- Query optimization
- Frontend rendering optimization
- Asset delivery optimization
- Caching strategies
-
๐ ๐ก [P8] Testing Infrastructure: Enhance test coverage and reliability
- Increase unit test coverage
- Expand end-to-end test scenarios
- Implement visual regression testing
- Performance testing automation
-
๐ ๐ข [P8] Documentation System: Comprehensive documentation
- API documentation
- Developer guides
- User documentation
- Architecture documentation
Planned
- ๐
๐ก Authentication Path Consolidation: Standardize auth routes and remove redundancy
- Audit current auth routes (
/auth,/donor/auth, `
- Audit current auth routes (
...[truncated for intake]
Provenance
- Source file:
family-shapes/ROADMAP.md - Source URL: https://github.com/maggielerman/family-shapes/blob/main/ROADMAP.md