Download APK Session Version Selection, Latest Features & Review

I first opened Session on a quiet morning while my phone was still charging, and I had a few minutes to spare before the day properly began. What struck me first was the simplicity of the layout and the way the important actions sat exactly where I expected them to sit. Nothing shouted for attention. The chat list was clean, the compose button was easy to find, and the settings menu used plain words instead of jargon. Over the first week I used Session mainly in short sessions, and I paid attention to how it felt on ordinary days rather than on perfect ones, because that is where a messenger either earns its place or quietly gets deleted.

Session is a private messenger built around a simple idea: you should be able to talk to people without handing over your phone number, and without a company building a map of who talks to whom and when. It grew out of the Signal protocol family, but it takes a different route for moving messages around. Instead of a central server that knows your identity, Session routes messages through a decentralised network of service nodes, and your account is a long Session ID rather than a telephone number. That design shapes almost everything about the app, from how you add contacts to how you recover an account, and it is the reason version choice matters more here than it does for an ordinary chat app.

This article answers the questions I had before I kept Session installed: which version should you pick, what has changed lately, what does it actually do well, and where does it fall short next to the messengers most of your friends already use? I tested it on a mid-range Android phone running a recent Android version, with a second phone on an older build for comparison. I sent text, photos, voice notes and group messages, I left the app alone for a day to see whether notifications still arrived, and I tried the recovery flow with a saved recovery phrase. What follows is what I found, including the rough edges.

What Session private messenger is and how version selection works

Session is a messaging app for Android, iOS and desktop that offers end-to-end encrypted chats, voice messages, group chats and file sharing without asking for a phone number or an email address. When you create an account, the app generates a Session ID, a long string of letters and numbers that acts as your address. People add you by that ID, or by scanning your QR code, and nobody needs to know your real name or your number to reach you. Messages are encrypted on your device before they leave it, and they travel through onion routing, which means each relay node in the network only knows the previous hop and the next hop, never the full path or the sender and receiver together.

Version selection matters because Session is updated often, and the way you install it decides how quickly you get fixes. The main routes are the official app listing on Google Play, the F-Droid build, and the APK published by the developers themselves. The Play build is the simplest route for most people, since updates arrive automatically and the listing shows the current version number and the date of the last update. The F-Droid build suits people who prefer open-source app sources, though new versions sometimes arrive there a little later. The direct APK suits people who want a specific version, for example to test whether a new release fixes a problem on their phone, or to stay on a build that works well on older hardware. That said, staying on an old version for months is a poor trade: you miss security fixes, and older clients can struggle with newer group features.

How onion routing changes the privacy picture

Most messengers encrypt the content of your messages but still see metadata: who you are, who you message, when, and from which IP address. Session tries to shrink that metadata by routing each message through three service nodes in the Oxen network, with layers of encryption peeled away at each hop, in the same spirit as onion routing on the wider web. No single node sees both ends of a conversation, and the nodes that hold your messages while you are offline, the swarm, only see encrypted blobs addressed to your Session ID. In practice, this means the app feels like an ordinary messenger on the surface, while the plumbing underneath is doing considerably more work than a centralised chat service. The trade-off is real too: routing adds a little latency, and message delivery can occasionally take a few seconds longer than a direct server hop, especially on a weak connection.

Session ID instead of a phone number

Your Session ID is both your username and your key. You can share it freely, because knowing it lets someone message you but does not reveal your number, your contacts or your location. You can also create a display name and a profile picture, and you can change both whenever you like. Contacts see the name you choose, not the raw ID, once they have added you. The part that needs care is recovery: if you lose your phone and you have not saved your recovery phrase, there is no password reset email and no support desk that can hand your account back. That is the price of an account with no central registry, and it is worth understanding before you move important conversations into the app.

Where to find your Session ID

Open Session, tap your profile picture or avatar at the top of the chat list, and your Session ID appears on the profile screen with a copy button and a QR code. Tap the copy button and paste the ID into a password manager or a private note. I keep mine in the same password manager where I keep my other recovery phrases, because that is the one place I know I will check first if a phone is lost or reset. Do not post the full ID in a public chat or on a public profile unless you are happy for strangers to message you.

Backing up your Session ID safely

Session shows a recovery phrase when you create your account, and the same phrase appears in the settings under your account section. Write it down on paper as well as saving it digitally, and keep the paper copy somewhere a visitor would not stumble across it. Test the phrase once by signing in on a second device or after a reinstall, so you know it works before you actually need it. A recovery phrase you have never tested is a guess, not a backup, and I learned that lesson the expensive way with a different app years ago.

Session latest features worth knowing in 2026

