Feature request: Make SMS mode optional on first start

[prinz-z]

I would like to have the option to opt-out of the SMS functionality on first start.. Many people don't have an unlimited plan on SMS or would like to send international messages. Especially for non-technical users, the SMS functionality can be very confusing and can result in (high) costs. A dialog asking whether this app should be used as SMS app with optional PUSH service or as PUSH service with optional SMS fallback or only SMS or only PUSH would help a lot.

[phihos]

+1

Since now is the best time to get fleeing WhatsApp users to use encrypted chat programs, it can't hurt to make it easy to configure TextSecure as a clone of it.

[ghost]

+1

The distinction between data and SMS should be clearer for the average user.

[prinz-z]

In the new version, it asks whether it should replace the SMS service, but
when answering no, the fallback is enabled by default, which I would say
should be disabled by default as it can lead to unintentional costs..

[0xACE]

I should mentions that the cost of sending a regular SMS vs using the network differs. There are providers which have cheaper text messages than it is to use their network, this depends on your dataplan. However I should also mention that I believe that when you're roaming SMS will be cheaper than your network plan...

My understanding of the app was that it would encrypt my SMS/MMS to contacts who also use Textsecure, and would otherwise use regular SMS/MMS. So I guess to me it would make sense to have it activated by default.

I believe that a very novice finds the program off-putting when they start the program for the first time, as they are supposed to answer some questions. They are very cleverly given the option to skip(!). Adding more to it only makes it more complicated. I've helped friends install this and they would ask questions like: "What does it mean by import?", the person didn't understand that the app asked to import all the old messages (person asked it as if it didn't understand the words import/export in that context) I may have been a distraction in that case. I feel like a standard should be agreed on and let advanced users customize according to their own taste as it is today.. I would say using SMS fallback would be more complete, but this is my opinion.

I guess what I wanted to say is, be more careful with adding steps to the First-time-run process...

[monreal]

FYI my sister just sent me an encrypted SMS by accident (she was not registered to the push service yet because it seems to be slow ATM) and she was not pleased :)

[prinz-z]

In my opinion, that's perfectly okay : if you want to use it as a
replacement for the SMS app, the fallback is useful. In case of roaming,
internet is by default not working at all, which means no costs right
away.. In worst case, your message is not sent or not received. I know that
Textsecure was originally intended as a SMS encryption app, but you
shouldn't underestimate the people who are looking for a secure replacement
for Whatsapp right now but do not want to send SMS through this app, like
me.

[GAS85]

+1

It seems very difficult to move my friends from Whatsapp to textsecure as soon I should always make them aware and explain how to disable sms fall-back.
My opinion - default users are looking for a data solution, all who really needs to encrypt sms/mms will be able setup this in options.

[0xACE]

@GAS85 the app is more likely to deliver the message with SMS fallback enabled, hence making it more feature complete. Disabling it just increases chances of messages never being delivered, making the application seem unreliable for message delivery. One could argue that one that doesn't want it could change the settings themselves...

Having fallback enabled:

• Bothers users who have bad SMS/MMS plans when the network method fails
• Ensures greater chance of message being delivered

Having fallback disabled:

• Chance of messages not being delivered within reasonable time (say someone is roaming for example), this in turn bothers users who have good SMS/MMS plans. In turn it gives the user the impression that you app will fail to deliver messages in a reliable fashion.
• I'd say; expect the program to stop working if you're roaming, unless you have a good contract, but then you'd not nag about fallback enabled.

If this gets added to the first-start process, it should at least be optimized, together with the other options, as one could potentially argue that the complete settings menu should be stepped through on the first-start process. Don't bloat the first-start mindlessly... Also giving a user the choice to disable the SMS fallback could potentially lead them to believe the app is unreliable when the network method fails.

Just think it through before you apply changes, the first-start process should be handled with care, consider it to be fragile.

[nysatrok]

This one is very important. I think the current setup process is very confusing to beginners. You can't assume that every user knows that TextSecure can be used as a SMS app and has a SMS fallback mode.

Many assume that a messaging app sends everything over the air. Therefore it is necessary to point out how TextSecure actually works. Currently you have to give your friends a lengthy explanation that TextSecure can be used as an SMS app and how to configure TextSecure if the SMS fallback option is not suitable for them.

At the moment the option to make TextSecure your SMS app is offered after you were asked if you want to import the SMS database. I think the proposal mentioned in #1065 makes much more sense. In this case there would be no need for the SMS import dialog if someone wants to use TextSecure in push-only mode.

[ghost]

I totally agree that the SMS fallback option can be quite ambivalent. There are those normal users and whatsapp-renegades who are confused by the SMS feature and I had to send some of my friends textwalls of explanations of how to use this feature or disable it.

Therefore the setup process and settings-page should be a bit clearer regarding this feature! At first I would let the user choose between the 'Push-Only-Setup' and the 'Complete-Package' - two huge buttons with a small explanation of the underlying features/costs. If the latter one is chosen one might import the existing sms database in a second step as well as setting up a possible notification about what to do, when push is unreachable.

The setup page should represent these two options as well - 'Push-Service' and 'SMS-Options'. Hence I would move the upcoming message about setting up TS to the default SMS App into the SMS-Options-Tab. There you can also activate/deactivate the SMS fallback option as well as the only option which is missing (IMHO):

• a notification if the push-service cannot be used atm and if TS should take the SMS route or try again the push-service in a specific amount of time perhaps

The Push-only and SMS-only-users are obvious. Push is activated and the rest deactivated / SMS is activated and the notification is deactivated. The mixed-user who wants to use TS as SMS App with a little more control about sent SMS' can setup the notification when the push-service is unreachable atm. And the unbothered-user has push and sms fallback option activated and the notification is deactivated.

now reconsidering I would suggest 3 options in the install process:

1. Push-only
2. Let me know when u send a SMS
3. Send em all ;)

edit: uups. I just read #1065 which is a bit more condensed... So a possible visual implementation could be two huge options:

(1) Push-Only (2) Default SMS-App

and two checkboxes asking about the SMS-fallback option and if a notification should ask before sending a SMS in established Push-Conversations

[nysatrok]

This is exactly the problem. TextSecure aims to be layman-friendly but TextSecure might send out expensive messages via SMS and MMS without the user's knowledge. TextSecure might get a bad reputation because it works very differently from what most people expect from a messaging app.

It should be noted that there is a similar discussion in #838 which hasn't been referenced here yet.

@mcginty You seem to be the assignee. What's your position on this issue?

[tinloaf]

Does #984 perhaps do what you want?

[ghost]

For me it does. To get asked prior falling back to sms is all i'm asking for

[generalmanager]

We shouldn't close this issue just yet, because the user is still not asked on which behaviour he prefers on first start/first potential use of SMS.

[Nemo64]

How about not asking on first launch? What if the default setting is on ask, and every time you answer get an option do not ask again? That way the initial setup is still short and the behavior after that is intuitive. A little message with there could be additional costs would be nice then.

[nysatrok]

@mcginty This issue should probably be closed because it seems to be fixed now.

[mcginty]

Thanks @nysatrok