Sora's iOS debut mirrors ChatGPT's success, raising concerns.

Sora’s iOS debut is getting a lot of attention for one simple reason: it’s moving fast. And honestly, when I saw the early numbers floating around, my first thought wasn’t “wow, AI video is here.” It was: what does this mean for adoption, and what does it mean for misuse?

Below is what stood out to me from a few recent announcements and tool updates—plus the bigger picture behind them.

Sora on iOS: big downloads, familiar hype—and real concerns

Let’s start with the headline people keep repeating: 627,000 downloads on iOS in the first week—and the claim that it’s “coming close” to ChatGPT’s launch momentum. The stat itself matters, but what matters even more is what it implies (and what it doesn’t).

What the download number likely means (and what it doesn’t)

The figure you’ll see referenced comes from reporting on Sora’s early iOS traction in the U.S. via TechCrunch. In my experience, download counts are a useful “interest” signal, but they’re not the same thing as retention, active usage, or successful generation rates.

• Downloads ≠ daily creators. A lot of installs happen from curiosity, press coverage, or app-store featuring.
• Time window matters. “First week” is usually a burst period. What you want to know next is how many people stayed for week two and week four.
• Definition of “download.” Most publishers mean installs/starts, not completed generations. If someone installs and immediately hits a waitlist or limits, the download still counts.

Still—627,000 installs in a week is not nothing. It suggests that the “AI video” idea has crossed the curiosity threshold for a chunk of mainstream users. And that’s where the concern kicks in.

Why iOS access can change the deepfake risk

When AI video tools were mostly web-based or limited to power users, the barrier to experimenting was higher. With iOS, the barrier drops: it’s in a familiar app store, on a device people already use daily, with friction reduced.

Here’s the part I don’t love: if a tool makes it easier for people to generate realistic video content quickly, you don’t just get more creators—you also get more bad actors trying to test boundaries.

Now, to be fair, “more access” doesn’t automatically mean “more harmful output.” The real question is what safeguards exist inside the product: content filters, prompt handling, detection, rate limits, and how enforcement behaves when users push the system.

If you’re reading coverage like this, try to look for answers to these practical questions:

• Are there visible guardrails? For example, does it refuse certain requests clearly?
• What happens when prompts get creative? Do filters catch obfuscated requests, or only obvious ones?
• Are there usage limits? Limits don’t stop misuse, but they slow scale.
• Is there reporting/escalation? If users flag content, is there a real process behind it?

I can’t verify every safeguard from the outside just by reading headlines. But the core takeaway is still fair: easier access tends to widen the audience—and that naturally increases both legitimate experimentation and potential misuse.

Google Gemini extensions: “build whatever you want” is powerful—and messy

Next up is Google Gemini, where the big claim is that anyone can create extensions without needing approval.

I get why Google is doing this. If you’ve ever tried to build anything “official” in a platform ecosystem, you know the approval bottleneck can kill momentum. Letting people ship faster can lead to genuinely useful add-ons—and it can also create a lot of junk.

What I’d watch for if you’re building on this

• Permissions and data access. If extensions can access user data, storage, or external services, you want to understand what’s actually allowed.
• Quality control. “No approval” shifts the burden to runtime behavior and user feedback.
• Security posture. Extensions are code plus logic plus integrations. That’s a bigger surface area than a simple chat prompt.

In other words: the “build whatever you want” philosophy can be great for creativity. It can also make it easier for sketchy or low-quality extensions to spread. If you use Gemini extensions, I’d treat them like third-party apps: check what they request and don’t blindly install anything that looks vague.

Zendesk’s AI agent claim: 80% sounds great—until you ask “80% of what?”

The TechCrunch report highlights Zendesk’s AI agent, claiming it can solve around 80% of customer problems on its own, with co-pilot and voice tools for harder cases.

Here’s my honest take: this kind of number is only meaningful if we know the measurement details. Otherwise, it reads like marketing gloss.

The details you should look for (because they change the meaning)

