How Fulldive Browser Became WizeUp: A Product History

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

This post answers one question: how Fulldive Browser became WizeUp. The short answer is that the Android app known as FD Browser / Fulldive Browser (package com.fulldive.mobile) spent late 2025 and early 2026 shifting from a general mobile browser frame toward an AI-assisted news, trends, and claim-review workflow — and, in January 2026, it renamed itself WizeUp. The long answer is written into the repository history, which is what this post walks through.

The repository we inspected

The Android app that is now WizeUp lives in fulldiveVR/fulldive-android-apps. Its local history spans 2016-05-27 to 2026-04-03, with 18,587 commits across all refs. That long history is important context: WizeUp is not a new app. It is a long-running browser codebase that turned into something more specific.

The Play Store name today is “WizeUp: Fake News Hoax Check”. The package name did not change. If you have had the app installed for years, it has been through every stage described below.

Late 2025: the feed and trends refactor (6.2.0)

The first visible move toward WizeUp happened in December 2025, before the rename. Commit 11fc50e4cf refactored the main screen and cut release 6.2.0. Around it, the team shipped:

Trends comments (commit bcf547c606).
Rising trends on the home feed (commit e098f17ce4).
A trend detail screen with internationalisation sync (commit d328d2d8a5).

Read end-to-end, these commits describe a browser product whose home screen is no longer “tabs and a search box”. It is a feed of trending topics, with comments, detail pages, and translations. That is the product shape WizeUp eventually ships under its new name.

January 2026: the rename

The rename landed in January 2026. Commit 26bf5abcdb renamed “WizeUp Browser” to “WizeUp” and fixed a notification icon that still referenced the older branding. It is a small commit in lines, but it is the moment the app’s identity changes: the Google Play listing, the in-app title, and the push notification pipeline all become WizeUp in one pass.

The rename sits in the middle of a broader January-February push:

Commit 569681c230 added retention tracking.
Commit 0536b97ea8 added analytics for the home feed and trend detail.
Commit c0bb2c6c3f introduced the App Info screen.
Commit 3cf6f75e6c wired a daily digest push.
Commit 7a8fd0afbd shipped the first analytics dashboard.
Commit ba78fd4c6a introduced personalized feeds.
Commit 26d2fccaf9 added personalized pushes.

Those are engineering artifacts, not user-facing features on their own. We treat them as instrumentation: ways to tell whether the new feed and trend flows are actually used, not a privacy story. See the “Limits” section below for why we are careful with that language.

Deep-link routing also moved over: commit f9cce9d25a added a wizeup:// scheme, so other surfaces (emails, notifications, the Fulldive Summary server) can link into specific WizeUp screens. The separate post Deep links and App Info in WizeUp covers how that routing works.

February 2026: AI Chat and performance work

February 2026 is the point at which the “AI browser” framing starts to show up in code. Commit 3e90b710c3 refactored the AI Chat feature. The chat is scoped to trend and article context — it exists so a reader can ask questions about the claim in front of them, not as a general chatbot. The companion post What an AI fake news checker can and cannot do is honest about what that framing means in practice.

In parallel, the team started paying down performance debt. Commit 3166bfe28f is labelled as a performance refactor aimed at reducing Application Not Responding (ANR) errors. We covered the engineering details in Reducing ANR and cold start in a browser.

March-April 2026: version 6.12.0 and the backend move

Between March and April 2026, two things happened that you will not notice as a user but that matter for the long-term shape of the app.

Architecture refactors. Commit 1139255e9f migrated the app away from Moxy and onto Android’s ViewModel. Commit d4da24b7ff migrated asynchronous code from RxJava to Kotlin coroutines. Both follow current Android guidance from Android Developers on ViewModel and on coroutines. They matter because they are what lets smaller, leaner feature teams keep shipping without re-learning the old browser’s idioms.

Backend consolidation. Commit fd0e6206a8 removed dependencies on api.fdvr.co. Commit 522ff7e541 migrated authentication to the Fulldive Summary server. For most users this means their sign-in flow now runs through Fulldive’s newer backend rather than the legacy FD-era API.

Version 6.12.0. Commit 68782a0368 bumped the app to 6.12.0. That is the version line WizeUp shipped in spring 2026. Version 6.2.0 in December 2025 (commit 11fc50e4cf) and 6.12.0 in April 2026 bracket the rename and the modernization sprint cleanly.

What a FD-Browser veteran will notice

If you installed Fulldive Browser years ago and only recently opened it again, here is what has changed, in repository terms:

The home screen is a feed of trending topics, not a bookmarks-and-search surface (11fc50e4cf, e098f17ce4).
There is a trend detail screen with its own comments, translations, and analytics (d328d2d8a5, bcf547c606, 0536b97ea8).
The app is called WizeUp (26bf5abcdb).
AI Chat is scoped to trends and articles, not general purpose (3e90b710c3).
Deep links use the wizeup:// scheme (f9cce9d25a).
Sign-in runs through the Fulldive Summary server (522ff7e541).
The api.fdvr.co dependency is gone (fd0e6206a8).

The package ID (com.fulldive.mobile), the account continuity, and the underlying browser stack are the same.

Limits

A few things we want to be explicit about:

WizeUp is not a “fully private browser.” We have not re-reviewed and re-certified every tracking surface since the rename, and treating the app that way would be an overclaim. If private browsing is the job-to-be-done, pair WizeUp with a system-level tool like Wize AdBlock VPN and check its current privacy policy.
The AI Chat and trend review flows are assistive, not definitive. They help a reader form questions about a claim. They do not guarantee that a claim is true or false.
Analytics commits (569681c230, 0536b97ea8, 7a8fd0afbd) are product instrumentation, not a feature we are selling to users. They let the team see whether the new feed shape is working.

Where this fits

The WizeUp rename is part of a broader pattern across the Fulldive app catalog, described in the Fulldive company story and the Fulldive extensions explainer: long-running Android codebases, repositioned as their jobs-to-be-done got clearer. WizeSMS went from a messenger to a forwarding utility on roughly the same schedule, for the same reason.

If you want to try WizeUp, the product page is /project/fulldive-browser/. If you want to ask us something about the history or the scope of the AI features, support@fulldive.com works, and so does the FAQ.

Sources

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