#app-intents — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #app-intents, aggregated by home.social.
-
Found something good in Safari? Send it to Bulletin in a couple of taps, thanks to the new App Intents (Shortcuts) in 3.0.
Open it in the reader, or go straight to a Smart Summary. And if now isn't the time, save it to Read Later.
It all runs on App Intents, so you can build your own version in Shortcuts.
-
Found something good in Safari? Send it to Bulletin in a couple of taps, thanks to the new App Intents (Shortcuts) in 3.0.
Open it in the reader, or go straight to a Smart Summary. And if now isn't the time, save it to Read Later.
It all runs on App Intents, so you can build your own version in Shortcuts.
-
Found something good in Safari? Send it to Bulletin in a couple of taps, thanks to the new App Intents (Shortcuts) in 3.0.
Open it in the reader, or go straight to a Smart Summary. And if now isn't the time, save it to Read Later.
It all runs on App Intents, so you can build your own version in Shortcuts.
-
Found something good in Safari? Send it to Bulletin in a couple of taps, thanks to the new App Intents (Shortcuts) in 3.0.
Open it in the reader, or go straight to a Smart Summary. And if now isn't the time, save it to Read Later.
It all runs on App Intents, so you can build your own version in Shortcuts.
-
I mostly like the new audio AppEntity schemas in iOS 27, but there are a lot of weird quirks when it comes to implementing Shortcuts actions.
My conspiracy theory is that, because of the AI Shortcuts builder, Apple didn’t bother considering the end user’s experience building shortcuts for apps that adopt the new App Intents features.
Or maybe I just don’t know what the heck I’m doing, which I really hope is the case.
-
I mostly like the new audio AppEntity schemas in iOS 27, but there are a lot of weird quirks when it comes to implementing Shortcuts actions.
My conspiracy theory is that, because of the AI Shortcuts builder, Apple didn’t bother considering the end user’s experience building shortcuts for apps that adopt the new App Intents features.
Or maybe I just don’t know what the heck I’m doing, which I really hope is the case.
-
I mostly like the new audio AppEntity schemas in iOS 27, but there are a lot of weird quirks when it comes to implementing Shortcuts actions.
My conspiracy theory is that, because of the AI Shortcuts builder, Apple didn’t bother considering the end user’s experience building shortcuts for apps that adopt the new App Intents features.
Or maybe I just don’t know what the heck I’m doing, which I really hope is the case.
-
I mostly like the new audio AppEntity schemas in iOS 27, but there are a lot of weird quirks when it comes to implementing Shortcuts actions.
My conspiracy theory is that, because of the AI Shortcuts builder, Apple didn’t bother considering the end user’s experience building shortcuts for apps that adopt the new App Intents features.
Or maybe I just don’t know what the heck I’m doing, which I really hope is the case.
-
Fighting all day to get @zenitizer to play nicely with #SiriAI. All this worked so well with "Old Siri" via #Shortcuts / #AppIntents but this is a lot trickier 😞
At least querying, playing and stopping meditations through media playback schema works now (the most important bit) 😅
-
Fighting all day to get @zenitizer to play nicely with #SiriAI. All this worked so well with "Old Siri" via #Shortcuts / #AppIntents but this is a lot trickier 😞
At least querying, playing and stopping meditations through media playback schema works now (the most important bit) 😅
-
Fighting all day to get @zenitizer to play nicely with #SiriAI. All this worked so well with "Old Siri" via #Shortcuts / #AppIntents but this is a lot trickier 😞
At least querying, playing and stopping meditations through media playback schema works now (the most important bit) 😅
-
Fighting all day to get @zenitizer to play nicely with #SiriAI. All this worked so well with "Old Siri" via #Shortcuts / #AppIntents but this is a lot trickier 😞
At least querying, playing and stopping meditations through media playback schema works now (the most important bit) 😅
-
After throwing away most of my App Intents code and starting fresh using the new audio schemas, I’m the closest I’ve ever got to getting Siri to work in Groove.
It all seems good in the logs but playback isn’t actually starting for some reason. 😭
-
After throwing away most of my App Intents code and starting fresh using the new audio schemas, I’m the closest I’ve ever got to getting Siri to work in Groove.
It all seems good in the logs but playback isn’t actually starting for some reason. 😭
-
After throwing away most of my App Intents code and starting fresh using the new audio schemas, I’m the closest I’ve ever got to getting Siri to work in Groove.
It all seems good in the logs but playback isn’t actually starting for some reason. 😭
-
After throwing away most of my App Intents code and starting fresh using the new audio schemas, I’m the closest I’ve ever got to getting Siri to work in Groove.
It all seems good in the logs but playback isn’t actually starting for some reason. 😭
-
So, my oldest app has a #maccatalyst version for #macOS, I've spent time this last week creating a macOS native version. It used to be that the #macOS, #tvOS, and #iOS versions were all bundled into one price. I am wondering, now that I have a much more native Mac. version, should I sell that as a separate version? It's a very inexpensive app, but I do update it ever year, and this year I am spending a lot of time rewriting for #AppIntents - #IndieDev
-
So, my oldest app has a #maccatalyst version for #macOS, I've spent time this last week creating a macOS native version. It used to be that the #macOS, #tvOS, and #iOS versions were all bundled into one price. I am wondering, now that I have a much more native Mac. version, should I sell that as a separate version? It's a very inexpensive app, but I do update it ever year, and this year I am spending a lot of time rewriting for #AppIntents - #IndieDev
-
So, my oldest app has a #maccatalyst version for #macOS, I've spent time this last week creating a macOS native version. It used to be that the #macOS, #tvOS, and #iOS versions were all bundled into one price. I am wondering, now that I have a much more native Mac. version, should I sell that as a separate version? It's a very inexpensive app, but I do update it ever year, and this year I am spending a lot of time rewriting for #AppIntents - #IndieDev
-
So, my oldest app has a #maccatalyst version for #macOS, I've spent time this last week creating a macOS native version. It used to be that the #macOS, #tvOS, and #iOS versions were all bundled into one price. I am wondering, now that I have a much more native Mac. version, should I sell that as a separate version? It's a very inexpensive app, but I do update it ever year, and this year I am spending a lot of time rewriting for #AppIntents - #IndieDev
-
#SiriAI is the real deal. Sure its still got some rough edges, but beta 2 sets a great baseline. I particularly love the “sources” buttons in the Siri.app thread transcripts, which contain URLs directly into source app data. #AppIntents ftw
I do wonder where the intersection of this and #SwiftData will be. Developers are already declaring their models, so lets DRY, please? What will the best practices be?
-
#SiriAI is the real deal. Sure its still got some rough edges, but beta 2 sets a great baseline. I particularly love the “sources” buttons in the Siri.app thread transcripts, which contain URLs directly into source app data. #AppIntents ftw
I do wonder where the intersection of this and #SwiftData will be. Developers are already declaring their models, so lets DRY, please? What will the best practices be?
-
#SiriAI is the real deal. Sure its still got some rough edges, but beta 2 sets a great baseline. I particularly love the “sources” buttons in the Siri.app thread transcripts, which contain URLs directly into source app data. #AppIntents ftw
I do wonder where the intersection of this and #SwiftData will be. Developers are already declaring their models, so lets DRY, please? What will the best practices be?
-
When conforming to DeleteIntent, is there a way to show the plural form of the entity ("Books" vs "Book") in the Shortcuts app?
DeleteIntent requires an AppEntity array, but it ignores the parameter title and instead uses the entity typeDisplayRepresentation (which is singular).
I filed this feedback @mgorbach: FB23451186
-
When conforming to DeleteIntent, is there a way to show the plural form of the entity ("Books" vs "Book") in the Shortcuts app?
DeleteIntent requires an AppEntity array, but it ignores the parameter title and instead uses the entity typeDisplayRepresentation (which is singular).
I filed this feedback @mgorbach: FB23451186
-
When conforming to DeleteIntent, is there a way to show the plural form of the entity ("Books" vs "Book") in the Shortcuts app?
DeleteIntent requires an AppEntity array, but it ignores the parameter title and instead uses the entity typeDisplayRepresentation (which is singular).
I filed this feedback @mgorbach: FB23451186
-
When conforming to DeleteIntent, is there a way to show the plural form of the entity ("Books" vs "Book") in the Shortcuts app?
DeleteIntent requires an AppEntity array, but it ignores the parameter title and instead uses the entity typeDisplayRepresentation (which is singular).
I filed this feedback @mgorbach: FB23451186
-
Is duplicating our current types the way to go to support anyAppleOS 27 app schema domains for our app intents and app entities?
-
Is duplicating our current types the way to go to support anyAppleOS 27 app schema domains for our app intents and app entities?
-
Is duplicating our current types the way to go to support anyAppleOS 27 app schema domains for our app intents and app entities?
-
Is duplicating our current types the way to go to support anyAppleOS 27 app schema domains for our app intents and app entities?
-
The CSSearchableItem(appEntity:) method is marked as iOS 18+ but my app crashes when it launches on iOS 18+, even if I wrap the lines in #if available(iOS 26, *). It works fine on iOS 26+.
Any idea if that can be solved and how?
Documentation: https://developer.apple.com/documentation/corespotlight/cssearchableitem/init(appentity:)-89ehq
cc @mgorbach
-
The CSSearchableItem(appEntity:) method is marked as iOS 18+ but my app crashes when it launches on iOS 18+, even if I wrap the lines in #if available(iOS 26, *). It works fine on iOS 26+.
Any idea if that can be solved and how?
Documentation: https://developer.apple.com/documentation/corespotlight/cssearchableitem/init(appentity:)-89ehq
cc @mgorbach
-
The CSSearchableItem(appEntity:) method is marked as iOS 18+ but my app crashes when it launches on iOS 18+, even if I wrap the lines in #if available(iOS 26, *). It works fine on iOS 26+.
Any idea if that can be solved and how?
Documentation: https://developer.apple.com/documentation/corespotlight/cssearchableitem/init(appentity:)-89ehq
cc @mgorbach
-
The CSSearchableItem(appEntity:) method is marked as iOS 18+ but my app crashes when it launches on iOS 18+, even if I wrap the lines in #if available(iOS 26, *). It works fine on iOS 26+.
Any idea if that can be solved and how?
Documentation: https://developer.apple.com/documentation/corespotlight/cssearchableitem/init(appentity:)-89ehq
cc @mgorbach
-
Apple, can you please explain why running Shortcuts & App Intents on an iOS 18 simulator works fine but fails miserably on iOS 26 and iOS 27?
Can you please fix that for this release cycle?
Feedback: FB23342158
Project is a sample code from Apple: https://developer.apple.com/documentation/appintents/acceleratingappinteractionswithappintents
-
Apple, can you please explain why running Shortcuts & App Intents on an iOS 18 simulator works fine but fails miserably on iOS 26 and iOS 27?
Can you please fix that for this release cycle?
Feedback: FB23342158
Project is a sample code from Apple: https://developer.apple.com/documentation/appintents/acceleratingappinteractionswithappintents
-
Apple, can you please explain why running Shortcuts & App Intents on an iOS 18 simulator works fine but fails miserably on iOS 26 and iOS 27?
Can you please fix that for this release cycle?
Feedback: FB23342158
Project is a sample code from Apple: https://developer.apple.com/documentation/appintents/acceleratingappinteractionswithappintents
-
Apple, can you please explain why running Shortcuts & App Intents on an iOS 18 simulator works fine but fails miserably on iOS 26 and iOS 27?
Can you please fix that for this release cycle?
Feedback: FB23342158
Project is a sample code from Apple: https://developer.apple.com/documentation/appintents/acceleratingappinteractionswithappintents
-
I tried with the attached code. Wdyt?
It seems the available choices come from the suggestedEntities if implemented, then from allEntities (EnumerableEntityQuery).
If suggestedEntities, there doesn't seem to be a way to choose something else.
And allEntities could mean a lot!
-
I tried with the attached code. Wdyt?
It seems the available choices come from the suggestedEntities if implemented, then from allEntities (EnumerableEntityQuery).
If suggestedEntities, there doesn't seem to be a way to choose something else.
And allEntities could mean a lot!
-
I tried with the attached code. Wdyt?
It seems the available choices come from the suggestedEntities if implemented, then from allEntities (EnumerableEntityQuery).
If suggestedEntities, there doesn't seem to be a way to choose something else.
And allEntities could mean a lot!
-
I tried with the attached code. Wdyt?
It seems the available choices come from the suggestedEntities if implemented, then from allEntities (EnumerableEntityQuery).
If suggestedEntities, there doesn't seem to be a way to choose something else.
And allEntities could mean a lot!
-
App Intents question (again 😅): I notice that some "Find" intents allow to choose specific related items when filtering (e.g. an album when searching for a photo or an author when searching for books) instead of a textfield.
How's that done? What drive the available choices?
-
App Intents question (again 😅): I notice that some "Find" intents allow to choose specific related items when filtering (e.g. an album when searching for a photo or an author when searching for books) instead of a textfield.
How's that done? What drive the available choices?
-
App Intents question (again 😅): I notice that some "Find" intents allow to choose specific related items when filtering (e.g. an album when searching for a photo or an author when searching for books) instead of a textfield.
How's that done? What drive the available choices?
-
App Intents question (again 😅): I notice that some "Find" intents allow to choose specific related items when filtering (e.g. an album when searching for a photo or an author when searching for books) instead of a textfield.
How's that done? What drive the available choices?
-
#AppIntents IndexedEntity type is iOS 18+
My app minimum deployment is set to iOS 17+
My app compiles fine and run on a iOS 17 simulator 🤔I'm curious, how is that possible?
-
#AppIntents IndexedEntity type is iOS 18+
My app minimum deployment is set to iOS 17+
My app compiles fine and run on a iOS 17 simulator 🤔I'm curious, how is that possible?
-
#AppIntents IndexedEntity type is iOS 18+
My app minimum deployment is set to iOS 17+
My app compiles fine and run on a iOS 17 simulator 🤔I'm curious, how is that possible?
-
#AppIntents IndexedEntity type is iOS 18+
My app minimum deployment is set to iOS 17+
My app compiles fine and run on a iOS 17 simulator 🤔I'm curious, how is that possible?
-
With “Find…” actions in Apple #Shortcuts, is there a way to specify only the date part (not the time) for a filter?
I now I can omit the time part in my app’s queries but it’s not very intuitive for a user in my opinion.
Asking for a friend implementing #AppIntents.
-
With “Find…” actions in Apple #Shortcuts, is there a way to specify only the date part (not the time) for a filter?
I now I can omit the time part in my app’s queries but it’s not very intuitive for a user in my opinion.
Asking for a friend implementing #AppIntents.
-
With “Find…” actions in Apple #Shortcuts, is there a way to specify only the date part (not the time) for a filter?
I now I can omit the time part in my app’s queries but it’s not very intuitive for a user in my opinion.
Asking for a friend implementing #AppIntents.
-
With “Find…” actions in Apple #Shortcuts, is there a way to specify only the date part (not the time) for a filter?
I now I can omit the time part in my app’s queries but it’s not very intuitive for a user in my opinion.
Asking for a friend implementing #AppIntents.
-
one interesting side effect of #AppIntents `supportedModes`, when set to `foreground`: it also opens a window of the default scene in a multi-window environment. Fixed by using foreground(dynamic), which allowed me to foreground the app with openURL using the appropriate scene for the url. #iosdev
-
one interesting side effect of #AppIntents `supportedModes`, when set to `foreground`: it also opens a window of the default scene in a multi-window environment. Fixed by using foreground(dynamic), which allowed me to foreground the app with openURL using the appropriate scene for the url. #iosdev
-
one interesting side effect of #AppIntents `supportedModes`, when set to `foreground`: it also opens a window of the default scene in a multi-window environment. Fixed by using foreground(dynamic), which allowed me to foreground the app with openURL using the appropriate scene for the url. #iosdev
-
So… I’ve just learned that most of my adoration for #AppIntents was premature. 😆 I discovered why they didn’t work from actionable notifications, by having the same issue when I tried to use them in .onMove. 😬
#BuildInPublic #IndieHacker #iOSDev #IndieDev -
So… I’ve just learned that most of my adoration for #AppIntents was premature. 😆 I discovered why they didn’t work from actionable notifications, by having the same issue when I tried to use them in .onMove. 😬
#BuildInPublic #IndieHacker #iOSDev #IndieDev