Closed archie94 closed 5 years ago
Thanks for all the work on this. Forced adoption of Signal isn’t all bad, but it can be improved.
Did a small, hands-on workshop w/this branch yesterday; group of ten users. Signal & encrypted messaging was discussed & demonstrated followed by Haven.
*Users w/no prior knowledge of Haven
This is a tiny sample size from a tech-forward city. It did however contrast basic:advanced users and how they fell about learning two apps at the same time.
Users that understood encryption were highly receptive to using/registering Signal.
Some crashes were found when remote number is used without proper verification. Overall, better feedback than expected.
C’mon, Google, do the right thing.
Some very insightful metrics there. Signal verification flow needs some UX improvements. Right now there is no way to tell whether verification is a success or failure. In the coming week will dig into the signal-CLI and see if something can be done.
Yes, a basic step through Signal onboarding setup, explaining how to verify, would be helpful. We also need to explain the concept of whether you need a second "virtual" phone number or not.
One idea I had was to see if Signal was installed on the phone or not. If not, then just go ahead using the device's built in phone number. Otherwise, we can show a screen that says "Looks like you are already using Signal on here. You'll need to get a second number, and here is how."
No progress from Google contacts. Going to merge this, and then figure out a way to keep SMS as an option through an external APK of some kind, or perhaps a flavored build for F-Droid / APK download.
Aims to solve #364
Changes
SEND_SMS
permission -> removed remote SMS notification feature.Some thoughts: