Sandes Message App Being Made in India – An Alternative To WhatsApp

Every time a large messaging service revises its terms, a wave of alternatives gets installed, opened twice and forgotten. Sandes arrived during one of those waves, and it was widely written up as the Indian answer to WhatsApp. That framing sells the story but it misreads the product, and the misreading is why so many people who installed it never worked out what to do with it.

Sandes is built by the National Informatics Centre under the Government of India. Read that sentence again before you judge the app, because it explains almost everything about the design decisions inside it. This is a look at what the app is genuinely for, what signing up requires, how to think about the security question without repeating marketing claims, and whether it can realistically live on your phone alongside what you already use.

Who Sandes Was Built For, And Who It Was Not

Government departments have a communication problem that ordinary users do not. Officials coordinate across offices, share documents that should not sit on foreign servers, and need a way to reach staff that survives an audit. For years that traffic ran on the same consumer messengers everybody else uses, which is convenient and administratively awkward at the same time.

Sandes is a response to that problem first. The verified-account system for officials, the broadcast facilities aimed at government-to-citizen messaging, and the choice to run the whole thing on state infrastructure all point the same direction. It is a departmental tool that citizens are also allowed to use, rather than a consumer app that departments happen to have adopted.

That distinction is not a criticism, but it does reset your expectations. Software built for institutional use optimises for accountability, identity and control. Software built for friends optimises for stickers, reactions, disappearing messages and whatever the app you already use added last month. Judging one by the priorities of the other produces a review that helps nobody.

Two Doors Into The Same App

Registration is where the dual purpose becomes visible. You can sign up with a mobile number, in the way any messenger works, or with a government email address. Those are not two routes to an identical account. They describe two populations using one piece of software.

The email route is the one that matters institutionally, because it ties an account to an official identity that somebody else issued and can withdraw. That is what makes verified accounts meaningful: the verification rests on employment records rather than on a blue tick bought or granted by a platform. The number route gives an ordinary citizen a working messenger without any of that apparatus.

Two practical consequences follow. First, an ordinary user should not expect the same set of capabilities an official sees, because some features exist specifically to serve verified accounts. Second, an account tied to a departmental email is tied to a job, so if the job ends the identity behind the account ends with it. That is intentional in an official tool and worth knowing before you make it your only messenger.

Where The Messages Live, And Why That Argument Is Real

The most repeated claim about Sandes is that it runs on Indian government infrastructure. This gets waved around as a security feature, which is sloppy. Data residency is not the same thing as data protection. It is a jurisdiction argument, and jurisdiction arguments cut in more than one direction depending on who you are.

For a department handling official correspondence, domestic hosting is straightforwardly useful. Records stay within reach of Indian law and Indian audit processes, and there is no question about a foreign company's obligations to a foreign government. That is a genuine institutional benefit and it is most of the reason the app exists.

For a private citizen the calculation is different and depends on what you are actually worried about. If your concern is a commercial platform building an advertising profile from your metadata, a non-commercial operator with no advertising business removes that motive entirely. If your concern is domestic access to your communications, moving them onto domestic government servers does not address it, and pretending otherwise would be dishonest. Neither of those is a scandal. They are just different threat models, and you should pick software against yours rather than against a slogan.

How To Interrogate Any Messenger About Encryption

Rather than repeat claims about any app's cryptography, learn the questions that separate a strong answer from a vague one. These apply to Sandes, to the messenger you use now, and to the next alternative that trends for a fortnight.

• Is content encrypted end to end by default, or only encrypted in transit between your phone and the server?
• If it is end to end, who holds the keys, and can the operator read a message if compelled to?
• What happens to backups, since a backup stored unencrypted elsewhere undoes the protection completely
• Is there a way to verify that you are talking to the right person, such as a safety number or code you can compare?
• Does the operator publish a policy stating what is retained, for how long, and under what process it is handed over?
• Has the implementation been examined by anyone outside the organisation that wrote it?

The distinction in the first question does most of the work. Transport encryption protects a message from anyone watching the network between you and the server, which is essential and also the minimum any competent service provides. End-to-end encryption additionally means the operator cannot read what passes through. Marketing copy frequently blurs the two by saying messages are encrypted, full stop, and a reader who knows the difference will notice the omission immediately.

Check the current answers in the app's own published documentation rather than in an article, including this one. Security properties change with releases, and a claim that was accurate a year ago may describe software that no longer exists.

The Feature Set Against A Normal Day Of Use

On the essentials Sandes does what you would expect. Individual chats, groups, voice messages and file sharing cover the bulk of what most people do in a messenger, and none of them requires explanation to anyone who has used a phone in the last decade.

Where you feel the gap is in the accumulated conveniences of a consumer platform, the ones nobody lists as requirements but everybody misses within a week. Consider what your own daily use actually depends on before switching:

• A desktop or web client, if you type long messages during working hours
• Voice and video calling, which many people now use more than typed messages
• Payments inside the chat window, where that habit has taken hold
• Status or story posts, which are load-bearing for small businesses more than for individuals
• Reactions, replies to a specific message and threaded context in busy groups
• Media compression that keeps a shared photograph usable rather than reducing it to mush
• A reliable search across old conversations, which is what turns a messenger into a filing system

Go down that list honestly and mark the three you would refuse to give up. That short list, and not a feature-count comparison, tells you whether a switch is realistic for you. Most people discover their attachment is to two or three specific behaviours rather than to the app as a whole.

The Barrier Is Your Contacts, Not The Software

A messenger has an unusual property among applications: its usefulness to you is determined almost entirely by decisions other people make. A photo editor works perfectly whether or not anybody else installs it. A messenger with nobody in it is an empty room with excellent furniture.

This is why alternatives get installed in waves and abandoned quietly. The install is one person's decision and takes thirty seconds. Actually moving requires dozens of other people to make the same decision at roughly the same time, and they each face the same problem you do. The switching cost is not paid by you alone, so it very rarely gets paid at all.

Two situations break that deadlock, and both are worth recognising because they are the only realistic paths to adoption. The first is a mandate: an employer or a department instructs its people to use a particular tool, and the network appears overnight because nobody had a choice. The second is a group with a specific shared reason to move, such as colleagues who handle official documents. Sandes is plausible in both. It is not plausible as the app that pulls your school friends across one at a time.

Running Two Messengers Without Making A Mess

The pragmatic outcome for most readers is keeping both, and that arrangement works fine if you give each one a defined job rather than letting them overlap. Overlap is what produces the familiar mess of searching three apps to find one file.

Assign a purpose to each: Decide that one app carries official or work correspondence and the other carries personal conversation, then hold the line. The rule only functions if you never make exceptions for convenience.

Tell people the rule once: A single message to the groups that matter, stating where you can be reached for what, saves months of messages arriving in the wrong place.

Set notifications differently: Give the work messenger quiet hours and leave the personal one alone, or the second app simply doubles the number of interruptions in your day without adding anything.

Watch storage on an older handset: Two messengers means two media caches. On a phone with limited space, clear the cached media in each every few weeks rather than waiting for the storage warning.

Install from official sources only: Get it from the official app store listing or the government's own distribution page. Messenger names are among the most heavily impersonated in sideloaded packages, and a fake messenger is a keylogger with a chat interface.

Where It Falls Short

The obvious weakness is the one it shares with every challenger: an empty contact list. That is not a flaw in the code, but it decides whether the app is useful to you, and no amount of engineering fixes it from the inside.

The second is a matter of pace. Consumer messengers iterate constantly because they compete for attention and their revenue depends on it. Government software is built to a specification, released, and maintained. That produces something stable and unexciting, which is the right trade for official correspondence and the wrong one for an audience accustomed to a new feature every month.

The third is documentation aimed at ordinary people. Institutional software tends to be described in the language of the institution, so a citizen trying to establish what is retained, for how long, and how the two account types differ has to work harder than they should. That is a fixable problem and it would meaningfully improve the app's standing with private users.

What Readers Ask Before Trying Sandes

Do I need a government email address to use it? No. A mobile number registration is available to any user. The official email route exists to attach an account to a verified institutional identity, which is a requirement for officials rather than a barrier to everyone else.

Is it safer than what I use now? Safer against what? It removes a commercial operator with an advertising business from your communications, which is a real change. It does not make your messages invisible to everyone, and no messenger does. Decide by naming the specific risk you care about, then check the app's published policy against it.

Can I move my old chat history across? Assume not. Message histories are stored in formats specific to each application, and portability between competing messengers is close to non-existent everywhere. If a conversation contains something you need to keep, export or screenshot it before you rely on a second app.

Does it work on an old phone? The basic functions are light by design, since a departmental tool has to run on whatever handsets staff already carry. Two messengers on a phone with very little free storage will still fight over cache space, and that, rather than processing power, is what usually causes the trouble.

Should I delete the app I use now? There is no prize for switching cleanly. Keeping both costs you some storage and a little attention, and it lets you be reachable where people actually are while you find out whether the alternative sticks.

Install Sandes if you deal with government correspondence, if your workplace has asked you to, or if you want to see what a publicly built messenger looks like from the inside. Do not install it expecting to replace the app your family uses, because that decision was never yours to make alone. The most useful thing this app demonstrates is that the hard part of messaging was never the software.