Recent Session releases have focused on polish rather than reinvention: faster message sync, steadier notifications, better group handling, and small quality-of-life fixes that show up in daily use. The chat list loads more quickly on first open, and switching between conversations feels snappier than it did a year ago. Closed groups now handle larger member lists more gracefully, and the app does a better job of showing which messages have actually been delivered when a contact is offline for a while. None of these changes is dramatic on its own, but together they make the app feel less like a privacy experiment and more like a messenger you can rely on for everyday talk.

One change I noticed quickly was how the app handles media. Photos and voice messages send in the background now, so you can keep typing while a large photo uploads instead of watching a progress bar. Link previews appear for shared web pages, with a toggle to turn them off if you would rather not fetch preview data. The app also lets you set a disappearing message timer per conversation, from a few seconds up to a week, and the timer applies to new messages from the moment you set it. For people who use Session for sensitive work, that per-chat control is more useful than a single global setting, because a chat with a colleague and a chat with a close friend rarely need the same rules.

Disappearing messages and screenshot controls

Disappearing messages in Session delete messages from both devices after the timer you choose, and you can set the timer from the conversation settings screen. I use a one-day timer for casual chats where old messages add nothing, and I leave it off for chats where I need to look back at an address or a date. The app also offers screenshot protection on Android, which blocks screenshots inside the app when enabled. Here is the catch, though: no screenshot block can stop someone photographing a screen with another phone, so treat disappearing messages as a tidy-up tool and a courtesy to the other person, not as a guarantee that words vanish from the world.

Closed groups and community groups

Session offers two kinds of group chat. Closed groups are encrypted end to end, capped at a modest size, and suited to a family chat, a small team, or a circle of friends. Community groups, sometimes called open groups, are larger public or semi-public rooms hosted on a server, and they are not end-to-end encrypted in the same way, because the server needs to relay messages to many members. That distinction matters: use a closed group when the conversation itself is private, and use a community group when you are joining a public discussion where the topic matters more than secrecy. Admin controls cover adding and removing members, and group invites work through a link or a QR code.

Voice messages, attachments and link previews

Voice messages record with one long press, and they play back inside the chat with a simple scrubber, which makes them practical for quick updates when typing is awkward. Attachments cover photos, videos, documents and other files, with a size limit that is generous for everyday sharing but not designed for moving huge video files. Link previews fetch a title and a thumbnail when you paste a web address, and you can disable them in settings if you prefer that the app never contacts a preview service. In my testing, a voice note sent over a slow mobile connection arrived within a few seconds, and a photo sent from a weak signal queued and delivered once the connection steadied, without me having to resend it.

How to choose the right Session version for your phone

Choosing a version starts with a simple question: does your phone run a recent Android release, and do you want automatic updates? If the answer to both is yes, take the current build from Google Play and let it update itself. That is the path with the least friction, and it keeps you on the newest security fixes without any thought. If your phone runs an older Android version, check the minimum Android version listed on the app page before installing, because a build that targets a newer Android release may refuse to install or may behave oddly on an old device. If you are testing a fix for a specific bug, install the exact version the developers mention in the release notes, use it for a few days, and then move back to the current release once you have confirmed the fix.

There is also a practical habit worth building: after every major update, spend two minutes checking the basics. Send a message to a contact, check that notifications arrive with the screen off, and open a group chat to confirm older messages still load. Most updates pass that check without a thought, but the two minutes catch the occasional bad release before it becomes a missed message. If an update does misbehave, the safest step is to restart the phone, then check whether a newer patch release has already appeared, because Session releases patches quickly when a real problem surfaces.

Checking the version you already have

Open Session, go to Settings, and look for the version number at the bottom of the screen or under the About section. Compare that number with the current version shown on the official app listing. If the numbers match, you are up to date. If they differ by more than one minor release, open the app listing and update, or check whether automatic updates are paused for this app. I check the version whenever I notice a feature behaving differently after an update, because half the time the answer is simply that I am reading release notes for a newer build than the one installed.

When an older version makes sense

An older version makes sense only for a short, specific reason: a new release breaks something on your phone, a feature you rely on changed in a way you dislike, or you need to reproduce a bug for a report. In those cases, keep the older build for a week or two, note what works and what does not, and then try the next release. Treat the older version as a temporary experiment, not a permanent home. Security fixes, group compatibility and notification reliability all drift away from old builds over time, and the longer you stay behind, the more likely a small annoyance becomes a real problem.

Session vs Signal vs WhatsApp vs Telegram: a fair comparison

Session sits in a crowded field, and each rival has a genuine strength. Signal is the closest cousin: it uses the same encryption ideas, it is open source, and it is widely audited, but it asks for a phone number at registration. WhatsApp has the largest user base by far, so your friends are already there, and it offers encrypted chats by default, but it is tied to a phone number and to a large company that collects metadata. Telegram offers huge groups, channels and bots, but its ordinary cloud chats are not end-to-end encrypted by default, and only its secret chats use that protection. Session trades reach for privacy: fewer of your contacts will already have it, but nobody needs a phone number to use it, and no central server holds a directory of who you are.