• Sample size and timeframe. Was it measured on 1,000 tickets or 1 million? Over a week or a year?
• What “solve” means. Does it mean resolved without human touch? Or “answered” even if the customer still had to follow up?
• Production vs. test environment. Some demos look amazing because they only include the easiest cases.
• Escalation rules. When does it decide to hand off? Early handoffs can protect quality but reduce automation.

Still, even without all the fine print, the direction is clear: support teams want deflection and faster resolution. If Zendesk’s agent truly reduces human workload for the bulk of routine issues, that’s a meaningful operational win. The risk is that if “80%” is defined loosely, teams might over-trust it and accidentally worsen customer experience on edge cases.

Best new AI tools I’d actually try (and what they claim to do)

I’m not going to pretend I’ve used every one of these end-to-end, but I can tell you what the descriptions imply—and where I’d dig in first.

• JustCopy.ai
• What it’s supposed to do: clone popular apps and create tailored versions so you’re not starting from zero.
• What I’d check: what inputs you provide (screens? flows? prompts?), how much customization is actually supported, and whether you can export or hand off the result to your team. Also—pricing and limits matter here because “cloning” can get expensive fast if you iterate.
• Extruct
• What it’s supposed to do: find businesses based on real activity using AI to explore specific markets that standard databases miss.
• What I’d check: what counts as “real activities” (job postings? website updates? product launches?), what data sources it uses, and how reliable the targeting is compared to traditional lists. If you can’t explain the source signals, it’s hard to trust the output.
• Sluqe
• What it’s supposed to do: turn voice memos into searchable text, then auto-sort them into decisions, tasks, and important points.
• What I’d check: transcription accuracy (especially accents/background noise), how it detects “decisions” vs “tasks,” and whether you can edit tags after the fact. The best tools make it easy to correct errors quickly.
• Crossfade
• What it’s supposed to do: identify key timestamps in long videos, then let you clip and reuse content across sites.
• What I’d check: how it chooses “important times” (speech emphasis? viewer retention? keywords?), and whether it handles copyright-safe workflow guidance. Also, exporting formats and speed are big practical factors.
• The Drive AI
• What it’s supposed to do: manage files using simple language commands—make, arrange, and study documents.
• What I’d check: what platforms it connects to (Google Drive? local folders?), how it handles permissions, and whether it can summarize without losing critical context. “Study documents” can mean anything, so I’d look for concrete outputs like outlines, Q&A, or structured notes.
• Notabl
• What it’s supposed to do: summarize long YouTube videos into actionable summaries or simple plans.
• What I’d check: whether it captures steps and constraints (not just generic takeaways), and whether you can regenerate a summary focused on a goal (e.g., “build a content calendar” vs “explain the concept”).
• Lamatic
• What it’s supposed to do: transform AI creation into drag-and-drop tasks, with vector storage and controlled resources.
• What I’d check: how the vector storage is organized (projects? collections?), whether you can reuse memory across tasks, and what “controlled resources” actually limits (cost, speed, token usage). That’s often the difference between “cool demo” and “usable tool.”

Prompt of the day: a practical Sora/iOS policy-and-safety workflow

If you’re thinking about Sora (or any AI video tool) and you want a prompt that actually produces something usable, here’s one I’d use. It’s not fluff—it forces the model to output a test plan and measurable criteria.

You’re helping me evaluate an AI video generation app on iOS (similar to Sora). I need a safety and misuse risk assessment that I can run in a week. Output 1) a short threat model (who misuses it, what they try to do, and likely attack paths), 2) a test matrix with at least 25 prompts grouped by risk level (low/medium/high), 3) for each prompt: expected safe behavior, what the model should refuse or redirect to, and what would count as a failure, 4) a measurement section with concrete metrics (refusal rate, partial compliance rate, time-to-response, and escalation triggers), 5) a mitigation plan (rate limits, watermarking/detection, content reporting workflow, and user guidance), and 6) an example policy snippet I can paste into an internal moderation guideline. Important: include assumptions, and list what evidence I should collect from the app logs or user reports.

Why this prompt? Because it turns “AI is risky” into something you can actually test, document, and improve. And if you’re going to talk about deepfakes and access, you need more than vibes—you need a checklist.