Abstract
Messages has a large installed base and a loud, specific user backlash: people say ads interrupt the one job a texting app must do, while reliability, default-SMS setup, MMS, photos, grouping, and familiar Samsung-style features feel worse than what they lost.
Background
Messages is a free SMS/MMS app with a 3.7★ lifetime rating and 16,259,114 installs as of 2026-08-05. Its listing promises SMS/MMS, after-call actions, location reminders, themes, spam protection, backup/restore, scheduled messages, dual-SIM support, and optional permissions.
What it does
A default texting app for SMS, MMS, contacts, media, scheduling, blocking, backup, and customization.
What changed
Recent reviews repeatedly describe ads appearing before, inside, or over the message screen, sometimes before users can read or send texts.
Why it is soft
Texting is a trust product; when users believe the app blocks urgent messages, deletes photos, or forces itself as default, they actively look for a safer replacement.
Strengths
This is not a dead app. Some reviewers still call it simple, easy, useful for older users, and good for one-tap deletion; the install base proves demand for a non-OEM messaging alternative. A competitor must respect that users are not asking for a flashy social app — they want familiar SMS that opens quickly, avoids surprises, and preserves their conversations.
Retained habit
Texting is used daily, and a default SMS app can become sticky once trusted.
Simple positioning
The pitch is easy to understand: no interstitial ads, readable inbox, reliable MMS, and familiar folders/favorites.
Market gap
The gap is real but narrow: users are not asking for a new messaging paradigm; they want the old one back without intrusive monetization and broken basics.
Ads blocking messages
The dominant complaint is ads: pop-ups, bottom banners, Temu/Walmart redirects, load delays, and ads appearing before users can read OTPs or respond.
Forced default confusion
Many users say they were forced away from Samsung, Verizon, Motorola, or Google-branded flows and cannot easily switch back or set the default correctly.
Reliability and media loss
Reviewers mention missing texts, group messages, photos, attachments, links, failed sends, deleted conversations, and lost transferred media.
Missing familiar controls
Favorites, folders, larger inbox text, themes, background changes, search by name, sent/trash views, and message color-coding all appear as unmet expectations.
Ads are ridiculous , gotta wait for the ads to load before I can even read my messages 😞
the size of the messages is too small in the inbox. not all messages are received. needs to have an option to see when messages are delivered and read. need an option to like a message. had to pay to avoid ads in the app.
I was forced to switch from Samsung SMS to Google messages. Now I'm bombarded with ads when trying to send texts. I'm a senior citizen and have issues with my eyesight, and I can get confused. When technology moves too fast for all of its users, that's not good. Samsung is a good brand, but this was a bad move. I wish I could keep the app I knew how to use. Now I will use text less. That probably means I will lose touch with some people. At my age, that is a big deal.
- Never interrupt the inbox with ads. Use a free core app plus a $4.99 one-time supporter unlock for themes, backup, scheduling, and extra organization; do not put monetization between a user and an incoming text.
- Ship a senior-friendly familiar mode. Large inbox text, favorites, folders, clear sent/trash areas, simple default-SMS setup, and an obvious “switch back” help screen directly answer the usability complaints.
- Treat MMS reliability as the product, not an add-on. Group messages, photos, attachments, links, and transfer/restore need testing before themes, stickers, or after-call extras.
Build complexity
Estimated, not derived: one developer, part-time, no funding, no team, and no paid acquisition. A polished SMS/MMS client is harder than the UI suggests because it must become the default handler, request sensitive permissions, and behave across carriers, devices, dual-SIM setups, and media edge cases.
| Workstream | Weeks |
|---|---|
| Default SMS flow, permissions, policy-safe onboarding | 2.0 |
| SMS send/receive, contacts, threads, dual-SIM basics | 4.0 |
| MMS, group media, attachments, failure handling | 2.5 |
| Accessible inbox, favorites, folders, themes | 2.0 |
| Backup/restore, scheduling, basic spam controls | 1.5 |
| Billing, listing, QA on real devices | 2.0 |
| Total | 14.0 |
Expected revenue
Estimated, not observed: the model assumes a free ad-free core app and a $4.99 one-time unlock for extra organization, themes, backup/restore, and scheduling. Because users are specifically angry about ads and subscriptions, month-12 revenue is modest monthly receipts from new unlocks, not dependable subscription MRR.
| Month 12, monthly | ||
|---|---|---|
| Organic installs | 1,500 | assumption |
| Activated as default SMS | 750 | 50% |
| Still active after 30 days | 420 | 28% |
| Paid one-time unlocks | 180 | 12% |
| Revenue | $900 | $4.99 unlock |
Biggest challenges
The hard part for a solo builder is trust and edge-case coverage, not drawing chat bubbles. Users are handing over private texts and default-SMS control; one missed OTP, broken MMS thread, or scary permission prompt can create the same backlash you are trying to exploit.
Store and permission risk
SMS, contacts, call-log-adjacent, backup, and default-handler flows require unusually careful onboarding and review-safe wording.
Carrier and device testing
MMS, group messages, attachments, dual SIM, transferred photos, and failed sends are exactly where a part-time solo developer lacks test coverage.
Cold-start trust
A new SMS app asks for deep permissions with zero review history; the incumbent’s 16,259,114 installs still matter even with angry reviews.
AI angle
There is no strong AI wedge here. AI can help write support replies, classify spam, suggest folders, or summarize long threads, but it does not solve the core gap users are complaining about: ads blocking messages, default-SMS confusion, missing media, and reliability. Do not make this an AI messaging app; make it a boring, trustworthy SMS app.
Useful but secondary
Local spam labeling or smart folder suggestions could be premium polish after the base client works.
Not a build shortcut
AI will not materially reduce the SMS/MMS, default-handler, permissions, or cross-device testing work in the 14-week estimate.
Conclusion
Skip it. The user pain is obvious and emotionally strong, but SMS is a brutal solo-builder category: sensitive permissions, default-app trust, real-world carrier bugs, weak monetization because users reject ads/subscriptions, and no paid acquisition. Build it only if you already specialize in Android telephony and want a slow trust product, not a quick indie win.
14 weeks
Time to v1
$4.99
One-time unlock
$900
Revenue at month 12
Default SMS
Fact that decided it