The verdict depends on what you value most. If your priority is talking privately without a phone number attached to your identity, Session is the strongest pick of the four, and the onion routing is a real difference rather than a marketing line. If your priority is reaching everyone you know without asking them to install anything new, WhatsApp wins on reach alone. If you want strong encryption plus a polished, widely audited app and you do not mind registering a number, Signal is the balanced choice. If you live in large public groups and channels, Telegram is hard to beat, though you should use secret chats for anything genuinely sensitive. I keep Session alongside one mainstream messenger, because that split covers both privacy and reach without forcing every contact to switch.

Who should pick Session

Session fits journalists, activists, researchers, and anyone whose work involves sensitive conversations, as well as ordinary users who simply dislike handing a phone number to every app they try. It also fits people who want a second messenger for a small circle, where everyone agrees to use it together. If your threat model is a curious company building a profile from your metadata, rather than a targeted attack by a skilled adversary, Session covers that case well. If you enjoy Session then the LINE article is a useful next read because it covers a fellow social app with a similar daily rhythm, and it helps to see how a messenger built for a different audience handles the same everyday tasks.

Who should pick something else

If most of your family and friends refuse to install a new messenger, Session will feel lonely, and a mainstream app will serve you better for daily life. If you need reliable voice and video calls every day, or you need to run a large public community with bots and moderation tools, Telegram or WhatsApp will fit better right now. Readers who compare options often open the Buffer article next, because it shows how a different kind of social tool organises sharing and scheduling, and that contrast helps you decide what kind of app your routine actually needs. For a third perspective the Likee article is worth a look because it shows another approach to sharing and discovery, one that is built for entertainment rather than private talk.

Session features in everyday use

Day to day, Session behaves like a calm, focused messenger. The chat list shows unread counts and message previews, and a long press on a conversation gives you mute, pin and delete options. Inside a chat you get text, emoji reactions, replies, forwarded messages, voice notes, photos, videos and documents, plus the disappearing timer already mentioned. The app supports a dark theme, which I leave on permanently, and it lets you set a passcode or use your fingerprint to lock the app, so a borrowed phone does not open your chats. Notifications can be customised per conversation, and the app shows a simple delivery indicator so you know whether a message has left your phone.

• Onion-routed private messaging keeps your chats encrypted and your routing metadata minimal, so the network sees far less about who talks to whom than a centralised messenger would.
• Disappearing messages with a per-chat timer, from seconds to a week, so each conversation can have its own retention rule.
• Closed groups for small private circles, plus community groups for larger public discussions, with clear admin controls for both.
• Voice messages and file attachments for everyday sharing, with background sending so a large photo does not block your typing.
• App lock with PIN or fingerprint, a dark theme, and per-chat notification settings that keep the app quiet when you need it to be.

What I liked most after a week was how little the app asked of me. There were no stories, no suggested contacts, no feed trying to pull me back in. I opened it, I read or sent a message, and I put the phone down. That restraint is a feature in itself, and it is the main reason the app stayed on my home screen after the novelty wore off. The design is not flashy, and the animations are modest, but the basics are solid: messages arrive, groups stay in sync, and the app rarely crashes or freezes on ordinary hardware.

Pros and cons of Session after a week of daily use

A fair review needs both sides, and Session has clear strengths and clear limits. The strengths show up in daily use: privacy that is built into the design rather than bolted on as a setting, a simple interface that stays out of the way, and a small, focused feature set that does a few things well instead of doing everything poorly. The limits show up just as clearly: fewer of your contacts will already have it, voice and video calls have been less mature than the big rivals, and account recovery rests entirely on a phrase you must keep safe yourself.

• No phone number or email needed to register, so your identity is a Session ID you control.
• End-to-end encryption plus onion routing, which limits both content exposure and metadata exposure.
• Clean, calm interface with disappearing messages, closed groups and an app lock built in.
• Open-source code and a decentralised network, so no single company controls the whole system.

• Smaller user base, so you will need to invite friends rather than finding them already there.
• Voice and video calls are less polished than WhatsApp or Telegram, and call quality varies by device.
• No password reset: losing your recovery phrase can mean losing the account for good.
• Occasional delivery delays on weak connections, because routed messages take a longer path.

Who Session is for

Session is for people who want private messaging without a phone number, who are comfortable inviting a small circle to join them, and who are willing to keep a recovery phrase safe. It suits a second messenger role very well: keep your mainstream app for family groups and school chats, and use Session for conversations where privacy matters most. It also suits anyone who is tired of feeds, stories and suggestions, because Session is only a messenger, and it does not try to be anything else. If that description sounds like you, give it a full week with at least two or three real contacts before you judge it, because a messenger with nobody to talk to tells you nothing.

