Our goal is of course to use it as a replacement to WhatsApp / Telegram / Discord for social stuff, even though it's dominated by developers today. And we will get there (despite all the negativity on this thread :|)
Our goal is of course to use it as a replacement to WhatsApp / Telegram / Discord for social stuff, even though it's dominated by developers today. And we will get there (despite all the negativity on this thread :|)
This is a very regionally desirable feature, in my experience.
I have never (deliberately) sent a voice message on any platform, nor do I know anybody (well/any more) who would. But I went to a university with a high proportion of Chinese students, and it was really striking how much that feature was used (in apps that supported it obviously).
I'm just speculating, but I wondered if it was at least partly because of the tonal nature (roughly speaking: four intonations for each vowel, rendering completely different words, not just subtle changes in tone/emphasis) of mandarin, and relatively large number of different characters, making vocal communication more efficient than written; to an even greater extent than that may be true of English, for example.
I'm not really sure what I'm saying. Maybe it's not good to burn one market, maybe it is good to focus on excelling in others if (if!) the alternative is mediocrity everywhere, I don't know. Your comment just reminded me and I thought it was vaguely interesting.
In short, I don't think it's regional. It depends on the person with whom you need to communicate.
I'm not denying it's helpful/required for accessibility, I'm just talking about 'in general' large scale use of it (or not).
Maybe it's less about glasses (if you have to find your glasses to type a message I expect you also need to in order to unlock your phone, open the app, and tap the voice message button) for older people than it is about accustom to IM - the brief chatty format is more like a telephone call than a letter.
(But those I've known to use smartphones haven't used voice messages - as distinct from telephone voicemail - anyway, as I said.)
From my anecdotal/regional experience, people over 60 prefer to use voice messages almost exclusively while younger people prefer to text.
Maybe someone at telegram or whatsapp can provide statistical data to shed more light on voice message usage.
Any app lacking them has no chance of gaining traction there.
I think it's because we dumped SMS (which has no voice clips) early and moved to WhatsApp (I think it's been the norm for like 8 years now in Argentina).
same here.
really dislike how people essentially just ramble on and on for what could have been one sentece or a few words.
so it costs the recipient a lot of time and concentration to get the gist of the message.
maybe a cultural thing because my wife and here friends use voice msg a lot.
My personal pet peeve is that I have no idea what the difference is between "people" and "rooms", and why when I try to talk to a friend our chat is sometimes in one and sometimes in the other. Maybe you'd like to take a page out of the Telegram/Whatsapp book and not distinguish between the two, since they're all chats, they just sometimes have two people and sometimes more.
Best of luck, I'm really hoping to switch to Element for all my chats one day!
I still think that this is one of the more important open-source future-facing projects around and will continue supporting it, and urge others to, as well. If you dislike the hegemony of centralized services, then throw some money towards projects that support ideals you believe in.
I am a member of a social group that varies widly in age and technical experience. When I tried switching two of our members over to Element, I noticed them quickly growing upset with the app because the found it to be missing key features they expected like easily recording audio messages or the visual seperation of messages that are more than a few minutes apart.
From my personal experience with switching people from one chat app to another, people expect a replacement app to:
1. have 1:1 feature parity with the app it's replacing, 2. display all the information they've grown to rely upon, 3. and both feel and work like the app it's replacing. (even cosmetic things like text bubbles and larger font sizes)
Failing the first two points lead to the immediate dismissal of the app. Failing the last point is seen as a deficiency in the new app. Inversely, succeeding in all three leads to smooth adoption. It is why all my group is using telegram right now instead of whatsapp.
I'll have another go at switching my group to Element when/if the app gains the ability to send audio messages, but without Element looking and feeling similar its compition, I'm skeptical of my chances to succeed.
By the way, I really like Matrix and appreciate the hard work and care you're putting into this project. Thank you and keep up the good work.
Sign-up is a metric that your marketing team loves to track, but is a crazy user bottleneck.
Even if you only do it for, e.g. 6 months-1 year (spam concerns), let people chat with no account/sign-up. Let me give people a link that will let them chat with me, with no sign-up.
Element (back when we called it Riot) removed support for this a while ago BUT we are trying to design it back into the app, which you can follow https://github.com/vector-im/element-web/issues/9264
And yeah as a developer on the project, getting users into rooms quickly and chatting is a desperate goal of mine.
Whatsapp: 1) Install 2) it works. Even my 60+ relatives can handle it.
Discord: 1) install 2) it works. It also has voice/video chat rooms and a huge ecosystem of bots.
Telegram: Works, has bots, channels can be moderated, sticker packs, gifs etc fun stuff.
Discord: Works as long as Discord does not run out of VC money.
Telegram: Sends all phone numbers on your phone to a third party.
It's very strange to me to hear people describe Whatsapp as having good UX.
Having to give up your phone number and contacts is a feature for most people. They can instantly see that Marge from the office also uses WhatsApp so they can call/message them using that instead of paying for calls and SMS.
The limitations of WhatsApp web are mostly due to it being end to end encrypted. The "web client" is basically just using the phone as a proxy. It _is_ possible to have E2E encryption and allow multiple separate clients, but it's not a trivial problem to solve, thus most won't do it. (Telegram's E2E chats are device to device and not available on other clients than the one that initiated the connection.)
It's still crap, don't get me wrong. I'd rather use anything else, but at least where I live, it has critical mass and is the de facto standard.
> it has critical mass and is the de facto standard.
Yeah, it's the critical mass thing that is the most significant reason here, although it originally caught on back when simple onboarding was very unusual and that was its killer feature.
[1]: https://github.com/spantaleev/matrix-docker-ansible-deploy
I’ll admit, the documentation isn’t perfect. But it’s pretty good, and they should be able to set it up. There’s a few things I think could be more explicit in the docs, but even a mediocre set of sys-admin skills should be able to fill in the gaps.
I’m not an IT guy, or a sys-admin. I’m just a lowly, mid-level web developer :) But I was recently able to successfully setup my own Synapse server as per the docs, the very first attempt.
However, to your point. A more streamlined, or ‘automatic’ installation option would be fantastic!
Also wary of it wanting to upload my contacts list - could you comment on how it’s used? Or is that entirely up to the specific app?
Uploading contacts is strictly optional (and is missing on some platforms like Android currently, as per complaints elsewhere on this thread). They're used purely to discover which of your contacts are already on the platform - the privacy policy can be found at https://github.com/vector-im/policies/blob/master/docs/ident...