Tag: iOS

TL;DR

• Apple’s 2019 launch of Voice Control in iOS 13 and macOS Catalina, plus 2020’s Screen Recognition in iOS 14, shows the OS can map visible UI to actions—exactly the substrate a more agentic Siri needs. [1][2]
• Bloomberg reported in March 2024 that Apple discussed bringing Google’s Gemini to iPhone features, implying any “smarter Siri” will blend on‑device work with cloud assist that defines cost and latency trade‑offs. [4]
• The real moat isn’t a chatbot veneer; it’s Apple’s OS‑level semantic map—accessibility labels in UIKit/SwiftUI and the App Intents framework, introduced at WWDC22—turning taps into addressable actions rivals can’t replicate on iOS. [3][9]

What the source said

Bloomberg’s March 2024 report by Mark Gurman said Apple and Google discussed integrating Gemini into iPhone AI features, including potential Siri enhancements; the piece framed this as complementary to Apple’s on‑device stack, not a replacement. [4]

Apple itself shipped two relevant building blocks years earlier: Voice Control arrived on June 3, 2019 with iOS 13/macOS Catalina as a system‑wide voice interface, and Screen Recognition landed in 2020 with iOS 14 to infer element structure when developers didn’t supply labels. [1][2]

Apple’s developer materials from June 2022 added App Intents, binding app entities and actions into a structured model that Siri, Shortcuts, and Spotlight can call—an explicit signal that per‑app automation would move from ad hoc to first‑class. [3]

MacRumors coverage in 2024 also highlighted a planned Siri redesign with a chat interface and more on‑device processing in iOS 18, aligning with the trajectory implied by Apple’s accessibility and intents investments. [6]

Why it matters

Accessibility users benefit first because robust “what’s on my screen?” interaction reduces mode errors and cognitive load in daily tasks on iPhones and iPads running Voice Control since 2019. [1]

For developers, semantics decide who wins: clear accessibility labels and App Intents make actions discoverable and routable, whereas missing traits push the system into brittle heuristics that feel broken. [3][9]

If cloud assist enters the loop, economics join reliability: every extra round‑trip to Gemini or a peer model adds dollars and milliseconds, shaping which Siri features scale to millions of daily requests. [4][5]

Historically, Apple’s platform wins—Automator in 2005 on Mac OS X 10.4 Tiger and the 2017 Workflow acquisition that became Shortcuts—came from making automation an OS primitive, not a bolt‑on. [8][10]

Original analysis

Apple’s accessibility stack is the agentic scaffold

Consensus says “Siri just needs a bigger LLM.” That’s a half‑truth. The strategic shift is Apple baking an OS‑level semantic model of the UI—via 2019 Voice Control, 2020 Screen Recognition, and 2022 App Intents—so an agent can reference what’s visible and act deterministically. [1][2][3]

Voice Control’s heritage (number overlays, element targeting) and Screen Recognition’s inferred labels imply Apple already maps pixels to selectors when developers fall short, which is the quiet superpower for third‑party apps. [1][2]

Historically analogous moves include Automator in 2005 creating action chains on the Mac and Shortcuts’ rise after the 2017 Workflow acquisition, which normalized user‑authored automations across iOS by 2018. [8][10]

The contrarian read: a “chatty” Siri matters less than a boringly reliable action layer; once taps become addresses, any competent model can orchestrate them, and Apple’s review‑enforced semantics keep that layer consistent. [3][9]

Back‑of‑envelope: the Gemini bill for “Siri that actually does stuff”

Assume Apple blends on‑device parsing with selective cloud calls, per Bloomberg’s 2024 reporting on Gemini talks. [4]

Working from publicly cited Gemini API prices: roughly $1.25 per 1M input tokens for 1.5 Pro and $0.075 per 1M for 1.5 Flash; output tokens often run 3–5× input cost, per industry summaries. These are proxies; Apple’s deal will differ. [5]

Scenario math (assumptions stated and shown):

• Users: 1,000,000 people/day invoking agentic Siri twice (2,000,000 invocations/day).
• Tokens per invocation: 3,000 input + 500 output (moderate, multi‑step task).
• Input tokens/day: 2,000,000 × 3,000 = 6,000,000,000 → 6,000 “million‑token” units → 6,000 × $1.25 ≈ $7,500/day (if Pro‑class input). [5]
• Output tokens/day: 2,000,000 × 500 = 1,000,000,000 → 1,000 units → if output costs 3× input rate, ≈ $3.75 per 1M → ~$3,750/day. [5]
• Total: ≈ $11,250/day per 1M daily users → ≈ $4.1M/year; scale linearly to 50M daily users and you reach ≈ $205M/year.

Even with Flash‑tier calls, prompt compression, or on‑device summarization, a popular feature risks nine‑figure OpEx, which makes reliability and scope control first‑order product decisions, not polish. [5]

Named‑stakeholder breakdown (what this means for them)

• Apple
  • The moat is the OS action layer: accessibility semantics plus App Intents shipped at WWDC22. Ship reliability and you minimize cloud fallbacks; miss, and token burn rises alongside latency. [3][5]
• Google Cloud
  • A Gemini deal would bring sustained “agent minutes” rather than spiky chatbot traffic; Apple will optimize prompts to cut token counts, squeezing margins unless value‑based pricing emerges. [4][5]
• Third‑party app developers
  • Accessibility labels, traits, and intents become growth levers; if Siri can’t find your “Add to cart” or “Post comment” intent, your competitor wins the invocation in Spotlight or Shortcuts. [3][9]
• Regulators in the U.S. and EU
  • A brokered Siri that can route to multiple assistants (as reported) defuses “default” concerns under regimes like the DMA while keeping Apple in control of entry points. Watch how third‑party models access intents. [4]
• Accessibility community
  • Immediate, concrete benefits accrue on devices from 2019 onward that run Voice Control; this cohort will surface edge cases (fatigue, dexterity, noisy rooms) that harden the on‑screen model. [1]

2×2: How Apple could roll out an agentic Siri

• Axis 1: Execution locus (On‑device vs. Cloud‑assist).
• Axis 2: Entry point (Accessibility‑first vs. Mainstream‑first).

Quadrants:

• On‑device × Accessibility‑first: Voice Control (iOS 13, 2019) and Screen Recognition (iOS 14, 2020) deliver fast, private, deterministic targeting. [1][2]
• Cloud‑assist × Accessibility‑first: When on‑device parsing fails, server‑side vision or ASR can backstop captioning and descriptions; Apple has shipped hybrid approaches in media apps.
• On‑device × Mainstream‑first: App Intents‑driven Shortcuts and Spotlight actions (WWDC22 onward) cover quick local tasks with typed or spoken triggers. [3]
• Cloud‑assist × Mainstream‑first: A “Siri agent” that reasons across apps with selective Gemini calls, as discussed in 2024 reporting, likely launches with usage caps and clear disclosure. [4][6]

The bet: start in the top‑left where Apple’s silicon and privacy story shine, then expand diagonally as reliability and unit economics improve. [1][2][5]

What others are missing

Coverage often fixates on a chat UI and model brand, but the plumbing matters more: Apple is turning accessibility metadata—labels, traits, and hints—plus App Intents domains into a de facto automation DSL that any compliant app inherits. [3][9]

Because Screen Recognition can infer structure when labels are missing, the system gains resilience across older apps, while review guidelines nudge new apps to expose entities and actions cleanly. That architecture removes the need for one‑off bot integrations and makes Siri’s competence scale with conformance. [2][9]

What to watch next

1. By June 8, 2026: Apple demos Siri completing a multi‑step task across at least two third‑party apps in one request during the WWDC keynote, and explicitly marks the feature “beta” on a slide or in a footnote.

2. By June 12, 2026: Apple posts WWDC sessions and docs expanding App Intents domains to cover at least one new commerce or social action category, verifiable in Developer Documentation change logs.

3. By December 31, 2026: Natural‑language Voice Control expands beyond English to at least one additional language/locale listed on Apple’s public support matrices.

My take

Apple picked the right hill. “Agentic Siri” won’t be won by the cleverest model voice—it will be won by the OS that turns any pixel into a reliable action, the way Automator did for Mac tasks in 2005 and Shortcuts did for iOS workflows after 2017. [8][10]

If Apple ships a ruthlessly reliable action layer grounded in 2019–2022 primitives and adds cloud assist only where needed, Gemini becomes an accelerant, not a crutch—and Siri starts feeling like iOS itself waking up. [1][2][3][4]

Sources

1. Apple Newsroom — “Apple introduces Voice Control in macOS Catalina and iOS 13” (June 3, 2019) — Establishes system‑wide Voice Control origins and scope across Apple platforms.

2. Apple Developer Documentation — “Screen Recognition” (iOS 14, 2020) — Details on‑device inference that identifies UI elements when accessibility labels are missing.

3. Apple Developer — “App Intents” (WWDC22 session and docs, June 2022) — Explains the framework linking app entities/actions to Siri, Shortcuts, and Spotlight.

4. Bloomberg — “Apple in Talks With Google to Bring Gemini AI to iPhone” by Mark Gurman (March 2024) — Reports discussions that frame potential cloud assist for Siri.

5. TechTarget — “Google Gemini pricing and models explained” (2024) — Provides indicative token pricing for Gemini 1.5 Pro and 1.5 Flash used in cost estimates.

6. MacRumors — “iOS 18 to Feature Revamped Siri With On‑Device AI” (2024) — Summarizes expected Siri redesign and greater on‑device processing.

7. Apple Newsroom — “Apple announces WWDC24 for June 10–14” (March 26, 2024) — Confirms Apple’s June WWDC cadence used for dating predictions.

8. Wikipedia — “Automator (software)” (first released with Mac OS X 10.4 Tiger in 2005) — Historical analogue for OS‑level automation on the Mac.

9. Apple Human Interface Guidelines — “Accessibility” (ongoing) — Documents labels, traits, and patterns that form the semantic substrate for automation.

10. The Verge — “Apple acquires Workflow, the iOS automation app” (March 2017) — Context for Shortcuts’ lineage and Apple’s automation strategy.

Check your smartphone now — these apps are dangerous and should be deleted.

You should read that sentence again and then open your phone. Check your apps. Check what permissions they've been allowed. The FBI has just issued a public warning about mobile applications — especially those developed and maintained overseas — that can quietly collect and leak personal data. Check your smartphone now — these apps are dangerous and should be deleted. This is not fearmongering; it's a practical reminder that our pocket computers hold the keys to our contacts, location, photos, messages, and sometimes banking tokens.

Why the FBI warning matters

Over the last few years, governments and security agencies have flagged concerns about certain foreign-developed apps that request broad device permissions, persistently collect data, or route information through infrastructure in countries with different national security laws. The FBI’s recent public service advisory highlights three recurring risks:

• Apps that ask for access to contacts, SMS, storage, and location can harvest data about people who never installed the app.
• Some apps persistently collect information even when they aren’t actively used.
• Apps that host or hide malware can exfiltrate data or enable surveillance.

The advisory doesn’t ban specific mainstream brands by name in every case, but it does nudge users to be extra cautious about apps that maintain infrastructure or data stores in foreign jurisdictions where local laws may compel that data be handed over to state authorities.

Transitioning from awareness to action is the point: if an app on your phone requests sweeping permissions and you don’t trust its origin, treat it as a red flag.

Which apps you should watch for

The FBI’s message is broad rather than a neat list of offenders. That’s intentional: the risk isn’t just one app, it’s a pattern in how some apps behave and where they store data. Still, coverage from security outlets and tech sites highlights common categories to scrutinize:

• Free VPNs and “lite” streaming or downloader apps that ask for device-wide access.
• Lesser-known social or utility apps that request contact lists, SMS, and storage access on install.
• Apps hosted outside official stores (sideloaded APKs on Android) or unofficial versions of popular services.
• Apps that solicit device admin rights, accessibility privileges, or persistent background access.

If an app is obscure, newly published, or from a developer you can’t verify — and it asks for broad permissions — it’s safer to delete it and find a well-reviewed, reputable alternative.

What to do right now

• Open your phone’s Settings and review app permissions. Revoke anything that looks unnecessary (camera, mic, contacts) for apps that shouldn’t need them.
• Uninstall apps you don’t recognize, don’t use, or that you installed outside Apple’s App Store or Google Play.
• Update your OS and apps to the latest versions so security patches are applied.
• Only download apps from official stores and check developer details and reviews.
• Change passwords for sensitive accounts and enable multi-factor authentication where possible.
• If you suspect an app has stolen data or behaved maliciously, reset the device and reach out to your bank or services you use — and file a report with the FBI’s IC3 or your local authorities if you’re in the U.S.

These steps reduce the attack surface and limit persistent data collection even if an app is trying to overreach.

How real is the risk?

A follow-up question is fair: how likely is your app to be an active surveillance tool versus just a privacy-invasive tracker? The answer is: both are possible. Some apps are simply greedy for advertising and analytics data. Others — whether through negligence or design — may process and store data in ways that expose it to foreign legal orders or hostile actors. Security researchers and agencies have repeatedly found malware-laden or trojanized apps on third-party stores and even within official marketplaces.

So while the worst-case scenarios are rarer, the cost of inaction is high: identity theft, account takeover, and privacy compromise. Treating your smartphone like a personal device that needs periodic audits is smart hygiene — not paranoia.

Navigating nuance: don’t throw the baby out with the bathwater

Not every app developed abroad is a threat. Big, reputable companies with clear transparency reports, independent audits, and local presence are different from small, opaque developers. Context matters:

• Look for transparency: where is data stored, how is it encrypted, and what do the privacy policies say?
• Prefer apps with independent security reviews or a track record of responsible disclosure.
• Remember that removing permissions or uninstalling apps may break functionality — weigh that against the information at stake.

In short: be skeptical, not reflexively fearful. Make decisions based on permissions, provenance, and behavior.

My take

Smartphone security is a habit, not a one-off action. The FBI’s advisory is a timely nudge reminding us that convenience often comes with trade-offs. A regular five-minute check of permissions, coupled with a quick uninstall sweep for unused apps, will dramatically improve your safety. We can enjoy modern apps while still insisting they earn our trust.

Final thought: think of your phone like your home — you wouldn’t give a stranger permanent access to your house keys or bathroom drawers. Treat app permissions the same way.

Sources

• FBI Public Service Advisory summarized by Forbes — "FBI Warns iPhone And Android Users—Do Not Install These Apps" (Forbes).
  https://www.forbes.com/sites/zakdoffman/2026/04/04/fbi-warns-iphone-and-android-users-do-not-install-these-apps/

• "FBI warns against using Chinese mobile apps due to privacy risks" (BleepingComputer).
  https://www.bleepingcomputer.com/news/security/fbi-warns-against-using-chinese-mobile-apps-over-to-data-security-risks/

• "Many of the most downloaded… are developed and maintained by foreign companies" (TechRadar coverage of the FBI advisory).
  https://www.techradar.com/pro/security/many-of-the-most-downloaded-and-top-grossing-apps-in-the-united-states-are-developed-and-maintained-by-foreign-companies-fbi-urges-users-not-to-download-chinese-mobile-apps-over-privacy-risks

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/