Phase 3 — Image durability (server-side proxy/cache)
Client caching (expo-image) is already solved; this is purely source-URL rot.
- During the pipeline: download each
og:image, resize (~400px WebP), upload to a Supabase Storage bucket, store the permanent bucket URL inimageUrl- Solves URL rot (articles 404 after days), 2–3MB image sizes, hotlink 403s. ~50–100 imgs/day ≈ trivial cost (free tier 1GB)
- Open Q: resize/encode in Node cron (sharp) vs. Supabase image transform; plus a backfill + eviction policy alongside existing
db.evict.
Phase 4 — Usage statistics collector (new component, research-y)
- Component to record usage stats (articles read, time in app) + handle device-registration deletion cleanup
- Lawful basis = "legitimate interests" (no consent popup) if Privacy Policy discloses it; keep aggregate/pseudonymous (userID + articleID + timestamp)
- Open Q: event schema, collection path (app →
/api/...→ Supabase), and retention — the real brainstorm candidate.
- Record user usage statistics for metrics and analysis (see GDPR section under Go Live; overlaps Phase 4 above)
- Start using bun as a package manager
- Privacy Policy hosted at a URL — must name: email, device token, preferences stored in Supabase; third parties Perplexity, Anthropic, Firebase. Link in app (Settings) and store listing
- Account deletion in-app — Google hard-requires this for any app with accounts
- Content rating questionnaire (IARC for Play, similar for App Store)
- Store assets: icon all sizes, 2–8 screenshots, short + long description
Play Store:
- Data Safety form — accurately declare what you collect and share; mismatch with actual behaviour gets you rejected
- Target SDK 34+ (Android 14)
App Store:
- Apple Developer account ($99/yr)
- Privacy nutrition labels
- APNs key for push (see V2 iOS push item)
- Privacy manifest file if you use certain Apple APIs
Allowed — but you need a lawful basis. For product analytics (which articles get read, time in app), "legitimate interests" covers it without a consent popup, as long as your Privacy Policy discloses it. Aggregate/pseudonymous stats (user ID + article ID + timestamp) = fine with disclosure. Selling or sharing with third parties = needs explicit consent.
- Right to deletion — account deletion covers this
- Right to data export — lower priority, rarely enforced for small apps
-
Sources filtering
-
Topic filtering — user selects preferred/suppressed categories (economy, politics, sports…)
-
Pulse weekly — clickable grey down-pointing caret next to "Pulse Daily"; dropdown for daily/weekly/monthly digest
- Daily: ready; weekly = same call with
recency: week; monthly =recency: month
- Daily: ready; weekly = same call with
-
iOS push notifications — FCM needs an APNs key from Apple Developer account uploaded to Firebase (Project Settings → Cloud Messaging → Apple app config → APNs Authentication Key). Requires paid Apple Developer account ($99/yr). Defer until ready to test on a real iOS device.
-
Language / translation — setting for returned article language; default English (no translation)
- Cron side: translate the full digest after fetching, store alongside original in Supabase with a
langcolumn on thedigeststable - Use DeepL (not Claude, not Mistral) — purpose-built for translation, free up to 500k chars/month, better quality than an LLM for most language pairs
- Cron side: translate the full digest after fetching, store alongside original in Supabase with a
Pro deepsearch model runs for potential VIP tier users — would ~10x costs, so need users first.
Cost estimate per active user per day: Perplexity (~9 regions × $0.005) + Anthropic ranking ($0.002) ≈ $0.05/day = ~$18/year. Before Supabase, Firebase, and hosting.
Recommendation — Freemium:
- Free: today only, 3 regions max, no global headlines, no history
- Premium ($2.99/month or $19.99/year): all regions, global headlines, full history, tune mode, currency rates, custom notify time
At $20/year, API costs are covered at ~1,000 active users and profitable beyond that.