Tag: Google

Hello, Gemma 4: Google’s newest Gemma model is now both open-weight and open-source

Imagine pulling a powerful, multimodal AI down from the cloud and running it on your phone, laptop, or Raspberry Pi — without paying subscription fees or signing an NDA. That's the real-world shift Google just nudged forward: Google's newest Gemma model is now both open-weight and open-source, available under Apache 2.0 and tuned for edge devices and developer ecosystems. This release feels like the moment the slogan “AI for everyone” stops being marketing and starts being practical. (blog.google)

Why this matters now

For years, the most capable models have lived behind corporate APIs and closed licenses. That created a gulf: cutting-edge capabilities for companies that could pay and constrained experimentation for everyone else. Gemma 4 chips away at that gap by shipping weights and tooling that developers can use, modify, and redistribute under a familiar open-source license. The result is faster innovation, more competition, and a broader base of people who can build with frontier AI. (eweek.com)

• It’s multimodal: text, images, and edge variants support audio and video patterns.
• It’s licensed permissively: Apache 2.0 removes many enterprise/legal frictions.
• It’s optimized for the edge: small variants target phones and other local devices. (blog.google)

What Gemma 4 brings to the table

Gemma 4 is a family rather than a single model. Google released several sizes — from lightweight E2B/E4B edge models to more capable 31B dense and 26B MoE variants — so developers can pick performance, latency, and cost trade-offs that fit their projects. The family is built on research from the Gemini line, but the emphasis here is on practical, runnable models for real systems. (blog.google)

Performance highlights include strong reasoning and multimodal understanding for models in their class, and benchmarks show Gemma 4’s 31B variant punching well above its weight on some tasks. More importantly, Google released Gemma 4 with day-one support across major inference engines and ecosystems — Hugging Face, Ollama, llama.cpp, NVIDIA NIM, vLLM, and more — so you don’t need proprietary tooling to get started. (build.nvidia.com)

How to try Gemma 4 (quick guide)

If you want to tinker, here are straightforward paths people are already using:

• Hugging Face: models and model cards are available in Google’s Gemma collection for immediate download and use with Transformers-based tooling. (huggingface.co)
• Google AI Studio and Edge Gallery: run the larger models in cloud dev environments or test edge variants on Android via Google’s developer apps. (blog.google)
• Local runtimes: community ports and quantized builds run on llama.cpp, Ollama, and other local engines — making phone-based, offline experiences viable. (huggingface.co)

Transitions between cloud and edge are smoother here because of the model sizes and pre-built engine integrations. Expect rapid community releases for quantized GGUF builds and optimized kernels in the next few days — the open-weight moment invites that energy.

The open-weight vs. open-source nuance

A quick clarification: "open-weight" has been used by model makers to mean the raw weights are available, but not all training data, training code, or full architecture details are published. Gemma 4 distinguishes itself by being released under Apache 2.0, a permissive license, and by shipping day-one ecosystem support — moving it closer to what practitioners reasonably call "open-source" in practical terms. That doesn’t mean every research artifact is public, but it does mean you can build, redistribute, and commercialize in ways you typically could with other Apache-licensed projects. (blog.google)

The developer opportunity and the risk landscape

Open weights democratize experimentation. Startups will be able to iterate on custom fine-tunes, on-device assistants will gain local intelligence, and defenders of privacy can architect systems that never send user data to third-party servers. This is a big win for builders and privacy-minded products. (techspot.com)

But with openness comes responsibility. Wider access means easier misuse and faster propagation of unvetted variants. Google and the community will need to keep working on guardrails, robust moderation tooling, and responsibly labeled checkpoints. The release also re-energizes debates about transparency in training data, provenance, and the ethics of model redistribution.

The broader tech context

Gemma 4 arrives into a field that has rapidly normalized large open-family releases. Other major players have pushed open-weight models in the past year, and the ecosystem has grown rich with quantization tools, inference optimizers, and hardware-specific kernels. Gemma 4's Apache licensing plus day-one integration with major runtimes could accelerate an already fast-moving open model marketplace. Expect more on-device AI experiences, new SaaS products built on local inference, and robust community forks. (techcrunch.com)

Final thoughts

My take: releasing Gemma 4 under Apache 2.0 is an inflection point. It lowers the bar for powerful, private, and portable AI, while re-centering developers in the innovation loop. The next few months will show whether community governance and responsible-release practices keep pace with the technical leaps. For now, we have a legitimately practical, high-quality open model family to explore — and that’s worth celebrating.

Sources

• Google DeepMind — Gemma 4: Our most capable open models to date. https://blog.google/innovation-and-ai/technology/developers-tools/gemma-4/ (blog.google)
• Hugging Face — Welcome Gemma 4: Frontier multimodal intelligence on device. https://huggingface.co/blog/gemma4 (huggingface.co)
• Yahoo / Mashable coverage — Google launches Gemma 4, a new open-source model: How to try it. https://tech.yahoo.com/ai/gemini/articles/google-launches-gemma-4-open-222148736.html (tech.yahoo.com)
• NVIDIA NIM model card — Gemma-4-31B IT Model by Google. https://build.nvidia.com/google/gemma-4-31b-it/modelcard (build.nvidia.com)

Hook: Fitbit gets hungrier — and thirstier — for your data

Today’s Fitbit update is more than a fresh coat of paint. The Fitbit Public Preview adds food & water logging, joining a broader app redesign and AI-powered personal health coach that Google has been rolling out in preview form. If you’ve been watching the gradual migration of Fitbit into Google’s ecosystem, this is one of those moments where the product starts to feel like the future Google described — and also like the kind of change that will stir conversation among longtime users.

What just landed in the Public Preview

• The app now includes built-in food logging and water tracking so users can set calorie targets, log meals, and track hydration directly in the Fitbit app.
• The Public Preview — originally focused on Premium subscribers and select Android users — is expanding access so free-tier users can try the redesigned interface and these nutrition features.
• This expands a broader push: the redesigned app pairs a Material 3-inspired UI with a Gemini-powered “personal health coach” that uses your activity, sleep, and (now) nutrition data to give suggestions.

Why this matters: nutrition and hydration are two of the largest behavioral levers for health outcomes. Bringing those logs into Fitbit’s new coaching experience is an obvious next step — it helps the AI see the whole picture, not just steps and sleep.

Why the timing and the rollout matter

Google started previewing the AI-powered Personal Health Coach last year, first to Premium users and a limited set of devices. The rollout has been gradual: Android users saw the earliest access, then iOS, and now more people on the free tier are being invited into the Public Preview.

That phased approach is pragmatic. It lets Google collect feedback, quiet bugs, and iterate on features that touch sensitive user data — especially when the product starts to take in things like nutrition entries and (in other recent previews) medical records or continuous glucose monitor data.

Still, phased rollouts create friction: some users will see new nutrition and water screens immediately; others will wait days or weeks. And historically, Fitbit’s food/water logging has been a touchy subject for users when it’s buggy or when sync behavior with third-party apps breaks.

The redesign: not just cosmetics

• Material 3 visuals, smoother animations, and a reorganized home experience aim to make daily logging simpler.
• The Personal Health Coach (Gemini-based) turns logs into conversational guidance: it can suggest adjustments, summarize patterns, and help set targets.
• Beyond nutrition, Google is adding resilience and sleep improvements, and plans to let eligible users link clinical records for a fuller health snapshot.

Put simply: Fitbit now wants to be both the place you record what you do and the place that explains what it means. That double role increases the product’s value — and the stakes.

What users should watch for

• Data continuity: If you have historic food and water entries, confirm those sync correctly. Some preview users historically reported migration hiccups after big app updates.
• Privacy and permissions: New features that ingest nutrition, hydration, and (in other previews) medical data mean you should double-check which Google/Fitbit account type is linked and which permissions you’ve granted.
• Feature parity: The Public Preview sometimes exposes a UI before all back-end pieces are in place. Expect some functionality to behave differently or appear later.
• Integration with third-party food trackers: If you rely on MyFitnessPal, Lose It!, or a smart scale to feed Fitbit, watch whether those integrations continue to sync smoothly.

A quick user checklist

• Update the Fitbit app to the latest version from your app store.
• Open Settings → Profile → Join Public Preview (if available) to get access.
• Back up or note important historical data if you depend on it daily.
• Review app permissions and the account linked to Fitbit (Google vs. legacy Fitbit account).

The broader picture

This update is a predictable but meaningful step in Fitbit’s evolution under Google. AI coaching without context is limited; nutrition and hydration bring context. Google is clearly aiming to stitch together device data, user-entered behavior, and — at times — clinical data to create a more personalized experience.

But that integration raises familiar trade-offs: convenience versus control, helpful nudges versus surprising recommendations, and the long-standing tension between new platform design and the muscle memory of long-term users. Some will love having one place to log a meal and ask an AI why their readiness score dropped; others will bemoan changes to workflows that used to be simple and reliable.

My take

I’m encouraged by Fitbit bringing food and water logging into the Public Preview — the product only becomes useful if it measures the things that actually move the needle. That said, Google will need to keep listening. Small quality-of-life details (quick add buttons, barcode scanning, consistent units for water, and reliable third-party sync) often determine whether people actually keep logging.

If Google gets those details right and keeps the privacy guardrails clear, this could be one of the stronger examples of practical, helpful AI in wellness. If not, it’ll feel like a shiny interface on top of the same old friction.

Sources

• Fitbit Public Preview adds food & water logging, more as app redesign comes to free users — 9to5Google
  https://9to5google.com/2026/03/31/fitbit-app-redesign-free/

• New Fitbit features for tracking medical records, sleep and metabolic health — Google Blog
  https://blog.google/products-and-platforms/devices/fitbit-personal-health-coach-updates-2026/

What’s new with Google Messages this March?

The headline you’ve probably seen — What new Google Messages features are rolling out [March 2026] – 9to5Google — captures exactly the slow, tease-y way Google ships changes to its messaging app. Google Messages for Android keeps evolving, and this March’s rollouts feel less like a single “big bang” update and more like a steady stream of practical additions that quietly make conversations better. In this post I’ll walk through the most useful changes, why they matter, and what this incremental approach says about Google’s strategy for RCS and SMS messaging. (9to5google.com)

Fresh features you might already have (or will see soon)

• Real-time location sharing inside conversations — Google is adding a robust location-sharing flow so you can share your live location directly in a Messages chat for a set time, and stop sharing whenever you like. This ties into Google’s broader “Find Hub” capabilities and feels like closing a long-standing gap versus dedicated apps. (androidauthority.com)

• @mentions for group chats — Finally: you can flag a particular person in group texts so they get pinged even if they’ve muted that conversation. It’s small, but in active groups this reduces the “who was that for?” noise. The feature has been in progressive rollout and appears in A/B tests before wider availability. (9to5google.com)

• Trash folder for deleted messages — A safety net for accidental deletes. Instead of losing threads forever, Messages now offers a Trash folder where recently deleted messages linger for some days. It’s the kind of quality-of-life fix that people notice the moment it’s there. (androidcentral.com)

• UI and media tweaks — Gallery and camera flows keep getting polishing: a cleaner media picker and updated sharing UI to make photos and clips easier to find and send. These are the iterative design moves that reduce friction when you’re trying to send something quickly. (androidpolice.com)

Transitioning from small fixes to bigger platform shifts, these changes are part of a broader Pixel/Android feature push that Google bundles into monthly Pixel Drops and wider “New on Android” updates. (blog.google)

