Apple Intelligence

RSS for tag

Apple Intelligence is the personal intelligence system that puts powerful generative models right at the core of your iPhone, iPad, and Mac and powers incredible new features to help users communicate, work, and express themselves.

Posts under Apple Intelligence tag

200 Posts

Post

Replies

Boosts

Views

Activity

Siri AI’s onscreen awareness can’t understand an AppEntity without a schema?
Use Case I’m currently developing , a hiking and cycling app. I’d like to use Siri AI in iOS/watchOS 27 to create an experience like this: While users are recording an activity in app, they can raise their wrist or invoke Siri on iPhone and simply ask: “How much farther to the destination?” “How far have I already gone?” “How much elevation gain is left?” “How far is it to the next waypoint?” … Siri can then answer based on the app’s current workout context. Since there are many metrics like these, and it’s not convenient to look at the screen while cycling or trail running, this could be a really valuable use case if Siri AI can support it. I defined an AppEntity like this, and then associated it with the UI. But I found that Siri AI doesn’t seem to understand this AppEntity. It can only understand the content it can see on the screen, even though I can see that it did execute ToobooWorkoutSessionQuery, the EntityQuery. This screen has multiple tabs. Siri understood the on-screen values such as “Distance: 0.21 mi” and “Remaining Distance: 0.14 mi”, but it didn’t know the data from the other tabs on the same page, such as heart rate, average speed, and so on. So it seems that Siri is directly reading the screen, instead of retrieving the information from the AppEntity I actually provided. Is this because the AppEntity doesn’t use one of the schemas defined by AppSchemaEntity, so Siri AI can’t understand it? App Intents without a schema seem to have a similar issue. If the AppIntent I define is not within one of those schemas, Siri won’t directly execute it either. My current solution: I defined many Intents and Shortcuts. Siri AI’s ability to parse shortcuts seems to be much smarter in the new system, and it can match them quite easily. Also, shortcuts don’t require the app to be in the foreground. However, when talking to Siri, the shortcut phrase has to include the app name, which feels a bit unnatural. For example: “How far have I traveled in xxx app?”
0
1
555
Jul ’26
Can any Apple Watch running WatchOS 27 access PCC via Foundation Models?
Apologies, if I've missed the answer already here, I've searched around but can't find it. Foundation models and Private Cloud Compute require Apple Intelligence to be enabled in Settings as mentioned here. At the same time it says that Foundation Models PCC calls are supported on all Apple Watch models that run WatchOS 27. So, will there be a seperate Apple Intelligence setting in WatchOS 27 for those devices? Otherwise if a user has an Apple Watch Series 11 (which does support Apple Intelligence) paired with an iPhone 15 (which doesn't support Apple Intelligence), will they be unable to use the Foundation Models PCC calls from WatchOS in my app? Despite the fact the iPhone isn't involved in these queries anyway?
1
1
804
Jul ’26
Visual Intelligence: controlling the "More results" button and the app result tab (ordering / opt-out)?
I've integrated my app with Visual Intelligence (iOS 26) using the semanticContentSearch schema. Image results are populated via an IntentValueQuery returning my entities, and the "More results" button is backed by an intent declared as: @available(iOS 26.0, *) @AppIntent(schema: .visualIntelligence.semanticContentSearch) struct ShowSearchResultsIntent { static let title: LocalizedStringResource = "Search products by image" static let openAppWhenRun: Bool = true var semanticContent: SemanticContentDescriptor func perform() async throws -> some IntentResult { /* deep-link into in-app search */ } } From WWDC25 (session 275) and WWDC26 (session 297) my understanding is that: the "More results" button is provided automatically by the system once this schema intent is adopted; returning an empty array from the value query lets the system show an empty response; my app appears as a result tab alongside other adopting apps, and the system decides the ordering based on the available image search providers on the device. I have a few questions about how much of this an app can control at runtime: "More results" button Is there any supported way to conditionally show or hide the system "More results" button at runtime (e.g., region, A/B test, server-driven feature flag)? Or is it strictly tied to the static presence of the semanticContentSearch intent? If IntentValueQuery returns an empty array, does the "More results" button still appear? Is there any API to suppress the button while keeping the schema intent declared? App result tab ordering How exactly does the system decide the order of the app result tabs? Is it based on relevance/similarity, app category, user behavior, or something else? Is there anything a developer can do to influence where their tab appears, or is ordering entirely system-controlled? App result tab presence / opt-out Once the integration is implemented, my app's tab appears automatically. Is there a supported way to conditionally opt out of appearing as a result tab at runtime (e.g., based on region or a feature flag)? Or is the only way to not appear to omit the integration at build time (or gate it by OS availability)? Thanks!
0
0
442
Jun ’26
Siri AI shows raw TypedValueToContentGraphResolutionErrorDomain error 4 to user
I found a UI/error-handling issue involving Siri AI where a raw/internal-looking error code is shown directly to the user instead of a user-friendly message. Environment: Device: iPad Pro 11-inch (M4) iOS/iPadOS version: 27.0 Siri / Apple Intelligence enabled: Yes App involved: Files & PDF Expert UI/context: Siri AI interaction with a document from Files File type: .doc Observed behavior: I asked Siri AI to create a new note inside a document through the app integration. Instead of completing the request or showing a user-friendly failure message, iOS displayed this raw error notification: “From PDF Expert: The operation couldn’t be completed. (TypedValueToContentGraphResolutionErrorDomain error 4.)” Expected behavior: Siri AI should handle this failure gracefully and explain that it could not create a new note in the document, instead of exposing the raw error domain and error code to the user. Screenshot:
0
0
466
Jun ’26
Wait Time for Siri AI waitlist
There seems to be a lack of clarity about how this Siri AI rollout is working. Does the indexing have anything to do with getting taken off the waitlist, or are they completely separate? Also, what is the expected wait time and has anyone gotten the new Siri after the initial wave of approvals (after 4 hours after the keynote)? The waitlist is extremely slow compared to the initial Apple Intelligence waitlist from a couple of years ago.
35
14
23k
Jun ’26
iPadOS 27 beta: Missing Apple Intelligence waitlist (UPDATED)
I finally installed iPadOS 27 developer beta 1 on my iPad Air (M2), opened Settings app and went to the Siri section. There’s no option to join a waitlist. I had Apple Intelligence enabled on iPadOS 26, but in 27, the “Apple Intelligence & Siri” section simply reads “Siri” now. No mention of Apple Intelligence at all! Has anyone else encountered this? Is it a regional thing? I’m in Canada. EDIT: Ok it was a region thing. I changed my region to US and the waitlist option appeared.
1
0
1.6k
Jun ’26
New Siri
Hello Apple community I would like to know why new Siri is currently inactive on my phone. I have a iPhone 17 base model and downloaded iOS 27 beta. I suspect that it is not functioning due to me being 13 and having parental controls on. That is my guess why New Siri is not downloading. The phone states that I have joined the waitlist though my stance on the situation is that there is more to this!
1
0
338
Jun ’26
Apple Mail compose field becomes uneditable after using Apple Intelligence rewriting tools on macOS 27 Developer Beta 1
Apple Mail compose field becomes uneditable after using Apple Intelligence rewriting tools on macOS 27 Developer Beta 1 I am seeing a reproducible issue in Apple Mail on macOS 27 Developer Beta 1 where the compose body becomes locked/uneditable after using Apple Intelligence writing tools. Environment Mac: macOS: macOS 27.0 Developer Beta 1 Build: 26A5353q Device: MacBook Pro with Apple Silicon shouldSwitchToCampoMode: false (isEnhancedSiriAvailable=false) App: Apple Mail Compose window Apple Intelligence Writing Tools Summary When composing an email in Apple Mail, if I write some text and then use Apple Intelligence to rewrite it — for example using Friendly, Professional, or Concise — Mail replaces the original text with the rewritten version. After the rewritten text is inserted, the message body becomes unresponsive. I cannot continue typing, edit the rewritten text, delete text, select text normally, or add new content inside the email body. The Apple Intelligence button also becomes unresponsive after this happens. The only actions that still seem to work are sending the email, discarding the draft, or using some toolbar actions such as emoji insertion. Steps to Reproduce Open Apple Mail on macOS 27 Developer Beta 1. Create a new email. Type any text into the email body. Use Apple Intelligence Writing Tools. Choose a rewrite option such as: Friendly Professional Concise Let Apple Intelligence replace/update the email body text. Try to click back into the message body and continue typing or editing. Expected Result After Apple Intelligence rewrites the email body, the compose field should remain fully editable. The user should be able to: Continue typing after the rewritten text Edit or delete the rewritten text Select and modify text Use Apple Intelligence again on the updated content Continue composing the email normally Actual Result After Apple Intelligence inserts the rewritten text: The email body becomes uneditable. Typing no longer works inside the message body. Clicking inside the body does not restore normal editing. Existing text cannot be edited or changed. Apple Intelligence controls become unresponsive. The compose window itself does not fully crash, but the body editor appears stuck. Send and discard still appear to work. Reproducibility This appears to be reproducible after using Apple Intelligence rewriting tools inside Apple Mail’s compose window. It was working before, so this appears to be a regression in macOS 27 Developer Beta 1.
0
0
255
Jun ’26
.messages.message reaction field type vs. error from macro
The documented template for @AppEntity(schema: .messages.message) at Integrating your messaging app with Apple Intelligence and on the MessagesEntity.message reference page shows: var reaction: <#ReadReaction#>? with <#ReadReaction#> rendered as a placeholder (the Xcode placeholder syntax). A natural reading is "fill in your own type that you want to use here". I tried several: Tapback? where Tapback is @AppEnum(schema: .messages.customReaction) MessageReaction? (same, renamed) MessageReaction? with manual AppEnum conformance (no schema decoration) AttributedString? AttributedString (non-optional) field omitted entirely Each variant produced one of: error: Property 'reaction' type does not match required AppSchemaEntity property type 'ReadReactionCases:(Schema<Tapback> | AttributedString)' error: Required AppSchemaEntity property 'reaction' must be optional error: Missing required property 'reaction' from AppSchemaEntity 'messages.message' The phrase ReadReactionCases:(Schema<Tapback> | AttributedString) is opaque — ReadReactionCases isn't a public type, Schema<Tapback> isn't constructable from outside, and the documentation doesn't mention @UnionValue in this context. The actual working pattern, which I only found by downloading the UnicornChat sample and reading MessageEntity.swift, is: @UnionValue enum MessageReaction: Sendable { case customReaction(CustomReaction) } @AppEnum(schema: .messages.customReaction) enum CustomReaction: String, AppEnum { case sticker static let caseDisplayRepresentations: [Self: DisplayRepresentation] = [ .sticker: "Sticker" ] } Two suggestions: Update the schema-template comment in the docs to either name MessageReaction explicitly with a @UnionValue annotation, or include a one-line note: "The reaction field is a @UnionValue enum wrapping the customReaction schema enum — see UnicornChat sample." The current placeholder <#ReadReaction#> plus the prose suggesting "you can generate the properties... with the @AppEntity(.messages.message) Swift macro" reads as if the developer just supplies any AppEnum-conformer. Improve the diagnostic. Property type does not match required AppSchemaEntity property type 'ReadReactionCases:(Schema<Tapback> | AttributedString)' is unhelpful because ReadReactionCases doesn't appear in any reachable type. Either rename to something developer-facing, or include a fix-it that suggests @UnionValue. iOS 27.0 beta, Xcode 27 beta, macOS Tahoe 26.4.
3
0
653
Jun ’26
Conforming existing App Intents / Entity to Schema
Our app already has a huge set of App Intents and Entities. Conceptually, our entities and intents matches well to the existing schemas (like the Notes schema). But because we have existing intents, we ran into two problems: Our existing intents/entities used different property names in the past and some properties are slightly different then the schema. Our existing intents are already used on older Versions of macOS / iOS. But the schema domain is only available on OS27 and later. What can we do to adopt the schema? Should we just duplicate all Intents / Entities and mark them as isAssistantOnly and limit their availability to OS27 and later?
0
1
302
Jun ’26
Generating Images of Real People Without Their Consent
I am concerned how easy they make it to generate photos of real people. And because it is so easy, people will likely just try it on people without their consent. At the WWDC26 keynote, they demonstrated how you can use any photo of a person to create a new photorealistic image based on modifications described using natural language. I would even describe this as creepy. Anyone who can find a photo of me online, can create a photo of me doing whatever they want! And of course, I have no control over who they share that with. I believe Apple could do better than the other AI companies. At minimum, they could display some warnings about the ethical considerations when using this feature.
1
0
199
Jun ’26
Xcode Codex login fails on Safari 27 (Beta 3)
When trying to log into the Codex Plugin from Xcode, on the auth.openai.com site I can not progress. No option will progress from that page. Not: Continue with eMail Continue with Microsoft Continue with Apple Continue with Google Continue with phone number Is this a Safari (27.0, 22625.1.22.11.4) issue, or an OpenAI issue?
Replies
0
Boosts
0
Views
597
Activity
Jul ’26
Siri AI’s onscreen awareness can’t understand an AppEntity without a schema?
Use Case I’m currently developing , a hiking and cycling app. I’d like to use Siri AI in iOS/watchOS 27 to create an experience like this: While users are recording an activity in app, they can raise their wrist or invoke Siri on iPhone and simply ask: “How much farther to the destination?” “How far have I already gone?” “How much elevation gain is left?” “How far is it to the next waypoint?” … Siri can then answer based on the app’s current workout context. Since there are many metrics like these, and it’s not convenient to look at the screen while cycling or trail running, this could be a really valuable use case if Siri AI can support it. I defined an AppEntity like this, and then associated it with the UI. But I found that Siri AI doesn’t seem to understand this AppEntity. It can only understand the content it can see on the screen, even though I can see that it did execute ToobooWorkoutSessionQuery, the EntityQuery. This screen has multiple tabs. Siri understood the on-screen values such as “Distance: 0.21 mi” and “Remaining Distance: 0.14 mi”, but it didn’t know the data from the other tabs on the same page, such as heart rate, average speed, and so on. So it seems that Siri is directly reading the screen, instead of retrieving the information from the AppEntity I actually provided. Is this because the AppEntity doesn’t use one of the schemas defined by AppSchemaEntity, so Siri AI can’t understand it? App Intents without a schema seem to have a similar issue. If the AppIntent I define is not within one of those schemas, Siri won’t directly execute it either. My current solution: I defined many Intents and Shortcuts. Siri AI’s ability to parse shortcuts seems to be much smarter in the new system, and it can match them quite easily. Also, shortcuts don’t require the app to be in the foreground. However, when talking to Siri, the shortcut phrase has to include the app name, which feels a bit unnatural. For example: “How far have I traveled in xxx app?”
Replies
0
Boosts
1
Views
555
Activity
Jul ’26
Can any Apple Watch running WatchOS 27 access PCC via Foundation Models?
Apologies, if I've missed the answer already here, I've searched around but can't find it. Foundation models and Private Cloud Compute require Apple Intelligence to be enabled in Settings as mentioned here. At the same time it says that Foundation Models PCC calls are supported on all Apple Watch models that run WatchOS 27. So, will there be a seperate Apple Intelligence setting in WatchOS 27 for those devices? Otherwise if a user has an Apple Watch Series 11 (which does support Apple Intelligence) paired with an iPhone 15 (which doesn't support Apple Intelligence), will they be unable to use the Foundation Models PCC calls from WatchOS in my app? Despite the fact the iPhone isn't involved in these queries anyway?
Replies
1
Boosts
1
Views
804
Activity
Jul ’26
Visual Intelligence: controlling the "More results" button and the app result tab (ordering / opt-out)?
I've integrated my app with Visual Intelligence (iOS 26) using the semanticContentSearch schema. Image results are populated via an IntentValueQuery returning my entities, and the "More results" button is backed by an intent declared as: @available(iOS 26.0, *) @AppIntent(schema: .visualIntelligence.semanticContentSearch) struct ShowSearchResultsIntent { static let title: LocalizedStringResource = "Search products by image" static let openAppWhenRun: Bool = true var semanticContent: SemanticContentDescriptor func perform() async throws -> some IntentResult { /* deep-link into in-app search */ } } From WWDC25 (session 275) and WWDC26 (session 297) my understanding is that: the "More results" button is provided automatically by the system once this schema intent is adopted; returning an empty array from the value query lets the system show an empty response; my app appears as a result tab alongside other adopting apps, and the system decides the ordering based on the available image search providers on the device. I have a few questions about how much of this an app can control at runtime: "More results" button Is there any supported way to conditionally show or hide the system "More results" button at runtime (e.g., region, A/B test, server-driven feature flag)? Or is it strictly tied to the static presence of the semanticContentSearch intent? If IntentValueQuery returns an empty array, does the "More results" button still appear? Is there any API to suppress the button while keeping the schema intent declared? App result tab ordering How exactly does the system decide the order of the app result tabs? Is it based on relevance/similarity, app category, user behavior, or something else? Is there anything a developer can do to influence where their tab appears, or is ordering entirely system-controlled? App result tab presence / opt-out Once the integration is implemented, my app's tab appears automatically. Is there a supported way to conditionally opt out of appearing as a result tab at runtime (e.g., based on region or a feature flag)? Or is the only way to not appear to omit the integration at build time (or gate it by OS availability)? Thanks!
Replies
0
Boosts
0
Views
442
Activity
Jun ’26
Siri AI shows raw TypedValueToContentGraphResolutionErrorDomain error 4 to user
I found a UI/error-handling issue involving Siri AI where a raw/internal-looking error code is shown directly to the user instead of a user-friendly message. Environment: Device: iPad Pro 11-inch (M4) iOS/iPadOS version: 27.0 Siri / Apple Intelligence enabled: Yes App involved: Files & PDF Expert UI/context: Siri AI interaction with a document from Files File type: .doc Observed behavior: I asked Siri AI to create a new note inside a document through the app integration. Instead of completing the request or showing a user-friendly failure message, iOS displayed this raw error notification: “From PDF Expert: The operation couldn’t be completed. (TypedValueToContentGraphResolutionErrorDomain error 4.)” Expected behavior: Siri AI should handle this failure gracefully and explain that it could not create a new note in the document, instead of exposing the raw error domain and error code to the user. Screenshot:
Replies
0
Boosts
0
Views
466
Activity
Jun ’26
Wait Time for Siri AI waitlist
There seems to be a lack of clarity about how this Siri AI rollout is working. Does the indexing have anything to do with getting taken off the waitlist, or are they completely separate? Also, what is the expected wait time and has anyone gotten the new Siri after the initial wave of approvals (after 4 hours after the keynote)? The waitlist is extremely slow compared to the initial Apple Intelligence waitlist from a couple of years ago.
Replies
35
Boosts
14
Views
23k
Activity
Jun ’26
iPadOS 27 beta: Missing Apple Intelligence waitlist (UPDATED)
I finally installed iPadOS 27 developer beta 1 on my iPad Air (M2), opened Settings app and went to the Siri section. There’s no option to join a waitlist. I had Apple Intelligence enabled on iPadOS 26, but in 27, the “Apple Intelligence & Siri” section simply reads “Siri” now. No mention of Apple Intelligence at all! Has anyone else encountered this? Is it a regional thing? I’m in Canada. EDIT: Ok it was a region thing. I changed my region to US and the waitlist option appeared.
Replies
1
Boosts
0
Views
1.6k
Activity
Jun ’26
New Siri
Hello Apple community I would like to know why new Siri is currently inactive on my phone. I have a iPhone 17 base model and downloaded iOS 27 beta. I suspect that it is not functioning due to me being 13 and having parental controls on. That is my guess why New Siri is not downloading. The phone states that I have joined the waitlist though my stance on the situation is that there is more to this!
Replies
1
Boosts
0
Views
338
Activity
Jun ’26
Apple Mail compose field becomes uneditable after using Apple Intelligence rewriting tools on macOS 27 Developer Beta 1
Apple Mail compose field becomes uneditable after using Apple Intelligence rewriting tools on macOS 27 Developer Beta 1 I am seeing a reproducible issue in Apple Mail on macOS 27 Developer Beta 1 where the compose body becomes locked/uneditable after using Apple Intelligence writing tools. Environment Mac: macOS: macOS 27.0 Developer Beta 1 Build: 26A5353q Device: MacBook Pro with Apple Silicon shouldSwitchToCampoMode: false (isEnhancedSiriAvailable=false) App: Apple Mail Compose window Apple Intelligence Writing Tools Summary When composing an email in Apple Mail, if I write some text and then use Apple Intelligence to rewrite it — for example using Friendly, Professional, or Concise — Mail replaces the original text with the rewritten version. After the rewritten text is inserted, the message body becomes unresponsive. I cannot continue typing, edit the rewritten text, delete text, select text normally, or add new content inside the email body. The Apple Intelligence button also becomes unresponsive after this happens. The only actions that still seem to work are sending the email, discarding the draft, or using some toolbar actions such as emoji insertion. Steps to Reproduce Open Apple Mail on macOS 27 Developer Beta 1. Create a new email. Type any text into the email body. Use Apple Intelligence Writing Tools. Choose a rewrite option such as: Friendly Professional Concise Let Apple Intelligence replace/update the email body text. Try to click back into the message body and continue typing or editing. Expected Result After Apple Intelligence rewrites the email body, the compose field should remain fully editable. The user should be able to: Continue typing after the rewritten text Edit or delete the rewritten text Select and modify text Use Apple Intelligence again on the updated content Continue composing the email normally Actual Result After Apple Intelligence inserts the rewritten text: The email body becomes uneditable. Typing no longer works inside the message body. Clicking inside the body does not restore normal editing. Existing text cannot be edited or changed. Apple Intelligence controls become unresponsive. The compose window itself does not fully crash, but the body editor appears stuck. Send and discard still appear to work. Reproducibility This appears to be reproducible after using Apple Intelligence rewriting tools inside Apple Mail’s compose window. It was working before, so this appears to be a regression in macOS 27 Developer Beta 1.
Replies
0
Boosts
0
Views
255
Activity
Jun ’26
.messages.message reaction field type vs. error from macro
The documented template for @AppEntity(schema: .messages.message) at Integrating your messaging app with Apple Intelligence and on the MessagesEntity.message reference page shows: var reaction: <#ReadReaction#>? with <#ReadReaction#> rendered as a placeholder (the Xcode placeholder syntax). A natural reading is "fill in your own type that you want to use here". I tried several: Tapback? where Tapback is @AppEnum(schema: .messages.customReaction) MessageReaction? (same, renamed) MessageReaction? with manual AppEnum conformance (no schema decoration) AttributedString? AttributedString (non-optional) field omitted entirely Each variant produced one of: error: Property 'reaction' type does not match required AppSchemaEntity property type 'ReadReactionCases:(Schema<Tapback> | AttributedString)' error: Required AppSchemaEntity property 'reaction' must be optional error: Missing required property 'reaction' from AppSchemaEntity 'messages.message' The phrase ReadReactionCases:(Schema<Tapback> | AttributedString) is opaque — ReadReactionCases isn't a public type, Schema<Tapback> isn't constructable from outside, and the documentation doesn't mention @UnionValue in this context. The actual working pattern, which I only found by downloading the UnicornChat sample and reading MessageEntity.swift, is: @UnionValue enum MessageReaction: Sendable { case customReaction(CustomReaction) } @AppEnum(schema: .messages.customReaction) enum CustomReaction: String, AppEnum { case sticker static let caseDisplayRepresentations: [Self: DisplayRepresentation] = [ .sticker: "Sticker" ] } Two suggestions: Update the schema-template comment in the docs to either name MessageReaction explicitly with a @UnionValue annotation, or include a one-line note: "The reaction field is a @UnionValue enum wrapping the customReaction schema enum — see UnicornChat sample." The current placeholder <#ReadReaction#> plus the prose suggesting "you can generate the properties... with the @AppEntity(.messages.message) Swift macro" reads as if the developer just supplies any AppEnum-conformer. Improve the diagnostic. Property type does not match required AppSchemaEntity property type 'ReadReactionCases:(Schema<Tapback> | AttributedString)' is unhelpful because ReadReactionCases doesn't appear in any reachable type. Either rename to something developer-facing, or include a fix-it that suggests @UnionValue. iOS 27.0 beta, Xcode 27 beta, macOS Tahoe 26.4.
Replies
3
Boosts
0
Views
653
Activity
Jun ’26
Conforming existing App Intents / Entity to Schema
Our app already has a huge set of App Intents and Entities. Conceptually, our entities and intents matches well to the existing schemas (like the Notes schema). But because we have existing intents, we ran into two problems: Our existing intents/entities used different property names in the past and some properties are slightly different then the schema. Our existing intents are already used on older Versions of macOS / iOS. But the schema domain is only available on OS27 and later. What can we do to adopt the schema? Should we just duplicate all Intents / Entities and mark them as isAssistantOnly and limit their availability to OS27 and later?
Replies
0
Boosts
1
Views
302
Activity
Jun ’26
Generating Images of Real People Without Their Consent
I am concerned how easy they make it to generate photos of real people. And because it is so easy, people will likely just try it on people without their consent. At the WWDC26 keynote, they demonstrated how you can use any photo of a person to create a new photorealistic image based on modifications described using natural language. I would even describe this as creepy. Anyone who can find a photo of me online, can create a photo of me doing whatever they want! And of course, I have no control over who they share that with. I believe Apple could do better than the other AI companies. At minimum, they could display some warnings about the ethical considerations when using this feature.
Replies
1
Boosts
0
Views
199
Activity
Jun ’26