Every week, I examine somewhere in the neighborhood of a hundred app updates while looking for changes. The most interesting things turn into APK Teardowns or Download posts. Many of the remaining updates are unremarkable, amounting to a few bug fixes, routine updates to libraries, or even just pixel-level adjustments to layouts and images. However, there are usually a few updates that land somewhere in between. I don't want to spam readers with dozens of short posts, but I hate to ignore things that people might want to know about, so I'm going to wrap up the leftovers for a little weekend reading and call it Update Notes.
Special thanks to נתנאל מ for the great hero image on this post!
Google Photos v4.2
Surprisingly, the 4.2 update landed with virtually no sign of change, save one. The RAW recommendation feature is now live, albeit not the most exciting change.
RAW editor suggestion
The RAW editor suggestions appeared in the v4.1 teardown. Now, if you are viewing a RAW image and tap the button to make edits, you'll see an Edit In card pop up. The top entry will be Photos, but it has a small line of warning to explain that it has limited support for RAW. This is followed by other image editors on the device, and then an entry at the bottom that links to a custom Play Store list containing more RAW editors.
Despite bumping the major version number to 12, the latest update doesn't appear to have made any revolutionary changes to the look or experience in the Play Store. I'm inclined to assume the team simply prefered to carry the one rather than ship a v11.10. Nevertheless, there are still a couple of things of interest in the last two updates.
Donating mystery apps to Play Protect [v11.9 Teardown]
Play Protect is effectively Google's version of a virus scanner for Android. Sideloading remains plenty common, and since there's a danger that malware-laden apps might be spreading, Google is raising the stakes to track down unsavory APKs. There's text for a new prompt asking users to submit unfamiliar apps to Play Protect for further scanning.
<stringname="package_malware_banner_send_play_protect">Send app to Play Protect?</string> <stringname="package_malware_checkbox_disclaimer_send_play_protect">You can change this setting in Play Protect settings</string> <stringname="package_malware_checkbox_message_send_play_protect">Always send unknown apps</string> <stringname="package_malware_message_send_play_protect">Play Protect hasn\'t seen this app before. Send it for a scan to detect harmful behavior and increase protection for you and others.</string> <stringname="package_malware_negative_button_send_play_protect">CANCEL</string> <stringname="package_malware_positive_button_send_play_protect">SEND</string>
This doesn't read like a prompt for simply scanning apps locally, I'm pretty certain this is intended to transfer APKs back to Google for a more thorough analysis. In general, this is a pretty good thing, though I can imagine some degree of privacy concerns. I'm just curious if this will attempt to send back beta builds of apps that are handed out separately from the Play Store, or even just developer builds.
Call log permission [v12.0]
There is a very minor change the organization of permissions in v12. A new group for the Call Log was added, and naturally, read and write permissions were moved into it from the Phone group.
Recommending tablet apps, assuming you already have them [Teardown]
It looks like there may be a recommendation dialog popping up to recommend tablet-optimized apps if you already had them installed on other devices. Basically, the Play Store will look at the apps you already own and make them more visible if you are using a tablet or some other device with a larger screen (e.g. a Chromebook).
<stringname="large_screen_reinstall_dialog_title">Install apps from your devices</string> <stringname="large_screen_reinstall_dialog_subtitle">We found %1$d apps from your account that are optimized for this device</string>
With Inbox inevitably shutting down in the future, all eyes are on Gmail to be the one size fits all email app. You're not going to find anything too significant in the last few updates, but there's at least one familiar feature preparing to make it's mobile debut: Smart Compose.
Smart compose [Teardown]
If you've used the web interface for Gmail in the last few months, you already know about Smart Compose. It basically tries to write emails for you. For fast typists, it might save you a couple seconds from time to time, but it's great for anybody that has to hunt and peck at the keyboard. But think of how much more useful it would be on smartphones where the keyboard experience isn't wonderful for anybody. That will be happening... soon?
<stringname="sc_pref_title">Smart Compose</string> <stringname="sc_pref_summary">Show predictive writing suggestions</string> <stringname="sc_onboarding_title">Smart Compose</string> <stringname="sc_onboarding_summary">Writing suggestions appear as you type. Swipe right to accept.</string>excerpt from /xml/gmail_account_preferences.xml <CheckBoxPreferenceandroid:title="@string/sc_pref_title"android:key="sc_enabled"android:summary="@string/sc_pref_summary"android:defaultValue="true"/>
There are a few lines for the setting that enables/disables Smart Compose. Judging by the location of the toggle, it seems likely that it will be enabled on a per-account basis.
Google Keep used to title its widgets as just "Google Keep." The latest version has replaced that name with descriptive titles that actually mean something to the widgets. They are now called Note List and Quick Capture.
The latest Google+ update continues a trend of adding quite a bit behind the scenes for what is obviously a major update to the social network. But unlike those last few releases, this one is promising a somewhat more mundane update to the moderation tools for communities.
Community moderation [Teardown]
There's a very large number of new strings and other resources related to community moderation. The content below is largely centered around approving posts, banning members, and handling requests. Of course, these things already exist in the current interface, but such a large addition likely suggests the interface will be changing, hopefully to make it more streamlined and convenient to use on mobile.
Google Pay updates have been relatively innocuous for the last few updates, but I've wanted to slip them into an Update Notes post to get caught up. There are a few things worth checking out.
Thomas Transit [v2.73 Teardown]
I can't say that I've ever heard of it, but it looks like support for Thomas Transit is in the plans.
<stringname="thomas_title">Thomas Transit</string> <stringname="thomas_pass_name">thomas pass</string> <stringname="thomas_pass_not_supported">thomas passes are not yet supported</string> <stringname="thomas_topup_description">Add money as you need it</string> <stringname="thomas_topup_name">thomas money</string> <stringname="thomas_country">Country</string>
QR Code money transfers [v2.74 Teardown]
Now that Google Pay and Google Pay Send (formerly Google Wallet) are fully merged, it's time for new features. Now there appears to be a QR code money transfer in development that would allow users to send money to each other by just scanning a code on the other person's phone.
<stringname="qr_entry_label">QR code</string> <stringname="qr_tutorial_image_description">Image of a phone scanning a QR code</string> <stringname="qr_tutorial_open_button">Continue</string> <stringname="qr_tutorial_screen_instructions">Scan a QR code to easily transfer money to a person nearby.</string> <stringname="qr_tutorial_screen_title">QR code payment</string><activityandroid:name="com.google.commerce.tapandpay.android.p2p.qrcodes.QRCodeTutorialActivity"android:exported="false"android:noHistory="true"android:theme="@style/Theme.GooglePay.NoActionBar"/>
No real details are exposed beyond the fact that this is peer-to-peer and not a way to make payments at businesses. Aside from that, it's not really clear if there are limits to how much can be sent, to whom, and if there are any other terms.
Alright, this name has been plaguing me for the better part of a year. I've been aware of the "thermo" name roughly since December, and a few weeks ago I thought there was enough to at least begin discussing it, but it wasn't until the v2.75 update that I got the one clue that finally explained what it actually is. In short, it's a South Korean payment method that appears to be useful for both purchases and mass transit. This was finally explained thanks to the presence of a currency symbol for South Korean Won on a line that mentions a fee for switching cards.
Google Pay is expanding to cover more financial scenarios, and one that's on the list is a discount for people that are under a certain age. The interface asks for a birth date, but otherwise doesn't explain how or if any meaningful verifications are taking place.
<stringname="birthday_input_label">Input your birthday info to apply for discounts!</string> <stringname="birthday_discount_text">Enter your birthday to check if you\'re eligible for a youth discount (optional)</string> <stringname="applying_for_discount_status_label">Applying for discount, please wait</string> <stringname="already_have_discount_label">You always have youth discounts!</string> <stringname="check_discount_lable">Check discount eligibility</string> <stringname="checking_discount_status_label">Checking your youth discount status, please wait</string> <stringname="discount_setup_successful_label">Congrats, you are set up for youth discounts!</string> <stringname="provider_name_with_youth_discount">%1$s Youth</string>