VIM: A new SwiftUI Architecture for iOS 17

День тому

We all know MVVM, MVC, and perhaps even TCA. But might it be time to consider a new architecture? Let's explore how we can use the AppIntents framework to build clean & reusable code.
Join this channel to get access to perks:
/ @flowritescode
🚀 LaunchBuddy: apple.co/3iFcjjW
📚 Try CWC+: bit.ly/cwc_flo
☕️ Buy me a coffee: ko-fi.com/flowritescode
👋 Links: flowritesco.de
🛠 Forge: apple.co/3riG8MQ
Affiliate Links ❤
📕 SwiftUI & Combine Books: www.bigmountainstudio.com/a/t...
🔬 Get Reports about your apps: appfigures.com/r/5by3g
📊 Privacy focused analytics: dashboard.telemetrydeck.com/r...
💻 The most powerful mac app for developers: devutils.app/?ref=flo
☕️ Support me: ko-fi.com/flowritescode
If you have any video suggestions please feel free to let me know by a comment.
Get in contact via
Twitter: / flowritescode

КОМЕНТАРІ: 11

@indiekiduk 7 місяців тому

Usually wrapping an app action in an additional layer of framework indirection causes problems (and leads to a lot of wrapping/unwrapping boiler plate) so I'll be interested to hear how this idea pans out

@tscholze 7 місяців тому

This is by far the first ever "app-wide" usage of AppIntends that I ever saw. To be honest, this seems like the "thousands of micro services"-approach of the late 2010s in the web industry, but maybe I'm an old grumpy man that hated the transition from MVC to MVVM and now with SwiftUI back to MCV or MVI. I see advantages in having an intend per action like create, update, delete for me the question is, if you have a web service in the background with a repository to hold states (if it is not SwiftData) if this approach is still usable *hm*.

@jordancalhouncom 7 місяців тому

This intrigues the heck out of me

@marceljaeger 25 днів тому

Nice video and an interesting approach. What do you think about encapsulate code for actions in a simple type and create global methods? Then you have all actions in one place and you can use it everywhere in your app.

@FloWritesCode 13 днів тому

Not a fan of that, as I see no advantage over AppIntents (expect for smaller code). Essentially you're saying to use one big ViewModel for the entire app, right?

@marceljaeger 13 днів тому

@@FloWritesCode Oke. No, not exactly. The data would be in the view. But all methods for buttons or other actions are in a separated type that you can access from all views. And you pass the data that the method needs as parameters.

@tiIIus 7 місяців тому

Could you make a video on how to implement a fully working subscription just with StoreKit 2 and the new SwiftUI SubscriptionStoreView?

@FloWritesCode 6 місяців тому

I'm planning to do that, yes. It's not on the Roadmap right now though, so I'd suggest watching someone else's video on the topic in the mean time (or just the WWDC talk from this year where they presented the StoreKit news).

@arjundureja 7 місяців тому

So in this example, let's say you wanted to add the ability to update and delete food. Would you need separate AppIntents for those two actions? If so, having a single view model that encapsulates all that logic sounds better to me

@FloWritesCode 7 місяців тому

Yes, exactly. You‘d need one AppIntent for each piece of logic in your app. Swift Macros might help automate that process, but it is some overhead for sure…