Top 20 User Complains of Session Android Based on Google Play Reviews

[venezuela01]

This is a user experience research drawing on 1153 user comments from Google Play reviews of Session for Android between 2020-02 and 2023-11. Employing NLP technology, we have systematically extracted and categorized 481 negative feedbacks (including duplications) from 1153 comments, then deduplicate/aggregate them into 100+ different complains.

This approach is not intended to replace formal bug reports; rather, it offers a reflection of users' subjective perceptions. This analysis helps identify priority areas for future development. While some feedbacks may refer to issues already resolved, the methodology remains valuable for ongoing monitoring and enhancement of user experience in Session.

(There's commercial solution called 'ticket routing' for similar purpose, haven't tried yet: https://monkeylearn.com/for-support/)

Duplications	Key Issue Description
75	Performance and stability issues: lags, crashes, usability disruptions
59	Issues uploading files/sending media through gallery
47	Notification system problems: failing to send, false notifications, persistent notifications, delayed alerts
22	Lacking calling features: silent calls, reconnection difficulties, no video calls, crashes or stability issues
21	Inconsistent message sending, blocked sending capabilities, degraded user experience
13	"Session is out of sync" errors during recovery phrase use, preventing session recovery
12	Antivirus software detects malware, leading to automatic app removal, security concerns
11	Disappearing Messages issue: not disappearing on recipient's device after session restoration
7	Inability to connect to Bluetooth earpieces/wireless hands-free devices
7	Group chat issues in 50-100 member groups: locked out/muted, laggy performance, slow multimedia loading
7	Deleting chat also deletes associated contact
6	Unable to send documents (e.g., PDFs, Android software files), "failed alert" when selecting documents
5	False screenshot notifications sent, raising security concerns
5	VPN requirement for functionality in Iran, affecting accessibility
5	"Bad encrypted message" errors on various Android devices
4	App lock feature not functioning correctly, privacy impact
3	Issues initiating chats on legacy Android systems: failed outgoing messages, crashes
3	UI/UX issues on Android during 'create session' process, visibility issues with random numbers box
3	High battery consumption
2	Fingerprint authentication not functioning

Due to the long-tail distribution of user feedbacks, we have focused on the top 20 complaints, while omitting the less frequent 100+ complaints from the report.

[KeeJef]

Thanks, this is useful, i went through an did a rough version of this a few weeks ago but this is nicer presented

[venezuela01]

See also Session User Engagement Report

[venezuela01]

Thanks, this is useful, i went through an did a rough version of this a few weeks ago but this is nicer presented

Actually I already have this analysis almost done a few weeks ago. If I have more visibility to the internal TODO list I'll publish my report much earlier.

[easthvan]

is this Session project abandoned or to be soon? Because 2 months and no update in Play Store while there are so many issues.

[KeeJef]

is this Session project abandoned or to be soon? Because 2 months and no update in Play Store while there are so many issues.

No, we are working on a large update to disappearing messages right now

[easthvan]

is this Session project abandoned or to be soon? Because 2 months and no update in Play Store while there are so many issues.

No, we are working on a large update to disappearing messages right now

It would be a great relief to see Session rising again. Will you remove the possibility of cloning users of Session accounts with the same ID...? And so to eliminate the risk of adversaries somehow obtaining the recovery seed of a user and cloning them? All this is possible on Session as there is no registration PIN code and system in place that prevents multiple devices with same Session ID on the network...

[venezuela01]

Will you remove the possibility of cloning users of Session accounts with the same ID...? And so to eliminate the risk of adversaries somehow obtaining the recovery seed of a user and cloning them? All this is possible on Session as there is no registration PIN code and system in place that prevents multiple devices with same Session ID on the network...

This sounds related to Multi-device Security Enhancement.
I suggest moving related discussions to that issue and keeping this one for data analysis of Google Play reviews.