Why the March 2026 rollouts matter

First, Messages is no longer “just SMS.” It’s the front line for Google’s hopes around RCS — richer messaging with typing indicators, read receipts, media sharing, and now better cross-platform functionality as Apple and Google experiment with interoperable encrypted RCS. Improvements like location sharing and mentions are practical signs that Google wants Messages to be a daily utility, not an afterthought. (9to5google.com)

Second, Google’s A/B testing approach means not everyone sees everything at once. That slow, selective rollout helps Google gather usage patterns and catch bugs before wider release, but it’s also frustrating for users who read about a feature and don’t have it yet. For power users, this creates a staggered experience across friends and devices. (9to5google.com)

Third, the integration with Pixel Drops and the broader Android feature set shows an ecosystem play: Messages benefits from platform-level services (like Find Hub) and the Pixel team’s cadence, which sometimes speeds the delivery to Google’s own phones before others. That’s worth remembering when you’re juggling rollout timelines across brands. (blog.google)

The product trade-offs behind steady rollouts

• Pros of gradual rollouts:

  • Safer launches with real-world telemetry.
  • Ability to experiment and refine without massive fallout.
  • Easier detection of device- or carrier-specific issues.

• Cons for users:

  • Fragmented experience — your friend might have a feature you don’t.
  • Feature fatigue — incremental updates feel less exciting.
  • Confusion about what’s “available” versus “in testing.”

This balancing act is exactly what you’d expect from a platform at the center of messaging between Android, carriers, and now interoperable standards. Google wants to push RCS into everyday use, but it’s tethered to the realities of carriers, device makers, and cross-platform support.

How this fits into the RCS and competition story

Google has been nudging Messages toward parity with apps like iMessage and WhatsApp for years. The big picture includes RCS adoption, end-to-end encryption efforts, and UI parity with modern chat features. March’s additions — practical sharing tools and group management improvements — are less flashy than OTT platform rivalry, but they’re the plumbing that makes RCS useful day-to-day.

Also, the timing with Pixel Drops and “New on Android” releases shows that Google layers messaging updates onto broader OS and Pixel feature sets — which helps integration but can delay access for non-Pixel users. Expect more iterative improvements rather than a single revolutionary update. (9to5google.com)

What to watch next

• Wider rollout of encrypted or cross-platform RCS messages between Android and iPhone.
• Further integration with Find Hub and Google services (e.g., travel, location recovery).
• UI refinements that take redundancy out of conversations — better search, smarter media handling, and clearer group management.

These are the areas where Messages could evolve from “good” to “essential” for people who already text a lot.

Brief takeaways

• Google Messages in March 2026 is improving through practical additions like live location sharing, @mentions, and a Trash folder.
• Rollouts are incremental and A/B tested — expect staggered availability.
• The changes support Google’s long-term push to make RCS a reliable, everyday messaging standard across Android (and potentially beyond).

Final thoughts

These updates don’t scream reinvention, but they are surprisingly impactful in daily use. Small fixes — a Trash folder, the ability to nudge someone in a group, or sharing your location without leaving the chat — reshape how you actually text. That’s the quiet power of thoughtful product iteration: it doesn’t always make headlines, but it improves the minutes of your life you spend tapping “Send.”

Sources

• What new Google Messages features are rolling out [February 2026]. 9to5Google. https://9to5google.com/guides/google-messages/
• Google Messages is getting a location-sharing feature. Android Authority. https://www.androidauthority.com/google-messages-location-sharing-march-2026-3645963/
• March Pixel Drop blog post. Google Blog. https://blog.google/products-and-platforms/devices/pixel/march-2026-pixel-drop/
• Google Messages Trash folder and group features. Android Central. https://www.androidcentral.com/apps-software/break-the-chaos-google-messages-lets-you-mention-that-one-friend-who-never-pays-attention