あぁなるほど OpenIntentの扱いはMac見るとわかりやすい

OpenIntent

As for this> I’ve read - Universal Links - Custom URL scheme - AppDependencyManager They have similar outcomes but are meant for different jobs. Universal links are great for opening something in your iOS app and not your web app if they have it for example. Custom URL schemes have been around forever and are awesome for x-callback related ops. ADM is just a container for app specific logic. If you're trying to open an app entity, OpenIntent is what you should use.

For example, I’m trying to add an OpenIntent to navigate to a specific item in my app (/item/345). What’s the way on iOS 18? I’ve read - Universal Links - Custom URL scheme - AppDependencyManager - Etc…

My Build on @shelbyserves : OpenIntent Protocol # Build Content: > Open Intent Auction Router (reduce MEV, optimize price) > Weaknesses: user swap/bridge susceptible to front-run, bad pricing, MEV. > Idea: standard "Intent" (user describes goal: change A→B, receive at least X, deadline...) instead of calling DEX itself. > Protocol organizes auction/solver competition: many solvers submit bids to best fulfill their intent; on-chain only settles the result. > Ingredients: > • Intent schema (EIP-style) > • Solver registry bonding/slashing (anti-cheat) > • Settlement contract (verify conditions, distribute fees) > Open value: many wallets/dApps integrate the same intent standard. > Maker signs an off-chain Intent (EIP-712): wants to exchange tokenIn -> tokenOut. > Relayer/anyone posts intent to chain. > Solvers sends bid amountOut (whoever pays more tokenOut wins). > After deadline, anyone can finalize() to settle: > Maker receives tokenOut > The winning solver receives tokenIn which is escrow Link to github Build: github.com/STMTP95/OpenInten… @affinity_matrix I built from an idea Weaknesses: user swap/bridge susceptible to front-run, bad pricing, MEV.. let's check if I can develop from this direction on Shelby?

@jsnyder81 and I have a chance to talk about OpenIntent - we all need to push our tools vendors to support this as much as possible! Both for predictive, as well as validation survey data. packetpushers.net/podcasts/h…

Intents (from OpenIntent) change everything: instead of signing calldata, you sign what you want. Your goal → an intent. Agents/solvers handle execution. We’re building to protect those intents and keep users safe. The future UX is intent-based.

✍️ New Post ✍️ A short ode to `OpenIntent` in iOS 26: swiftjectivec.com/Open-Inten…

Production push, check! ✅ 🤖 Auto-scale, scope, walls out of beta! ✨ More sparkles 📦 Scope zones in OpenIntent 📡 A gazillion antennas 📓 Complete release notes: docs.hamina.com/planner/othe…

We're trying to get better with our release notices, so.. 🚨🥳 Production Push 🥳🚨 🏷️Renamed Feature Previews to Beta features 📕Report generation on all paid tiers 🐛Fixed a 3D rendering issue 🪲Fixed an OpenIntent upload bug 📡New APs! Release notes: docs.hamina.com/planner/othe…

なお↑のドキュメントみると OpenIntent に準拠する必要があるように見えるが、普通の AppIntent で openAppWhenRun = true でもOK ```swift struct OpenAppIntent: AppIntent { static var title: LocalizedStringResource = ... static var description = ... static var openAppWhenRun: Bool = true func perform() async throws -> some IntentResult { return .result() } } ```

アプリを起動するだけのコントロールウィジェットを作ってみたのだけど、普通のショートカットアクションとしては動くAppIntentの実装が、なぜかエラーが出て起動しない。 Extension側だから、本体側開くにはなんか違う機構が必要なのか、とOpenIntentに準拠しようとしてみたり（→ targetの指定が必要でやりたいこととマッチしない）、OpensIntentを使ってみたり（起動しなかった）したが、 結局正解は「同じインテントを本体・Extension両方のターゲットに追加する」だけだった... ちらっと公式ドキュメントに書いてある： > The system requires the Target Membership of the app intent to be set to both the app and the widget extension to open the app. developer.apple.com/document…

PSA: Use a universal link (eg, cardpointers.com/x) rather than a deep link (cardpointers:///x) to get controls to work with OpenIntent. Big change happened in the previous beta, by design it seems.

Anyone managed to get an OpenIntent with an AppEnum to work? I've followed this example, but nothing happens when I tap the ControlWidgetButton. And, how does one pass the correct enum in? developer.apple.com/document…

Yep, and the intent conforms to OpenIntent, but it never launches. Tried Apple’s example I just found @ developer.apple.com/document…, no go, either.

There's a new production push! What's new: ⚡ Interference heatmap for surveys (Beta) ❓ Adjustable guess range for surveys 🚫 Manually disable radios 💾 Export to OpenIntent 📔 Release notes: docs.hamina.com/planner/othe…

I wish I got a 💵 every time I hear that. It will come…. Also - I already promised you Openintent import during Q2. Is nothing enough 🤪🤪🤪👍

let's talk about which platforms you'd need. We could do it natively using vendor protocol, thru @jsnyder81 's OpenIntent, or... The challenge here is you'd need to import these manually, save to disk, then upload to Hamina. Not a terrible experience, just not a click of a button.

Nice!! @JussiKiviniemi just took the stage with @jsnyder81 to challenge all tool vendors to support #OpenIntent by the end of the half at #WLPC!!

I put a Q&A session on the calendar for Friday. If you haven’t joined the OpenIntent mailing list ping me for the meeting invite. Friday at 12:30 pacific 3:30 eastern.