Personalized Feeds, Trends, and Daily Digest in WizeUp

Written by the Fulldive product engineering team, based on direct inspection of the repositories listed below.

If you are looking at WizeUp and wondering how the home feed, trend pages, comments, and daily digest push fit together — and where the AI-assisted browsing on Android happens — this guide walks through the full flow. It is grounded in the fulldiveVR/fulldive-android-apps repository, with commit hashes where the changes landed. WizeUp positions itself as a news bias awareness app rather than a verdict machine, and this post explains what that means feature by feature.

For the broader product history, see how Fulldive Browser became WizeUp. For the honest limits of AI claim review, see what an AI fake news checker can and cannot do.

The main screen, after the 6.2.0 refactor

The WizeUp home feed as users see it today is the result of a December 2025 refactor. Commit 11fc50e4cf rebuilt the main screen and cut release 6.2.0. That version is the baseline for every feature in this post.

What changed, in plain terms: the old FD Browser home was oriented around tabs and a search surface. The 6.2.0 home is oriented around topics — what is trending, what is rising, what has new comments. The URL-bar browser is still there, but it is no longer the primary job of the home screen.

Trends, rising trends, and trend detail

Three commits stitch the trends experience together:

Commit bcf547c606 introduced comments on trends, so a trending topic is not just a headline but a short social surface around it.
Commit e098f17ce4 added rising trends, which surface topics that are gaining attention fast, not just the current top topics.
Commit d328d2d8a5 shipped the trend detail screen with internationalisation sync. Trend detail is where a reader lands when they tap a topic — it aggregates the headline, context, comments, and the AI Chat surface described below.

The i18n sync is worth calling out because it lets the trend detail page render in a reader’s language without re-building the app. For a product that hopes to help users review claims across languages, that plumbing is the difference between “works in English” and “works for an international audience”.

Personalized feeds

Commit ba78fd4c6a introduced personalized feeds. Personalization here means the feed adapts to what you read, comment on, and linger on, not a social-graph feed. There is no “who to follow” mechanic.

A few things we want to be clear about with personalization:

It is a ranking on top of trending content, not a replacement for it. If a topic is trending broadly, it still shows up.
It is opt-in to signed-in state; the signed-out experience is closer to a pure trends feed.
We treat the personalization signals as product instrumentation, not as a profile we sell or syndicate. That is consistent with the caution we keep raising in the limits post.

Personalized and daily digest pushes

Push is where personalization most visibly reaches the user.

Commit 26d2fccaf9 added personalized pushes. These are notifications tied to topics or trends the reader has shown interest in, rather than generic “new article” blasts.
Commit 3cf6f75e6c added handling for a daily digest push. The daily digest is a single notification that summarises what happened on the topics you follow, rather than many small pings through the day.

Push reliability is a separate engineering concern — Android delivers notifications unreliably under certain OEM battery-saving behaviours. We cover the reliability work in a separate engineering post, reducing ANR and cold start in a browser.

The digest design choice is intentional. If the goal is to help readers review claims carefully, waking their phone every hour is counterproductive. One summary push a day fits the job better.

Where AI Chat plugs in

AI Chat (refactored in commit 3e90b710c3) is not a separate tab. It is attached to trend detail and article context. That is why it counts as AI-assisted browsing on Android rather than “a chatbot we bundled”.

In practice, AI Chat lets a reader:

Summarise the specific claim being made in the trend.
Ask for the most likely primary sources to check it against.
Check whether the framing of a post matches the underlying article.

The usage pattern we care about is described in checking news before sharing with WizeUp. AI Chat is the instrument; the workflow is the point.

How the pieces work together, in order

End to end, a typical WizeUp session in 2026 looks like this:

Open the app. The 6.2.0 home feed (11fc50e4cf) shows trending topics, with rising trends (e098f17ce4) highlighted.
If the reader is signed in, the feed is reranked by personalization (ba78fd4c6a).
Tap a topic. The trend detail screen (d328d2d8a5) opens, with localized headline and context.
Read the trend. If there is a claim worth interrogating, use AI Chat (3e90b710c3) to extract it and look for verification angles.
Optionally leave a comment (bcf547c606) or bookmark the trend.
Later, the daily digest push (3cf6f75e6c) lands as a single summary, and optionally a personalized push (26d2fccaf9) on a topic the reader has followed.

Nothing about this flow requires treating WizeUp as a truth oracle. It is a reading environment that makes claims easier to see and harder to share by accident.

Limits

A few honest notes before you rely on the feed for serious reading:

Personalization can narrow what you see. If you read mostly one angle, rising trends (e098f17ce4) exist partly to counter that, but they are not a full corrective. Users who want broader exposure should still look at the unpersonalized trends surface.
The AI Chat feature in trend detail is assistive. See what an AI fake news checker can and cannot do for the detail.
Push delivery is not guaranteed on Android. OEM battery savers, Doze, and user settings all affect whether the daily digest actually arrives. Reliability work is ongoing; see the ANR and cold start post.
WizeUp is not a fully private browser. We do not claim otherwise. If the job is system-level ad and tracker control, pair it with Wize AdBlock VPN.

Getting started

WizeUp installs from Google Play via /project/fulldive-browser/. If you are coming from the old FD Browser, the same account works — the auth migration (covered in how Fulldive Browser became WizeUp) routes existing sign-ins through the Fulldive Summary server. The projects list and FAQ cover cross-product questions.

Sources

Last updated: 2026-04-16. Commit hashes and version numbers are drawn from Fulldive repositories inspected on 2026-04-13.