Skip to content

Product History

How WizeSMS Evolved From SMS Messenger To Forwarding Utility

The WizeSMS app history in brief: from 2015 SMS/MMS foundations as Dive SMS through Fulldive extension releases to Gmail and Telegram forwarding in 2025-2026.

How WizeSMS Evolved From SMS Messenger To Forwarding Utility preview

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

The WizeSMS app history, grounded in the repository

If you’re trying to understand how WizeSMS evolved from messaging to forwarding workflows, the cleanest answer is the git log. WizeSMS (package com.fulldive.extension.divesms, previously Dive SMS) has a repository history running from 2015-02-21 to 2026-01-23, with 2,474 commits across all refs. That is a decade-plus of Android SMS and MMS work on a single codebase.

This is the short version of that history, tied to the commits that mark each turn.

2015-2020: the SMS/MMS foundation years

The first five or so years of the codebase are foundational messaging work. Notifications, MMS sending, search, blocking, the Realm data layer, default-SMS prompts, notification-channel adaptations as Android’s rules changed. None of this is glamorous, and none of it is visible as “features” in a modern release-notes screen.

But this is the period that produced an SMS/MMS app that actually works across OEMs, Android versions, and carrier quirks. Anything built on top in the 2025-2026 product direction is built on this base.

2021: becoming Dive SMS and joining Fulldive’s extension family

Two commits mark the app’s entry into Fulldive’s lineup of “extensions”:

  • ee511c80 — Dive SMS. The rename that signaled the app’s alignment with Fulldive’s extension family — small Android utilities shipped alongside the main Fulldive app, sharing branding and a common launch path. Our earlier post What are Fulldive extensions? describes that model.
  • fd5a1ae9 — removed payments and bumped 1.0.1. Trimming the app down to the core messaging experience, away from monetization paths that didn’t fit the extension model.
  • a97c5069 — 1.0.3 bump and copyright updates. The house-keeping release that comes with joining a larger ecosystem.

This is when the codebase became recognizably a Fulldive app, even though the underlying engineering lineage reaches further back.

2023: platform catch-up

Two commits stand out in the 2023 stretch because they’re the kind of platform-compatibility work that keeps an SMS app alive across Android releases:

  • 9c949f61 — push notification fix on SDK 31. Without this, notifications on Android 12 would have regressed.
  • 559e471d — scheduled SMS fix. A single commit hash, a lot of edge cases behind it.

The full SMS and MMS reliability post goes deeper on why this kind of work is load-bearing for any messaging app.

2025-11: the reliability sprint

November 2025 was dense with reliability commits that set the stage for a product direction change:

  • 68ecf707 — critical MMS/SMS reliability fixes.
  • 5895a312 — MMS error handling.
  • 3838a63b — default SMS warning banner, which surfaces when WizeSMS isn’t the active SMS handler.
  • 0f382e4a — SMS/MMS reliability and debugging tooling.

You do not add a “default SMS” warning banner unless you’re about to build features that depend on the role. You do not invest in debugging tooling unless you expect to field reports from a broader surface than before. This sprint is where the forwarding direction became visible in the code even before the forwarding features landed.

2025-12: the forwarding direction

December 2025 is where WizeSMS stopped being only a messenger:

  • dd629f2f — SMS to email forwarding with Gmail OAuth. Auth goes through Google’s consent flow instead of a pasted app password. See the Gmail OAuth scopes reference for the scope model in general.
  • 4c1ec87b — dedicated forwarding settings screen. Both destinations live in one place.
  • fa8b722b — SMS to Telegram via Cloud Function. A Fulldive-hosted relay bridges to the Telegram Bot API so the client never holds bot tokens.

These three commits, in that order, are the product pivot: WizeSMS now serves both traditional messaging and forwarding workflows for users who want incoming SMS to land somewhere other than only their phone.

2025-12 to 2026-01: polish, privacy note, and stability

After the core forwarding commits, the next weeks were polish and honesty:

  • e6815676 and a62b2d44 — forwarding translations. Forwarding UI is high-stakes copy; it has to read clearly in every supported language.
  • a53b2673 — forwarding status and failure notifications. A failed forward is visible, not silent.
  • 150204e5 — email test message button. Confirm delivery before relying on it.
  • 42f44224 — privacy note. Forwarding sensitive messages is a privacy decision; the app surfaces that at the point of opt-in.
  • 432b22cf — Realm migration nullability fix. The kind of bug that only shows up for some users on upgrade, the worst time for an SMS app to misbehave.

The privacy note (42f44224) is the commit we point to when people ask how we think about forwarding. Read forwarding OTPs and verification codes: privacy tradeoffs for the longer version of that argument.

2026-01: community support path

  • dfc606b3 — Discord community link added inside the app. Support now routes through Discord and support@fulldive.com consistently with other Fulldive apps.

What the arc says about WizeSMS

Three things follow from the history:

  1. The base is an SMS/MMS app, not a forwarder with messaging bolted on. You can turn off forwarding and still have a capable SMS client, because that’s what the first decade of the codebase built.
  2. Forwarding is opt-in and recent. The Gmail and Telegram paths landed in December 2025, behind a dedicated settings screen, with status notifications and an explicit privacy note. Nothing in the repository suggests forwarding is enabled without the user choosing it.
  3. Platform work is continuous. SDK 31 push fixes, Realm migrations, default SMS banners, MMS reliability — the 2022-2026 stretch is full of this work because maintaining an Android messaging app is a continuous job, not a one-time project.

Privacy tradeoffs

Forwarding SMS to email or Telegram changes your privacy and authentication surface. That is true whether the destination is Gmail, a self-hosted IMAP server, or a Telegram bot. WizeSMS makes forwarding opt-in and shows a privacy note (42f44224) at configuration time. If you forward OTPs or banking alerts, harden the receiving account first: hardware 2FA, session review, and narrow forwarding rules rather than forwarding every inbound text. The dedicated OTP forwarding post expands on this.

WizeSMS is listed on the Fulldive apps page. The About and FAQ pages cover ecosystem-level questions. Contact: support@fulldive.com or the Discord link inside the app (dfc606b3).

Sources

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