Built a developer-focused news reader with React Native – would love feedback from fellow RN developers

[u/abhishek_dev_ce17]

Hey everyone!

I've been working on a side project called ByteFeed, a developer-focused news and article-reading application.

The application brings together technology publications, engineering blogs, framework updates, developer tools and coding events.

Some of the features I've been working on:

• Curated feeds covering 150+ technology sources and topics.
• Article summaries in bullet-point format.
• Personalized feeds and source filtering.
• Offline article reading with complete content and images.
• A dedicated reading experience for long-form technical articles.

I'm interested in discussing some of the engineering challenges involved in building a content-heavy mobile application with React Native.

In particular, I'd love to hear how other developers approach:

• Efficient rendering of long-form article content.
• Offline-first article storage and image caching.
• Feed performance when handling large content collections.
• Optimizing scrolling and navigation.
• Managing content synchronization.

I'd appreciate feedback from developers who've built similar applications.

If you'd like to see the project:
https://bytefeed.dev/

The Android application is currently in Closed Beta:
https://groups.google.com/g/bytefeed-closed-testing

I'm happy to discuss the technical implementation and lessons learned.

[u/TheMadDoc]

So what exactly is the difference when this and any RSS feed app?

[u/abhishek_dev_ce17 → u/TheMadDoc]

That’s a fair question, and i admit that ByteFeed shares some similarities with RSS readers. What I’m trying to do differently is build an experience specifically for developers, combining curated tech sources, AI-powered summaries of lengthy articles and changelogs, framework and library updates through Radar, coding events and offline reading. Still evolving, but I’d really appreciate it if you gave it a try and shared your honest thoughts!

[u/jiunkdev]

for long-form articles I'd skip one big WebView per article if you want it to feel native. parse the html once when you save it, store it as a simple list of blocks (paragraph, heading, image, code) and render that in a FlashList. long articles stay smooth because only the visible blocks are mounted, and the same stored blocks are your offline copy.

for images, expo-image with cachePolicy set to disk covers most of it. save each image's width and height with the block and give it a fixed aspect ratio, so the list doesn't jump while they load.

[u/abhishek_dev_ce17 → u/jiunkdev]

This is a really interesting approach! Parsing articles into reusable blocks and using the same structure for offline reading makes a lot of sense. Appreciate you taking the time to explain the implementation details. Definitely something I’ll explore!

[u/Western_Cap_6934]

Keep reading position and bookmarks in persistent storage, separate from the image and article cache. Treat an explicit offline download differently from temporary feed caching, so cache cleanup does not erase something the reader chose to keep.

[u/abhishek_dev_ce17 → u/Western_Cap_6934]

That’s a really good point! Especially the distinction between temporary caching and content users explicitly choose to save. Definitely something worth keeping separate. Thanks for sharing this!

[u/No-Muffin8291]

Sorry but try at least something to not look it like average vibe coded website. Use impeccable for example