A setup that worked for me

My setup was simple: I installed the current Play build, saved the recovery phrase in my password manager and on paper, set a one-day disappearing timer on casual chats, turned on the app lock, and invited three friends to a closed group. That group became my test bed for the week, and it is where I noticed the delivery speed, the group sync and the notification behaviour most clearly. By day five the app felt routine, which is exactly what I want from a messenger.

What I would change first

If I could change one thing, it would be the first-run screen: it should explain the recovery phrase in plain language before the user can skip past it, because that phrase is the whole account. A short, honest warning on day one would prevent more lost accounts than any later help page. A second wish is steadier call quality, because a messenger that handles text beautifully but calls awkwardly will lose people who need both.

Troubleshooting Session: common problems and fixes

Most Session problems I met had simple causes. The app rarely failed on its own; more often the phone, the connection or a setting was the culprit. Work through the checks below in order, and change one thing at a time, so you know which step actually fixed the problem. If a problem survives a restart and a reinstall, check the official release notes or community channels for a known issue with your version, because a bad release is sometimes the answer, and the fix is usually a patch that arrives within days.

Messages not arriving

First, check your connection and whether other apps can reach the internet. Then open Session and pull down on the chat list to refresh, and confirm the contact is still in your list and has not changed their Session ID. If messages still do not arrive, restart the phone, because a stuck background process is the most common cause I have seen. Battery optimisation is the next suspect: on some Android phones, aggressive battery saving kills the background connection, so exempt Session from battery optimisation in the phone settings and test again with a message from a friend.

Notifications delayed or silent

Delayed notifications usually trace back to the same battery optimisation setting, or to a notification channel that is set to silent. Open the phone settings, find Session under apps, and check that notifications are allowed and that the battery setting is set to unrestricted or optimised rather than restricted. Inside Session, check the per-chat mute settings, because a muted chat stays silent even when everything else works. I also found that turning off the disappearing timer test chats and sending a fresh message was the quickest way to confirm whether the fix had worked, rather than waiting for someone to message me first.

Session frequently asked questions

Does Session need a phone number to sign up?

No. Session creates a Session ID when you first open the app, and that ID is your account. You do not enter a phone number or an email address, and there is no SMS code to wait for. The only thing you must keep is the recovery phrase shown during setup, because that phrase is how you restore the account on a new phone.

Is Session really more private than WhatsApp or Telegram?

For metadata, yes, in a meaningful way: onion routing and the absence of a phone-number directory mean the network learns less about who you talk to and when. For message content, Session, Signal and WhatsApp all use end-to-end encryption on private chats, so the content protection is comparable. Telegram is different, because its ordinary chats are not end-to-end encrypted by default. The honest answer is that Session is strongest when both content and metadata matter to you, and comparable to Signal when only content matters.

Which Session version should I install on an older Android phone?

Install the newest version that lists your Android version as supported, and prefer the Play build so updates arrive automatically. If the newest build refuses to install, check the minimum Android version on the app page, and consider whether the phone itself needs a system update first. Avoid staying on a very old build for months, because security fixes and group compatibility move on, and an old client can quietly fall behind.

Can I use Session on two devices at once?

Session supports linked devices, so you can use the same Session ID on a phone and a desktop, and messages sync between them. Linking is done from the settings by scanning a code or entering the recovery phrase on the second device. Keep in mind that each linked device holds its own copy of your messages, so lock each one with a passcode or fingerprint if the device leaves your hands.

Final verdict: is Session worth keeping installed?

After a week of daily use, my answer is yes, with a clear condition: Session is worth keeping if you have even a small circle willing to use it with you, and if privacy without a phone number matters to you. It is not the messenger for everyone, and it does not try to be. It is a focused tool that does private text chat very well, with a calm interface and honest limits. Keep a mainstream messenger for the contacts who will never switch, and let Session handle the conversations where privacy is the point. That split worked for me, and it is the setup I still use.

If you want to try it properly, install the current version, save your recovery phrase before you send your first message, invite two or three people you actually talk to, and give it a full week. A week of real chats will tell you more than any review can. When you are ready, use the link below to reach the Session page on AndroidRU.

Click here to download the Session app

A similar app is worth a quick look too. Click here to download the LINE app. For a second option, Click here to download the Buffer app.

Private messaging without a phone number is the idea that holds this whole app together, and it is the reason the small trade-offs, such as inviting friends yourself and guarding a recovery phrase, are worth accepting for the people who need it.

One last practical note: check the version number after any update, confirm notifications still arrive with the screen off, and keep the recovery phrase somewhere you will actually find it. Those three habits cost minutes and they protect the one thing Session cannot give back, which is an account whose only key is a phrase you hold yourself.