←back to thread

Show HN: Amber – better Beeper, a modern all-in-one messenger

(useamber.app)
68 points DmitryDolgopolo | 2 comments | 02 Sep 25 18:48 UTC | HN request time: 0.001s | source

Hi HN! Excited to share early access to Amber.

I’ve tried every all-in-one messenger out there (Beeper included) but they always fell short. No real folders, no AI, clunky UI, no CRM features… As a founder who speaks with hundreds of people every quarter, I needed something better. So I decided to rebuild the entire experience from ground up.

Thoughts from one of our users: "The app I've been searching for for a looong time."

Check it out for free today!

Demo: https://www.loom.com/share/8b5bc80b9893436b9190ae41fc3f0f50

Features: - All messages (Whatsapp, Telegram, iMessage) unified in a beautifully crafted interface. - Split inboxes (folders) to effortlessly focus on work, friends, a particular project.. whatever matters the most right now. - Mark read – no read receipts (even on Whatsapp and Telegram), mark done only when you’re done. - Personal CRM: a lightweight private database of knowledge about each person with (optional) AI pulling important facts straight from conversations. (the latter is coming soon) - Command bar + shortcuts. - Send later + reminders.

Everything is securely stored on-device. All messages are end-to-end encrypted and go straight from your device to the network of choice – never touching our servers.

Show context
devilkin ◴[02 Sep 25 19:24 UTC] No.45107823[source]▶
Before I would even consider something like this:

* Where's your privacy policy?

* What/how are you handling the different customer protection laws? What juristictions are you working in? Where's the data hosted?

* Where's the design description?

* What encryption are you actually using? If you rolled your own, then well.. good luck.

* How could you ensure end-to-end encryption over multiple protocols, without either completely reverse engineering said protocols? If your answer here would be that you're using a central server where messages get passed between services (and thus decrypted), it isn't end-to-end.

The site is also very flaky. Sometimes it loads, sometimes it doesn't. There are so many questions, and zero answers.

replies(2): >>45107901 #>>45107911 #
DmitryDolgopolo ◴[02 Sep 25 19:30 UTC] No.45107911[source]▶
- Yep. You can read our privacy policy here: https://dimadolgopolovn.notion.site/Amber-Privacy-Policy-256... - Check out the demo in the original post. - We use native API or reverse-engineer a solution depending on the platform. This approach maintains the security standard as high as the original app. Everything is done locally on your computer.
replies(2): >>45107931 #>>45146336 #
devilkin ◴[02 Sep 25 19:32 UTC] No.45107931[source]▶
At that point calling it end-to-end encrypted is not true.
replies(2): >>45107981 #>>45108090 #
1. warkdarrior ◴[02 Sep 25 19:36 UTC] No.45107981[source]▶
What definition of "end-to-end encrypted" do you refer to, if on-device processing does not qualify? Isn't your device one of the endpoints in E2EE?
replies(1): >>45108128 #
2. magackame ◴[02 Sep 25 19:48 UTC] No.45108128[source]▶
In context of instant messaging E2EE usually means that service providers servers don't ever see the plaintext with messages stored on device. Just the transport encryption is already an expectation for all networking.

- Signal: E2EE

- Telegram: by default, nah

- Discord, nah