Google’s Messages app came out with a brand new update this week, and while it’s sporting a major new version number, the changes are fairly moderate. It’s now possible to give custom names to your group chats, and there’s a tweak to the UI that makes Messages look a lot more like Google’s Contacts and Phone apps. There are also several things to discuss in a teardown, particularly with regards to RCS.
- Renaming group chats
- Color changes for contacts without pictures
Renaming group chats
Group chats are great for coordination or keeping up with friends, but the way they were displayed in the main list was sometimes problematic. The Messages app would simply take the group members and list each by their first name with a comma separating each member. This worked, but it was easy to confuse the group chat for a private chat with the first person listed, and nearly impossible to discern multiple group chats that happen to include a few of the same people.
With the latest update, Messages now allows you to define your own name for group chats. Simply open the group chat you wish to rename, find Group Details in the overflow menu, and look for a new field at the top of the detail screen where you can define your own group name. The new name will be shown in the conversation list and at the top of the conversation itself.
New colors for non-pictured contacts
Left: v3.9. Right: v4.0.
Back in October, an update to the Google Contacts app brought a small, but very welcome (imho) change to the styling used for contacts that didn’t have pictures. Previous versions placed the first letter of the name on a pastel background. With the updated look, the shapes stayed the same, but the letters were made white and the colored backgrounds were pushed to vibrant colors that provided more contrast.
It took a few months, but the new version of Messages has adopted the same change, and now all three of Google’s primary contact-based apps (Phone, Messages, and Contacts) are using the same styling for contacts. Cheers for consistency! … err, well, the colors used for each contact don’t actually match across apps, but I’d rather not nitpick this.
The features discussed below are probably not live yet, or may only be live for a small percentage of users. Unless stated otherwise, don’t expect to see these features if you install the apk. All screenshots and images are real unless otherwise stated, and images are only altered to remove personal information.
Reminder to turn off airplane mode
Admit it, there was at least one time in your life that you turned on airplane mode and then forgot about it. Messages currently doesn’t give you much of a heads up about this, only placing a fairly inconspicuous message across the top of chat windows to let you know there’s no connection. While that might be enough to remind you or I that airplane mode is on, many people might assume they’re in an area without cell service, and even attempting to send a message will only give you a warning that the phone is waiting for a connection.
A new line has been added that suggests Messages will begin detecting airplane mode and reminding users to turn it off. It’s not quite clear if this will provide an interface to disable airplane mode directly from within the app, but even just having the clear reminder is enough.
Sending generic files?
We know RCS allows for larger attachments and a generally richer experience. While most people think about sharing pictures and video, there are still other situations where you might want to share more unusual types of data.
A few new lines have been added that seem intentionally generic, preferring the word “file” in place of terms like “photo” or “video.” It’s entirely possible these strings were written this way to avoid writing multiple variations, or perhaps to acknowledge that attachments could include multiple data types at once, but it could also mean Messages will support sending unknown file types.
<string name=“c2o_contact_share_file_text“>Attach file</string>
<string name=“c2o_file_attachment_size_limit_exceed“>The file you are trying to send exceeds the %s attachment limit.</string>
<string name=“attachment_share_error“>Couldn’t share, try again in a few seconds</string>
I won’t get into the potential side effects or security issues involved with sending generic files, but I think it’s fair to point out that Google may as well support it since other RCS apps will surely allow it.
Curious settings for entering custom numbers
I’m not confident that anything in this section will ever be intended for regular (or even highly technical) users, but I’m including it because it may be of interest to some people that may want to poke around.
There’s text and settings for two new areas where it’s possible to enter a custom phone number.
The first addition is an advanced setting that seems to be related to RCS. The first few lines instruct users to enter a phone number to finish setting up chat features, which is strange since RCS would typically just use the numbers provided by SIMs. Again, that makes this seem like something that may only be intended for testing purposes.
On the other hand, this may be tapping into features of RCS that aren’t widely publicized. This aspect is reinforced by the following text that informs users that the app will occasionally verify the number with your carrier. To me, this sounds a bit like the setup details that would come with enabling multiple (or at least different) devices to receive messages that are sent to a single number, but I don’t want to speculate much without more research.
<string name=“enter_self_phone_number_suggestion“>Enter your phone number in Advanced Settings.</string>
<string name=“phone_number_input_title“>Enter your phone number to finish setting up chat features</string>
<string name=“phone_number_input_subtitle“>You’re a step away from enabling the enhanced chat features you selected earlier</string>
<string name=“phone_number_input_hint“>Your phone number</string><string name=“conversation_list_fast_track_paragraph_multi_sim_with_cost“>To turn on chat features from Google on “%1$s” (SIM %2$d), you accept the %3$s and %4$s. For phone number based message delivery, Google may occasionally verify your number by exchanging your device info with your carrier (SMS charges may apply). You can disable chat services from Settings. %5$s.</string>
<string name=“conversation_list_fast_track_paragraph_with_cost“>To turn on chat features from Google, you accept the %1$s and %2$s. For phone number based message delivery, Google may occasionally verify your number by exchanging your device info with your carrier (SMS charges may apply). You can disable chat services from Settings. %3$s.</string>
<string name=“setting_fast_track_body_with_cost“>By continuing, you agree to the %1$s and %2$s. For phone number based message delivery, Google may occasionally verify your number by exchanging your device info with your carrier (SMS charges may apply). You can disable chat services from Settings. %3$s</string>
<string name=“conversation_list_fast_track_tos_with_cost“>By turning on chat features from Google, you agree to the %1$s and %2$s. For phone number based message delivery, Google may occasionally verify your number by exchanging your device info with your carrier (SMS charges may apply). You can disable chat services from Settings. %3$s.</string>
The second addition is for defining your own SMSC (Short Message Service Center) number, which is basically the service that takes responsibility for storing SMS messages until they can be delivered to the destination. My assumption is that this will allow testing of new services or diagnosing networking issues. Changing your SMS service, especially to a destination that doesn’t exist, would obviously cause messaging to stop working correctly, which is why I doubt this will be exposed to regular people.
<string name=“smsc_number_pref_summary“>SMS might stop working if you change or delete this number</string>
<string name=“sms_message_center_pref_key“>buglesub_smsc_number</string>excerpt from /xml/preferences_per_subscription.xml
<com.google.android.apps.messaging.ui.appsettings.PhoneNumberPreference android:persistent=“false“ android:textSize=“24dp“ android:title=“@string/smsc_number_pref_title“ android:key=“@string/sms_message_center_pref_key“ android:dialogMessage=“@string/smsc_number_pref_summary“/>
RCS is picking up steam, even if the ideal adoption rate and user experience is still a long way from here. Google happens to be experimenting with different messages to introduce users to the new features and let them know how it works. Three different versions of the promotional text are included below. They’re obviously not important to features, but I figured some people might find it interesting.
<string name=“conversation_list_fast_track_popup_title_experiment1“>New! See when friends are typing</string>
<string name=“conversation_list_fast_track_popup_title_experiment2“>Share higher quality photos and videos</string>
<string name=“conversation_list_fast_track_popup_title_experiment3“>Chat features from Google</string>
<string name=“conversation_list_fast_track_popup_subtitle_experiment1“>Plus chat over Wi‑Fi and data, share higher quality photos, and more with others who have chat features</string>
<string name=“conversation_list_fast_track_popup_subtitle_experiment2“>Plus chat over Wi‑Fi and data, see typing indicators, and more with others who have chat features</string>
<string name=“conversation_list_fast_track_popup_subtitle_experiment3“>Share higher quality photos and videos, see typing indicators, chat using Wi‑Fi and data, and more with others who have chat features</string>
The APK is signed by Google and upgrades your existing app. The cryptographic signature guarantees that the file is safe to install and was not tampered with in any way. Rather than wait for Google to push this download to your devices, which can take days, download and install it just like any other APK.