Skip to content

Guide

Deep Links and the App Info Screen in WizeUp

How the WizeUp browser handles wizeup:// deep links, the App Info screen, and retention tracking on Android, with commits and platform references.

Deep Links and the App Info Screen in WizeUp preview

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

The WizeUp browser has three small pieces of plumbing that do a lot of work in combination: the wizeup:// deep-link router, the App Info screen, and a retention tracking path. None of them are visible features you would read about on a store listing, but together they are what makes the app feel like a coherent mobile fact checking app rather than a stack of trend pages. This guide walks through each, with the commits that shipped them.

For readers coming fresh, the product story is in how Fulldive Browser became WizeUp, and the feature guide is in personalized feeds, trends, and daily digest.

Commit f9cce9d25a added wizeup:// deep-link routing in February 2026. On Android, deep links let other surfaces — notifications, emails, the Fulldive Summary server, other apps — link a user directly into a specific WizeUp screen. The official Android docs on deep links and app links explain the platform mechanics.

Why the app has its own scheme matters:

  • Daily digest pushes (commit 3cf6f75e6c) can point to the specific trend in the digest, not just “open the app”.
  • Personalized pushes (commit 26d2fccaf9) can land on the trend detail screen the user is being notified about.
  • Server-side emails or dashboard links can target screens that do not have a web equivalent, such as the AI Chat surface scoped to a trend.
  • Other Fulldive properties can hand users off to WizeUp without losing context, once auth moved to the Fulldive Summary server (commit 522ff7e541).

A wizeup:// URL is not a web URL. It will only open WizeUp, and only if the app is installed. We pair it with standard HTTPS links for surfaces where a fallback is needed — that is the usual Android App Links pattern.

The App Info screen

Commit c0bb2c6c3f added the App Info screen. It is a small in-app surface that does something most apps neglect: it tells the user, from inside the app, what WizeUp is for, what its limits are, and how to reach support.

Specifically, App Info covers:

  • The product’s purpose, phrased carefully (claim review assistance, not truth verdicts).
  • Version information — relevant because the modernization work described in reducing ANR and cold start in a browser has shipped across several 6.x releases.
  • Support contact, including support@fulldive.com and the Fulldive Discord.
  • Links to the project page, privacy policy, and terms of use.

App Info is also the surface where the post-rename identity shows up most cleanly. The rename commit (26bf5abcdb) fixed the notification icon at the same time. App Info is where a long-time FD Browser user sees, explicitly, that the app they have installed is now WizeUp.

The first analytics dashboard

Commit 7a8fd0afbd shipped the first analytics dashboard. The dashboard is an internal surface, not a user feature. We mention it here because the deep-link router and App Info both depend on knowing which screens are actually entered and how often. That is engineering instrumentation, not a profile — see the limits post for the careful framing we keep applying.

Concretely, the dashboard is what lets the team answer questions like “is the daily digest push landing on the right trend via deep link?” or “is App Info being reached from the home feed at all?” These are operational questions. They do not affect what the user sees in the moment.

Retention tracking

Commit 569681c230 added retention tracking. Retention here is standard cohort retention — how many users who install in a given week come back in subsequent weeks. It is not a per-user behavioural file. On a product that has spent a year pivoting its main screen (commit 11fc50e4cf for the 6.2.0 refactor) and renaming itself (commit 26bf5abcdb), retention is the signal that tells us whether the new shape is worth the effort.

We flag this explicitly because the word “tracking” is loaded. In this repository, the commit refers to aggregated retention cohorts tied to product release, not a surveillance product. The App Info screen (c0bb2c6c3f) is the right place to see how Fulldive describes this to users.

Notification icon fix in the rename

The rename commit itself (26bf5abcdb) did two things in one change: renamed “WizeUp Browser” to “WizeUp” and fixed the notification icon that had been inherited from the older branding. Notification icons are rendered by the Android system shade in small monochrome form. Getting the icon wrong is a classic source of low-grade user confusion — a user taps a notification that does not look like the app on their home screen.

Fixing it inside the rename commit is not glamorous, but it is the right place to fix it. By the time the rename lands on a user’s device, both the label and the icon in the shade say the same thing.

How the pieces work together

End to end, here is how a user touches these features without noticing them:

  1. A daily digest push (3cf6f75e6c) arrives. The notification icon is correct because of 26bf5abcdb.
  2. Tapping the notification triggers a wizeup:// deep link (f9cce9d25a).
  3. The link opens straight into the trend detail page (d328d2d8a5) rather than the generic home.
  4. The reader uses AI Chat (3e90b710c3) to interrogate the claim, following the workflow in checking news before sharing.
  5. If the reader wants to understand what the app is and what it is not, App Info (c0bb2c6c3f) is one tap away.
  6. Retention tracking (569681c230) and analytics (7a8fd0afbd) register the session so we can tell, at the cohort level, whether this flow actually works for users.

None of these are features you would list on a Play Store page. All of them are what a mobile fact checking app needs to feel coherent on Android.

Limits

  • Deep links are not a security boundary. Anyone can construct a wizeup:// URL. The app treats incoming links as untrusted input.
  • App Info is descriptive, not a policy document. For the authoritative privacy and terms language, read the linked documents — not the summary on the App Info screen.
  • Retention tracking is not a user-facing feature. We do not claim it is. It is product instrumentation. Treating it as a benefit would be the kind of overclaim our internal publishing notes explicitly warn against.
  • WizeUp is not a fully private browser. The existence of deep links and analytics does not change that. System-level ad and tracker control is a separate tool; see Wize AdBlock VPN.

Where this sits

The full WizeUp product history, including the 6.2.0 refactor and the rename, is in how Fulldive Browser became WizeUp. The AI Chat framing that the deep-link router supports is in what an AI fake news checker can and cannot do. The broader Fulldive ecosystem is in the company story and the projects list.

If you are installing WizeUp for the first time, start at /project/fulldive-browser/. The FAQ covers cross-product questions, and support@fulldive.com is the fastest route to a human answer.

Sources

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