Every morning used to start the exact same way for me:
- Open Hacker News
- Skim 5 engineering blogs
- Check Substack newsletters
- Drown in 20 open tabs before writing a single line of code šµ
Between algorithmic social media feeds pushing clickbait and legacy RSS readers (like Feedly) turning into expensive enterprise suites ($12/mo) with paywalled shortcuts, staying updated became exhausting.
I wanted something lightweight, lightning-fast, and built for people who value deep focus.
So I built Frontpagee.
What is Frontpagee?
Frontpagee is a modern, distraction-free RSS reader and feed aggregator. It combines clean typography with power-user productivity features so you can read the open web without algorithmic noise.
ā” Key Highlights
- Pure Chronological Feed: No secret recommendation engines or sponsored clutter. You only see updates from sources you subscribed to.
-
Power-User Keyboard Navigation: Move through articles with Vim-inspired keys (
Jfor next,Kfor previous,Oto open). - 30-Second OPML Migration: Bring your existing subscriptions from Feedly, Inoreader, or any RSS app in one click.
- Curated Topic Hubs: Pre-curated reading lists for React, AI Research, DevOps, and Engineering Architecture blogs.
- Offline-Ready PWA: Install it as a desktop or mobile progressive web app with instant caching.
The Tech Stack
I built Frontpagee using:
- Frontend: React, TypeScript, Tailwind CSS, Vite
- Backend & Data: Firebase (Firestore real-time sync, Auth, Cloud Functions)
- Summaries: Google Gemini API for fast, contextual TL;DRs
Try It Out
Frontpagee is completely free to get started:
š Try Frontpagee Live (frontpagee.in)
I would love to get your honest feedback. What does your current morning reading stack look like, and what features would make your RSS workflow better?
Drop your thoughts in the comments below! š
Top comments (1)
For the offline-ready part, I'd distinguish caching the app shell from having the article itself available. A useful check: open a feed, go offline, reload the PWA, and try an article you haven't opened before. Showing "not downloaded" is better than an empty reader that looks like a feed failure.
With Firestore sync, I'd also try marking an article read offline on one device while changing its saved state on another, then reconnecting. Those are separate bits of state, so neither change should undo the other. Does the UI show which articles are actually available offline?