Implement progressive batch loading for faster recent edits

PERFORMANCE IMPROVEMENTS:
- Reduce API fetch limits from 20x to 8x (400→160 pages) for balanced performance
- Add progressive batch sizing: start with 15 items, increase to 20+5*batch for subsequent loads
- Fix Firebase admin initialization in subscription portal route (build-time issue)

PROGRESSIVE LOADING LOGIC:
- Initial load: 15 items for fast first paint
- Batch 2: 25 items (20 + 5*1)
- Batch 3: 30 items (20 + 5*2)
- Max batch: 50 items (capped)

BENEFITS:
- Much faster initial page load
- Smooth infinite scroll with increasing batch sizes
- Maintains data continuity while improving perceived performance
- Fixes build errors from module-level Firebase initialization

Author: sirjamesgray

app/api/recent-edits/route.ts

@@ -87,12 +87,12 @@ export async function GET(request: NextRequest) {
         .where('deleted', '!=', true) // Filter out deleted pages (includes pages without deleted field)
         .orderBy('deleted') // Required for != queries
         .orderBy('lastModified', 'desc')
-        .limit(limit * 10); // Increased multiplier to account for heavy filtering
+        .limit(limit * 5); // Moderate multiplier for user-specific queries
     } else {
-      // For general recent edits, fetch much more data to account for filtering
+      // Progressive batch loading: Start with reasonable fetch size, let client request more
       pagesQuery = db.collection(getCollectionName('pages'))
         .orderBy('lastModified', 'desc')
-        .limit(limit * 20); // Dramatically increased to ensure continuous data after filtering
+        .limit(limit * 8); // Balanced: enough data after filtering, but fast initial load
     }
 
     // Add cursor for pagination

app/api/subscription/portal/route.ts

@@ -8,14 +8,14 @@ import { NextRequest, NextResponse } from 'next/server';
 import { getUserIdFromRequest } from '../../auth-helper';
 import { initAdmin } from '../../../firebase/admin';
 
-// Initialize Firebase Admin
-const admin = initAdmin();
-const adminDb = admin.firestore();
-
 const stripe = require('stripe')(process.env.STRIPE_SECRET_KEY);
 
 export async function POST(request: NextRequest) {
   try {
+    // Initialize Firebase Admin inside function to avoid build-time issues
+    const admin = initAdmin();
+    const adminDb = admin.firestore();
+
     // Get authenticated user
     const userId = await getUserIdFromRequest(request);
     if (!userId) {

app/components/features/SimpleRecentEdits.tsx

@@ -63,18 +63,24 @@ export default function SimpleRecentEdits() {
   });
   const [isFollowingAnyone, setIsFollowingAnyone] = useState<boolean | null>(null);
   const [followCardDismissed, setFollowCardDismissed] = useState(false);
+  const [batchNumber, setBatchNumber] = useState(1); // Track batch number for progressive loading
 
   const fetchRecentEdits = useCallback(async (cursor?: string, append = false) => {
     try {
       if (!append) {
         setLoading(true);
         setError(null);
+        setBatchNumber(1); // Reset batch number for fresh loads
       } else {
         setLoadingMore(true);
+        setBatchNumber(prev => prev + 1); // Increment batch number
       }
 
+      // Progressive batch sizing: Start small for fast initial load, increase for subsequent batches
+      const currentBatchSize = append ? Math.min(20 + (batchNumber * 5), 50) : 15;
+
       const params = new URLSearchParams({
-        limit: '50',
+        limit: currentBatchSize.toString(),
         includeOwn: filters.includeOwn.toString(),
         followingOnly: filters.followingOnly.toString()
       });
@@ -114,7 +120,7 @@ export default function SimpleRecentEdits() {
       setLoading(false);
       setLoadingMore(false);
     }
-  }, [user?.uid, filters]);
+  }, [user?.uid, filters, batchNumber]);
 
   // Load more items when scrolling near bottom
   const loadMore = useCallback(() => {

docs/SIMPLIFIED_ACTIVITY_SYSTEM.md

@@ -2,7 +2,15 @@
 
 ## Overview
 
-WeWrite's activity system has been completely refactored from a complex multi-collection approach to a simple, reliable system based on recent pages with diff data stored directly on page documents.
+WeWrite's activity system has been completely refactored from a complex multi-collection approach to a simple, reliable system based on the unified version system with embedded token allocation controls.
+
+## 🚀 Latest Updates (July 2025)
+
+### Recent Edits System Overhaul
+- **✅ Fixed Data Gaps**: Increased fetch limits from 60 to 400 pages to eliminate massive timeline gaps
+- **✅ Smart Token Controls**: Added conditional token allocation bars (hidden on user's own pages)
+- **✅ Include Own Edits**: Changed default to show user's own recent edits for complete activity feed
+- **✅ Unified Version System**: All recent edits now pull from the consolidated version system
 
 ## Architecture
 
@@ -34,6 +42,47 @@ Activity Page → Query recent pages → Show pages with diff data
 - Automatic consistency (diff data lives with page)
 - Easier to maintain and debug
 
+## Recent Edits API Architecture (2025)
+
+### Critical Performance Fixes
+
+The recent edits system underwent major performance and data integrity improvements:
+
+#### 1. Increased Fetch Limits
+```typescript
+// OLD: Insufficient data causing gaps
+.limit(limit * 3); // Only 60 pages total
+
+// NEW: Adequate data for continuous timeline
+.limit(limit * 20); // 400 pages for general recent edits
+.limit(limit * 10); // 200 pages for user-specific edits
+```
+
+**Problem Solved**: The API was only fetching 60 pages before applying heavy filtering (visibility, ownership, deleted status), leaving massive 4-month gaps in the timeline.
+
+#### 2. Smart Token Allocation Controls
+```typescript
+// Only show token allocation for other users' pages
+{activity.userId && activity.pageId && user?.uid !== activity.userId && (
+  <EmbeddedTokenAllocation
+    pageId={activity.pageId}
+    authorId={activity.userId}
+    pageTitle={currentPageName}
+    source="HomePage"
+  />
+)}
+```
+
+**Benefit**: Users no longer see confusing token allocation controls on their own pages where allocation isn't possible.
+
+#### 3. Include Own Edits by Default
+```typescript
+// NEW: Show complete activity feed including user's own edits
+includeOwn: true, // Users want to see all recent activity including their own
+```
+
+**Rationale**: Most recent activity comes from the logged-in user, so excluding their own edits created artificially sparse feeds.
+
 ## Implementation Details
 
 ### 1. Diff Data Storage on Pages