MoineauWorld.com – Where Cooking Meets Tech & Everything Between

Tag: Google Wallet

Rivian Digital Key: Wallet-Based Access | Analysis by Brian Moineau

Posted on by Brian Moineau

A key in your pocket: Rivian Digital Key brings Gen 2 cars into your phone wallet

There’s a tiny moment of delight when you walk up to your car, your phone in your hand (or not), and the vehicle simply knows you’re there. Rivian just made that moment more seamless. On December 18, 2025, Rivian began rolling out Rivian Digital Key for Gen 2 R1T and R1S vehicles — a native digital-wallet car key experience for iPhone, Apple Watch, Google Pixel, and Samsung devices that lets owners unlock, share, and start their Rivian without the dedicated fob or the Rivian app’s Bluetooth-only workflow.

This isn’t just another “app feature” patch. It marks a bigger shift toward platform-level convenience, tighter hardware integration (Ultra-Wideband and NFC), and the standardization of car access across ecosystems.

Why this matters now

  • Smartphones have increasingly replaced physical items (boarding passes, credit cards, transit passes). Car keys are the next obvious candidate — but only when the integration is reliable and secure.
  • Rivian’s Gen 2 cars were built with newer connectivity and UWB hardware that make native wallet keys practical in ways first-gen Bluetooth approaches weren’t.
  • By supporting Apple Wallet, Google Wallet, and Samsung Wallet, Rivian avoids locking users into a single OS and taps into the “works-as-you-expect” experience people now expect from modern devices.

What Rivian Digital Key does

  • Native wallet integration: Add your Rivian Gen 2 car key to Apple Wallet (iPhone & Apple Watch), Google Wallet (Pixel), and Samsung Wallet.
  • Multiple unlocking modes: Ultra-Wideband (UWB) for precise hands-free proximity; NFC fallback that can work even when the phone is in power-reserve (Rivian notes up to ~5 hours on supported devices).
  • Key sharing: Send digital keys to family and friends instantly — no physical handoffs.
  • Broader device support: Works across major smartphone ecosystems to maximize owner convenience.
  • Requirements and flow: The feature arrives with Rivian’s 2025.46 OTA and Rivian Mobile App update (3.8.0); some Android implementations require recent OS versions (Android 15 / One UI 7.0 mentions in reporting).

(Technical specifics and exact device compatibility can vary; check your vehicle’s OTA status and the latest Rivian app release notes before expecting the feature on your car.)

How this compares to the old way

  • Old: Rivian’s earlier digital key used the Rivian app and Bluetooth Low Energy. It worked, but could be slower, less precise, and was app-dependent.
  • New: Keys live at the OS level (Wallet apps), enabling Express/Power Reserve, tighter proximity detection through UWB, native watch support, and a fallback NFC path if the battery is depleted. In short: faster, more reliable, and more integrated.

The broader context

  • Rivian is part of a broader industry trend: automakers are adopting the Car Connectivity Consortium (CCC) standards and integrating with phone wallet ecosystems. Apple Car Key and similar Android standards have been rolling out across several manufacturers in recent years.
  • This update arrives alongside other notable 2025.46 features (Universal Hands-Free driving modes and other Gen 2 improvements), signaling Rivian’s push to refine both autonomy and convenience features in tandem.
  • The move also reflects product lifecycle strategy: many automakers concentrate new platform-level integrations on newer vehicle generations, which can leave earlier owners waiting or requiring hardware retrofits.

Opportunities and caveats

  • Opportunities:

    • Simpler sharing: temporary or permanent digital keys can replace lending physical fobs.
    • Reduced lockout worry: Express/Power Reserve offers peace-of-mind if your phone dies.
    • Cross-platform parity: support for iOS and major Android ecosystems lowers friction for households with mixed devices.

  • Caveats:

    • Compatibility: older phones or Gen 1 vehicles may not gain the same functionality.
    • Security and privacy: while wallet-based keys typically have strong device-level protections, owners should follow best practices (device passcodes, biometric locks, OS updates).
    • Reliance on hardware: UWB and NFC behaviors depend on device and vehicle hardware; real-world performance can vary by device model and environmental conditions.

What this means for owners and would-be buyers

  • Gen 2 Rivian owners should look for the 2025.46 OTA and update the Rivian app (3.8.0+), then follow the wallet setup flow to add the car key.
  • If you’re evaluating Rivian vs. other EVs, consider how important native wallet integration is to your daily routine. For many buyers, the convenience of wallet-based keys will be a useful tie-breaker.
  • If you own a Gen 1 R1 and hoped for parity, note that many of these features rely on Gen 2 hardware and may not be fully transferable without retrofits.

A few practical tips for setup

  • Update the Rivian mobile app to the version that mentions wallet support (3.8.0 or later) and ensure your vehicle has received the 2025.46 OTA.
  • For iPhone owners: confirm iOS 17.4.1+ and Wallet readiness; for Apple Watch, make sure NFC works and watchOS is up to date.
  • For Android owners: check Google Wallet or Samsung Wallet compatibility and any OS version requirements (reporting has referenced Android 15 / One UI 7.0 for some features).
  • Keep your device OS updated and enable device-level protections (Face ID/Touch ID, PIN/passcode) for security.

My take

Rivian Digital Key is one of those “small” features that changes daily life more than you’d expect — especially once you get used to your phone being the primary interface for everything. By moving car access into native wallets and leveraging UWB/NFC, Rivian has reduced friction and added resilience (power reserve) against common real-world annoyances. It’s also a vote of confidence in cross-platform standards: owners shouldn’t need to swap ecosystems to get convenience parity.

That said, manufacturers must balance excitement with clarity: clear communication about device and vehicle compatibility will be crucial to avoid confusion, particularly between Gen 1 and Gen 2 owners. If Rivian keeps this momentum — and continues to make ownership feel like a continuous software upgrade — these moments of polish could become a meaningful competitive advantage.

Final thoughts

Digital keys are a practical example of how cars are becoming platforms rather than standalone devices. When automakers, OS vendors, and standards groups converge on simple, secure experiences like this, the payoff is everyday delight: fewer fumbling moments at the door, easier sharing with family, and one less physical item to misplace. Rivian’s rollout for Gen 2 is a smart step in that direction — now it’s about execution, clarity, and getting the experience right for every owner and device.

Sources



Related update: We recently published an article that expands on this topic: read the latest post.

Related update: We recently published an article that expands on this topic: read the latest post.

Related update: We recently published an article that expands on this topic: read the latest post.

Essential Android Apps for Non‑Tech Users | Analysis by Brian Moineau

Posted on by Brian Moineau

When the default just isn’t good enough: 12 Android apps I tell non-techies to try

Preinstalled apps are convenient. They’re ready the moment you unbox a phone and usually “just work.” But convenience isn’t the same as clarity, control, or comfort — especially for people who prefer simplicity over tinkering. I read Andy Walker’s recent roundup at Android Authority and pulled together a friendly, practical take geared toward helping non-technical users (and the people who help them) get more usable, secure, and accessible phones without turning setup into a weekend project.

Why swap the defaults?

  • Phones ship with apps that prioritize broad compatibility and integration — great for basic use, not always great for clarity.
  • Alternatives can improve accessibility (larger fonts, better talkback support), privacy (password managers, 2FA), and day-to-day simplicity (cleaner gallery or browser apps).
  • Many alternative apps require a one-time setup from someone more comfortable with tech, but after that they often “set-and-forget,” which is perfect for non-techies.

Below I summarize the apps Andy recommends, why they matter for non-technical users, and practical tips for getting each one running smoothly.

Apps that make life easier (and why)

  • TeamViewer

    • Why: Remote support without being in the same room. Perfect when you need to fix settings, install apps, or transfer files for a relative.
    • Tip: Install QuickSupport on the phone being helped and the full TeamViewer app on the helper’s device.

  • Vivaldi (browser)

    • Why: Cleaner UI, built-in ad blocking and dark mode — fewer accidental taps and less visual clutter than some preinstalled browsers.
    • Tip: Configure ad‑block and dark mode once, then lock the home page to something familiar for the user.

  • Google Wallet

    • Why: Contactless payments, boarding passes, loyalty cards all in one place — more useful than a lone OEM wallet on many phones. Google also documents accessibility features for Wallet. (support.google.com)
    • Tip: Walk the user through adding one card first and show them how to tap to pay once.

  • Nobook (lightweight Facebook client)

    • Why: A slim, fast alternative to the bloated official Facebook app — less data, fewer ads, simpler feed.
    • Tip: Nobook may be hosted on GitHub/F-Droid; ask a tech-savvy friend to install it the first time.

  • Bitwarden (password manager)

    • Why: Centralizes passwords behind one master password so non-techies don’t reuse weak passwords or get locked out — widely recommended and open source. Reviews from trusted outlets highlight its security and cross-platform ease. (wired.com)
    • Tip: Set up the vault and autofill options yourself, then show the user how to unlock the vault on their phone.

  • Google Authenticator (2FA)

    • Why: Multi-factor authentication is a major security upgrade over passwords alone. Google Authenticator is straightforward and ties into the Google ecosystem.
    • Tip: For recovery, note backup codes or link to an account recovery method so losing the phone doesn’t lock them out.

  • Localsend

    • Why: Fast local transfers over Wi‑Fi without cloud uploads — great for sharing large videos at family gatherings.
    • Tip: Install on both devices and demonstrate a quick “send/accept” transfer so it becomes muscle memory.

  • Google Photos and Google Gallery

    • Why: Photos offers automatic backup and search; Gallery gives a simple, familiar offline view. Together they protect memories without confusing album logic.
    • Tip: Enable backup over Wi‑Fi and show how to find photos from events or dates.

  • Tubular (YouTube frontend)

    • Why: Ad-light, configurable YouTube experience that avoids accidental ad taps and unnecessary accounts. Good for older users who just want to watch.
    • Tip: Tubular is usually available via F‑Droid; handle the initial install and explain basic playback settings.

  • Files by Google

    • Why: Simple file manager with safe folder and sensible categories — easier than digging through a raw file tree.
    • Tip: Use Files to tidy downloads and move important PDFs into the Safe Folder for extra protection.

  • Gboard (keyboard)

    • Why: Robust autocorrect, swipe typing, and accessibility features that reduce typos and the frustration of small keys. Many OEM keyboards don’t match its polish.
    • Tip: Changing keyboards takes a few steps; assist once and set Gboard as the default.

Practical setup checklist for helpers

  • Back up important data first (photos, contacts). Always.
  • Create or migrate a Google account if needed — many apps rely on it.
  • Install and configure Bitwarden, Authenticator, and Google Wallet for the user; show them how to unlock/use each once.
  • Demonstrate one or two everyday actions (paying with Wallet, accepting a LocalSend file, unlocking Bitwarden) so the new behavior sticks.
  • Explain recovery options: backup codes, trusted contacts, and where they wrote that master password down (not on their phone).

Quick wins for accessibility and simplicity

  • Increase font size and set a simple home screen layout with only the most-used apps.
  • Enable TalkBack or Voice Access for users with visual or motor accessibility needs.
  • Limit auto-updates for apps that break behavior unless you manage their device remotely.

What to remember

  • Defaults are fine for many people — but small alternatives can fix big annoyances (ads, confusing menus, missing accessibility).
  • A one-time guided setup is often all it takes to give a non-tech user a calmer, safer phone experience.
  • Security apps (password manager + 2FA) offer the largest long-term benefit for minimal ongoing effort.

My take

If you help someone with a phone even once a year, spending an hour to replace a handful of default apps is time well spent. The payoff isn’t novelty; it’s fewer calls saying “I accidentally tapped an ad,” fewer password resets, and fewer lost photos. Start with Bitwarden + a simple authenticator, make sure photos are backed up, and choose one interface-improving app (Gboard or Vivaldi) to reduce daily friction. That small bundle will make the device more understandable and much less stressful for non-tech users.

Sources



Related update: We recently published an article that expands on this topic: read the latest post.