[supritgandhi]

Thanks for your comment! Fragmented communication as in, users need to jump across multiple apps or platforms for different context, simple example, people generally use platforms like Slack/Teams for internal communication and prefer email for external communication. With RelayBeam you can have single platform for both the purpose.

You can create project specific ports as well, as it can can segregate the messages as per the context. Another example: if joe is in sales & marketing department, then joe can have joe@sales and joe@marketing, which can be helpful in prioritizing the messages.

Do you have any suggestions for further improvements?

[emacsen]

I don't want to sound negative, but as a potential user, I don't see this solving any problems I have.

My communication is spread across email, Signal, Discord, Matrix, and XMPP. I have several email addresses, two Signal accounts, a Discord user, and XMPP.

The selling point on the website is that my communication is fragmented. The answer you're suggesting is "Move all your communication to my platform and it won't be fragmented." I could make the same argument about any of these. "Stop using Signal, Discord, Matrix, and XMPP and do everything by email." Worse yet, it demands that everyone else stop using these other communication mediums and I switch exclusively to this. Even if this were possible (it's not) I'd never want a single vendor controlling all my communication.

The port idea is similarly underwhelming.

What I thought you were going to offer is some kind of semantic categorization. This way I can know about all the communications that involve Project X15, but instead, I now must rely on the other party to send to the right port.

I can't even get people to update their email address for me after over a decade, so this feels like a non-starter.

At the end of the day, I don't see what this will offer me. It's yet another platform, adding to the problem of fragmented communication. It's features aren't especially compelling, and it suffers from deep vendor lock-in.

My suggestion is to find a niche for this, since I don't see it providing value as a general tool.

[dismalpedigree]

So everyone needs to use RelayBeam in order to communicate? Selling all my contacts on yet another communication tool is difficult.

[supritgandhi]

Please help me understand:

Are you asking if you have to share your contact details like phone number or email? - No you need to share any of those. You don't even need phone number or email address for creating account on RelayBeam. You just need to share relevant port address for communicating with someone.

Or are you asking about migrating all your existing conversations in other tools?

[dismalpedigree]

When using a communication tool, I assume it is to communicate with someone other than myself. It seems the other person must be using RelayBeam also. The challenge is that even if I really like RelayBeam, it adds little value if I don’t have people to communicate with. People are somewhat burned out on having a thousand different communication apps, and getting them to add one more seems like a significant effort.

[vidarh]

If I give my contacts this address, every one will 1) think it's an email address, 2) when learning it is not, ask for my email address so they don't have to sign up to something else.

[supritgandhi]

You can start using RelayBeam whenever you think ports can help you organize the conversations.

[immibis]

Only if your conversation partner also does. And if I'm selling them on a new app, why not SimpleX, which is decentralized (I think?), has actual privacy, and even easier to install than something like Whatsapp?