Samsung Messages alternative app: what it restores and skips

As of this week, a Samsung Messages alternative app called Messages by OzarksMade is sitting in open beta on Google Play, with a public launch set for 14 days after its testing Google Group hits 12 members and a post-launch price of $0.99 (Notebookcheck, 1 day ago; Android Headlines, 1 day ago). Treat that as a snapshot, not a finished product. Betas shift, thresholds get hit or missed, and pricing plans change before launch.

The timing isn't a coincidence. Samsung retired Samsung Messages for U.S. Galaxy phones running Android 12 or later earlier this month, steering longtime Galaxy owners toward Google Messages as their default texting app (Android Headlines, 1 day ago). Once that cutoff arrived, the old app was left doing little more than handling emergency contacts, the fate Samsung had already flagged months earlier (Android Police, 3 months ago). Owners of a Galaxy S26 or newer never had the choice to begin with. Those phones shipped without Samsung Messages installed and can't pull it from the Galaxy Store even if they wanted to (Android Police, 3 months ago).

That's the gap OzarksMade is stepping into. The app rebuilds the look of Samsung Messages convincingly, but its RCS features still run through Google Messages behind the scenes. It's a facelift on Google's infrastructure, not a Samsung-independent revival, and every section below tests what that trade-off means once you actually install it.

What Messages by OzarksMade is, and who made it

It's an unofficial, third-party Android app built to reproduce the discontinued Samsung Messages interface for U.S. Galaxy users (Android Headlines, 1 day ago). That distinction shapes every promise the app can and can't keep.

The design work is where it earns points. It's a Samsung-style messaging app down to the details: rounded cards, collapsible headers, chip filters, conversation categories, and a dedicated trash bin for recovered texts, the same visual and organizational language One UI users grew accustomed to (Notebookcheck, 1 day ago). If you spent years navigating Samsung's chat categories and swipe filters, this will feel immediately familiar.

Weigh one thing before granting the app access to your texts: developer OzarksMade has only one other app published on Google Play, and this project currently sits in open beta, not a finished, publicly reviewed release (Notebookcheck, 1 day ago). That's not automatically disqualifying, but it's worth reading the rest of this article before handing anything over.

What OzarksMade has built is a front-end skin layered on top of existing messaging systems, not a Samsung-engineered service resurrected from scratch. Keep that in mind as the modes get more specific.

How the two modes work

The OzarksMade Messages app splits into Standalone Mode and Companion Mode, and the difference between them determines what you're actually getting.

(Table sourced from Android Headlines, 1 day ago, and Notebookcheck, 1 day ago)

Companion Mode needs a partner because Google restricts direct third-party access to its RCS backend, so it keeps Google Messages running silently in the background to actually push and pull RCS traffic (Android Headlines, 1 day ago). OzarksMade's app supplies the interface; Google Messages supplies the plumbing.

One piece of backend context is worth including. The developer states that Samsung Messages itself relied on Google's Jibe infrastructure for seven years, meaning RCS traffic in Companion Mode follows a familiar path rather than an untested one (Notebookcheck, 1 day ago). That's a developer claim relayed by tech outlets, not an independent audit, and it says nothing about whether OzarksMade matches Samsung's privacy practices or reliability standards.

There's a practical upside worth flagging, with the same caveat attached. Samsung Messages' old RCS setup was carrier-dependent, and it broke and fell back to plain SMS/MMS whenever a carrier's own servers faltered (Android Police, 3 months ago). Because Companion Mode routes through Google's own Jibe platform rather than individual carrier infrastructure, it may sidestep that specific failure mode, though this hasn't been independently tested.

That dependency is the app's real constraint: however convincing the interface looks, Companion Mode can't function without Google Messages quietly running underneath it. What nobody has confirmed yet is how cleanly the two apps share default duty on the same phone, which is exactly what the next section walks through.

Try it safely: a testing checklist for this Samsung Messages alternative with RCS

Before trusting this app with daily texting, work through it in order rather than diving straight into Companion Mode.

1. Confirm your phone qualifies. The shutdown only affects U.S. Galaxy phones on Android 12 or later. Devices still running Android 11 or older are unaffected and keep Samsung Messages working as it always has, so there's no urgent reason to install anything else (Android Police, 3 months ago).
2. Note your current default messaging app and message history before switching anything. If you need to revert, you'll want a clean starting point to compare against.
3. Install the beta from Google Play and join the testing Google Group if the app prompts you to; that group's membership count determines when public launch happens.
4. Start with Standalone Mode if the interface is the only draw. Only move to Companion Mode once you've decided RCS features are worth the added dependency on Google Messages.
5. Read the app's current Play Store listing and onboarding screens closely for any language about default-app status. None of the reporting on this app confirms whether it can hold default SMS/RCS status cleanly while Google Messages runs in the background, or whether the two apps end up competing for that role (Android Headlines, 1 day ago; Notebookcheck, 1 day ago).
6. Send a handful of test messages, both plain SMS and, if you're on Companion Mode, RCS texts to someone who also has RCS enabled. Watch whether Google Messages also surfaces a notification for the same text; that's the clearest sign of the two apps stepping on each other.
7. Know your way back. If either mode causes problems, Android's own settings let you set Google Messages back as your default SMS/RCS app at any time, the same app Samsung is already steering displaced users toward (Android Headlines, 1 day ago). That path doesn't depend on anything OzarksMade's app does or doesn't do correctly.

What this app can and can't restore

Everything below applies only to the Android 12-and-later population the shutdown actually affects; devices still on Android 11 or older keep Samsung Messages working without any of this (Android Police, 3 months ago). For everyone else, here's what this Samsung Messages replacement plainly cannot bring back:

• Any built-in Samsung ecosystem integration. This is an independent developer's project, not a Samsung release, and it carries none of Samsung's own account-level backing (Android Headlines, 1 day ago).
• Full independence from Google. Even in Companion Mode, Google Messages has to stay installed and running for RCS to function at all (Android Headlines, 1 day ago). There's no version of this app that removes Google from the equation.
• Wearable sync tied to older hardware. Tizen-based Galaxy Watches released before the Watch 4 can't run Google Messages at all (Android Police, 3 months ago). Since Companion Mode depends on Google Messages running in the background, installing OzarksMade's app on your phone doesn't change what those older watches can sync.

There's also a permissions question worth weighing independent of how well the app performs. Installing this means handing SMS/MMS access to a small, largely unproven developer, which is a reasonable point of hesitation on its own (Android Headlines, 1 day ago).

One more caveat: closely mirroring Samsung's interface, icons, and branding raises a plausible, unconfirmed risk of intellectual-property scrutiny down the line (Android Headlines, 1 day ago). That's a risk baked into how the app was built, not a report that Samsung has acted on it.

Conclusion

Standalone Mode is the lower-risk pick if the interface alone is the draw. It adds no new dependency and asks nothing of Google Messages. Companion Mode is worth trying only after working through the checklist above, since the app's own current listing, not this reporting, is where the default-status question actually gets answered.

The real test for this unofficial Samsung Messages app isn't how well it mimics One UI on day one. It's whether OzarksMade clarifies default-app behavior as the beta matures, stabilizes into a public release, and holds up if Samsung or Google ever push back on how closely it borrows from either company's work.