Most new apps begin with an app store listing, a download and a sign-up screen. A different approach has been gaining attention among young founders: build the product inside a messaging app people already use. Instead of asking users to install something, you let them text a number or add a bot to a chat. The idea sounds like a shortcut, and in some ways it is. It also comes with real limits that matter for anyone considering it.
What “inside messaging” means
There are several ways to deliver a product through chat.
1. A phone number that replies. You text a number and a service answers, often powered by AI.
2. Bots in group chats. A bot joins a conversation and responds to commands.
3. Official business messaging channels. Companies send updates, take bookings and answer questions through approved platform APIs.
4. Mini apps and extensions. Small apps that run within a messaging platform, such as stickers, games or payment tools.
5. Automation using shared accounts. Software that reads and sends messages on behalf of a user. This can break platform rules.
Each method gives different capabilities and different risks.
Why founders like it
- Zero install. Users start with something they already have.
- Familiar habit. Texting is natural, so there is little to learn.
- Fast launch. A small team can build a service without designing a full mobile app.
- Distribution through friends. Group chats make it easy to invite others.
- Low cost to test. You can see whether people want the idea before investing in a full product.
- Trust. People are used to messaging from known numbers.
For AI products, chat is the natural interface anyway, so the format fits well.
The practical limits
Messaging platforms were not designed as app stores, and building on them brings constraints.
Platform rules. The company that owns the messaging service sets the terms. Some platforms provide official tools for businesses, others restrict automation. If your product depends on behaviour the platform dislikes, it can be cut off.
Limited interface. Chat is flexible for text but weak for complex layouts, dashboards or detailed settings.
Identity and privacy. Your service may see phone numbers and message content, which raises responsibilities.
Cost. Sending large numbers of messages can incur carrier or platform fees.
Reliability. Messages can be delayed, filtered as spam or blocked.
Little control over experience. You can’t customise notifications, onboarding or design as fully as in your own app.
Monetisation. Taking payments inside messages may need separate links or workflows.
Compliance and consent
Messaging products are subject to regulations. Depending on the country, you may have to:
- Get clear consent before sending messages.
- Offer a simple way to stop messages, such as replying with a stop word.
- Follow rules for automated texting.
- Register campaigns with carriers.
- Handle personal data according to privacy laws.
- Protect minors.
Ignoring these rules can lead to blocked numbers or legal trouble.
Trust and safety
When a product operates in private conversations, it deals with sensitive material. Founders need to think about abuse, harassment and illegal content from the start. This includes content filters, reporting tools, rate limits and a way to ban bad actors. AI features add further questions, like how to prevent harmful outputs and how to describe the limits of the system honestly.
Is it a good approach for a new product?
It depends on the idea.
Good fits:
– Simple, text-based services such as reminders, answers, recommendations or coordination.
– Products meant to be shared among friends.
– Early experiments to measure interest.
Poor fits:
– Anything needing rich visuals or complex workflows.
– Products that need long-term control over the user relationship.
– Services whose business depends on platform features that may change.
Many teams use chat as a starting point and later build a standalone app once they know what users want.
A checklist for builders
1. Read the platform’s terms before writing code.
2. Use official business interfaces where available.
3. Collect only the data you need, and explain why.
4. Put opt-out and reporting tools in place on day one.
5. Plan how you will move users to your own channel if the platform changes.
6. Track costs per message and per user.
7. Test with a small group, then expand slowly.
A checklist for users
- Check who runs the service and how they handle your data.
- Be careful about sharing sensitive information in a bot conversation.
- Use the stop command if you no longer want messages.
- Remember that a chat bot is software, even if it sounds friendly.
- Avoid services that ask for access to your whole message history without a clear reason.
The takeaway
Building inside messaging lowers the barrier to launch and takes advantage of habits people already have. It also means depending on someone else’s platform and rules. For young founders, it is a quick way to learn whether an idea has appeal. For users, it offers convenience as long as privacy and consent are respected. The best products will treat chat as a starting channel, not as a permanent home.
For wider background, Wikipedia has a general overview of Messaging apps. You may also find these related guides useful: How Virtual Health Clinics Work: Telehealth Basics and Why Apps Get Shut Down During Cost-Cutting.
