Company Story
From Mobile VR to a Mobile App Ecosystem: The Fulldive Story
How the Fulldive Android app ecosystem grew from a mobile VR app into a family of privacy, browsing, emulator, SMS, and AI agent apps, told through repository history.

Written by the Fulldive product engineering team, based on direct inspection of the repositories listed below.
Fulldive is a mobile app ecosystem for Android that covers VR entertainment, private browsing, ad-blocking, no-root firewall, Android emulation, SMS forwarding, device cleaning, and, most recently, AI agent automation. This post traces how that ecosystem formed. It is drawn from the public repository histories of each app and cross-checked against the current app catalog on the Fulldive apps page.
We are not retelling a marketing story. We are walking through the git history.
2015-2017: The code that predates the brand
Parts of the Fulldive ecosystem live on codebases that are older than the Fulldive brand on them. Two stand out:
- DataGuard (package
com.fulldive.extension.dataguard) — repository history begins in October 2015 and spans 3,936 commits across all refs, including roughly a decade of firewall releases, FAQ maintenance, and Android compatibility work before and after Fulldive integration. - WizeSMS / Dive SMS (package
com.fulldive.extension.divesms) — repository history begins in February 2015 with 2,474 commits. Most of the first five years are foundational SMS/MMS reliability work: notifications, MMS sending, Realm migration, default-SMS prompts, search, blocking.
That early history matters because it shapes what these apps are good at today. DataGuard is a firewall built on a long-maintained no-root firewall lineage, not a fresh Fulldive write. WizeSMS is an SMS app built on years of Android messaging behavior, not a greenfield messenger.
2017-2020: Fulldive VR and the entertainment roots
The Fulldive brand starts in mobile VR. The Unity repository for Fulldive VR (package in.fulldive.shell, repo fulldiveVR/fulldive-unity) begins in April 2017 and accumulates 2,220 commits through October 2024.
The 2020-2022 commits are the most telling. They show a real mobile VR product, not a demo:
- Video playback with desktop user agent (
3a208241) so users could watch video content meant for larger clients. - YouTube-style links opening in the in-app video player (
62c1fd92). - Cinerama mode (
7a7f56f9) and browser brightness shader work (92e73443). - Video reactions, comments, and bookmarks (
e53affb9and related commits). - WaveVR and Vive SDK adaptations as the mobile/standalone headset market shifted.
VR is where Fulldive’s name on Google Play came from. But the app ecosystem grew outward from it, because mobile users needed more than headset content.
2020-2022: The extension family takes shape
Between 2020 and 2022, Fulldive’s engineering focus broadened from a single VR app to a family of Android utilities. The repository evidence is clear:
- Wize AdBlock VPN —
fulldiveVR/FulldiveExtension.AdShield, an ad-blocking codebase with history back to 2016 and recent DNS/VPN-service integration. - Full Cleaner —
fulldiveVR/FulldiveExtension.JunkRemover, where the Fulldive-specific extension period (2021-2022) adds app ID changes, permission handling for Android content providers, launch-from-main-app flows, and version bumps through 1.0.8 (commits5514121,705a3e7,fde533f,c2a9d6c,52c307f). - Dive SMS extension work — commits
ee511c80(Dive SMS rename) andfd5a1ae9(removed payments, bumped 1.0.1) mark the SMS app joining the Fulldive extension family. - One Emulator / Pro Emulator —
FulldiveExtension.FullRoidshows Fulldive-specific release commits from 2022 onward: updated cores, target SDK updates, version 1.0.4/1.0.6, Discord promo (74852fd8).
The shared pattern is: take a mature Android codebase, add Fulldive branding and package IDs, handle the platform permission/launch work needed to live alongside the main Fulldive app, ship a release. The “extensions” language on fulldive.com describes exactly this. (See What are Fulldive extensions? for the short version.)
2022-2024: Maintenance years
A lot of app history is not new features. It is keeping the app alive on a changing platform. Fulldive’s repositories in 2022-2024 show this directly:
- Fulldive VR imports portal VFX and screen logic (
90d360d0), restores legacy feed and dive requests (963bc03e,ba6dc4a6), fixes the build pipeline (01f20dc8,6f220ec5), and in 2024 migrates to a newer Unity version (dfc07c05). - DataGuard ships Android 13 notification permissions (
4165205e) and runs through a long 2.30x release cadence. - One Emulator migrates the search, systems, and games screens to Jetpack Compose (
38ddf7fa), fixes save-sync crashes (52e9487d), and handles melonDS save imports (28a1f115).
This period produced less visible change for users, but it is why older Fulldive apps still install and run today.
2025: The modernization sprint
2025 is the year several Fulldive apps all had to make the same platform jumps. In the repositories, the timing lines up:
- Wize AdBlock VPN: 16 KB library alignment (
ead5d3b1), AGP/Gradle update (585b28e8), graceful VPN teardown (886a3f2c), SDK 36 (b8315876), version 1.0.17 (7a6c12d9). Then Privacy Pulse and weekly report features (c8f7f968,5daecf90,8c4a9eca). - DataGuard: SDK 35 preparation (
2821d5e0), 16 KB alignment (b2af3518), 2.334 release (cdc04c9f), app-name consistency work (f008c1b2). - One Emulator: Game Activity migration to Compose (
def0215f), gamepad layout in Compose (47c9c8c3), quick save/load and fast-forward shortcuts (86d4d1b1), core bumps and save-path migration (be65800d,f71aade4). - WizeSMS: MMS/SMS reliability and default-SMS banner work (
68ecf707,5895a312,3838a63b,0f382e4a).
16 KB page alignment and SDK 35/36 were Android platform requirements Google set for 2025. Fulldive apps absorbed them across the catalog at roughly the same time. That is the engineering cost of running an ecosystem rather than one app.
2025-2026: The WizeUp pivot and the AI agent
Late 2025 into 2026 is where the Fulldive ecosystem started to change shape again.
FD Browser becoming WizeUp. The browser codebase (fulldiveVR/fulldive-android-apps, 18,587 commits since May 2016) spent December 2025 through February 2026 shifting toward AI-assisted news and trend workflows. Main-screen refactor and 6.2.0 (11fc50e4cf), trends comments (bcf547c606), rising trends (e098f17ce4), retention tracking (569681c230), App Info screen (c0bb2c6c3f), daily digest push (3cf6f75e6c), the WizeUp rename itself (26bf5abcdb), personalized feeds and pushes (ba78fd4c6a, 26d2fccaf9), refactored AI Chat (3e90b710c3), wizeup:// deep links (f9cce9d25a), and performance work to reduce ANRs (3166bfe28f). By March-April 2026, the app migrated away from api.fdvr.co (fd0e6206a8) and moved auth to the Fulldive Summary server (522ff7e541).
WizeSMS becoming a forwarding utility. December 2025 adds SMS-to-email forwarding via Gmail OAuth (dd629f2f), a forwarding settings screen (4c1ec87b), and SMS-to-Telegram via Cloud Function (fa8b722b).
LikeClaw AI Agent & Automation. Package com.fulldive.likeclaw. The local repository goes from first commit on 2026-02-11 to 141 commits by the end of March: chat-based dashboard in Flutter (9632105), VFS files and skills screen (2970709), rich chat and background polling (c3001bf, 09ee58f), model selection and billing (7cf67c3), inbox notifications (bf94935), tool-call and generated-image display (882aa78), the LikeClaw rebrand itself (bfb1dda), iOS TestFlight/App Store workflows (eacfed4), and StoreKit 2 transaction handling (0b9f7db). A mobile AI agent shipped in roughly seven weeks on top of the rest of the ecosystem.
One Emulator in the same window added Citra hardware shader cache (640cdc59), experimental Citra save-state support (1030d028), new 3DS core support (e9ca6f9b), version 1.9.5 (5e265141), and a free game catalog (809ab678) served by the separate fulldiveVR/FullRoid.Games repository.
What has stayed constant
Across a decade and more than ten repositories, a few things have not changed:
- Android-first. Every Fulldive app currently maintained has Android as its primary platform. Some apps add iOS/macOS later (LikeClaw’s TestFlight workflow, AdShield’s macOS private-DNS work), but Android is where the ecosystem lives.
- Extensions over monolith. Fulldive ships many small apps that share branding and a main-app launch path, rather than one giant app. Full Cleaner’s content-provider permission work (
6a42c35) and “permission check from main app” commit (bb1523b) are the clearest artifact of that design choice. - Community support path. Multiple 2025-2026 commits across repositories add Discord community links (
60546414in DataGuard,c8952402in One Emulator,dfc606b3in WizeSMS). Support is centralized around Discord andsupport@fulldive.com, not scattered per-app. - Honest limitations. The internal publishing notes for each app explicitly say things like “do not promise complete ad blocking,” “do not claim fake-news detection is definitive,” and “do not claim universal console support.” We try to carry that same honesty into product copy.
What is next
The current priorities, visible in the most recent commits:
- Continuing WizeUp’s move from a browser frame toward AI-assisted reading and trend review, with the limits of that framing called out clearly.
- Broadening LikeClaw from a chat dashboard into an AI agent workspace, with sandboxed execution treated as a real engineering question rather than a marketing line.
- Keeping DataGuard, Wize AdBlock VPN, One Emulator, WizeSMS, and Fulldive VR running through whatever Android’s 2026-2027 platform changes bring.
If any of the individual apps interest you, the Fulldive apps page links to each one, and the FAQ covers the ecosystem-level questions. You can reach the team at support@fulldive.com or via the Fulldive Discord community linked from each app.
Sources
- Internal repository evidence briefs (
website/docs/app-evolution/in thefulldive-comrepo), last researched 2026-04-13. - App catalog on this site: the Fulldive apps page.
- Android platform references for 16 KB alignment and SDK 35/36 requirements: Android Developers — 16 KB page size and Android Developers — target API levels.
- Schema references for this article: schema.org/Article and schema.org/Organization.
Last updated: 2026-04-16. Dates, version numbers, and commit hashes are drawn from Fulldive repository histories inspected on 2026-04-13. Before acting on any specific app version, package ID, or feature mentioned above, check the current app-store listing linked from the Fulldive apps page.