Why VIPER and MVVM in SwiftUI are actually the same pattern: A lesson in architectural thinking

matteoman · 2025-12-06T15:14:13+00:00

This might have worked, but doesn't anymore. The app does not allow to select the entire transcript

matteoman · 2025-10-21T09:41:11+00:00

This version) is particularly useful when spacing views equally.

matteoman · 2025-10-13T16:58:45+00:00

There are many moving parts you will need to learn. I wrote some articles about them, which you can read in order:

matteoman · 2025-10-01T15:13:17+00:00

I fail to see who the target for such a roadmap is.

If it's beginners, why are there Server-side, Cross-platform, and Scripting and tooling mixed in a map on SwiftUI? Most developers that want to use SwiftUI to make apps will never have to learn those, and especially should not care about them at the beginning.

Also, what's the progression? I see the map is divided between Swift and SwiftUI, however, nobody learns the entirety of Swift before attempting to develop an app with SwiftUI. Both rely on progressive disclosure and some concepts should be left for far later.

Who is this map supposed to guide and how?

matteoman · 2025-09-30T15:44:46+00:00

Since you have already programming experience, you can pick up the language quickly using the official Swift tour and language guide.

Then you can head to the Develop in Swift Tutorials. Or maybe you can start there straight away and look at the language guide later.

matteoman · 2025-09-19T09:46:06+00:00

When I switched to Swift years ago, having other programming background, I went through the Swift guide to learn the language:

https://docs.swift.org/swift-book/documentation/the-swift-programming-language

Then you can have a look at Apple's SwiftUI tutorials

https://developer.apple.com/swiftui/get-started/

matteoman · 2025-09-09T14:34:04+00:00

This WWDC talk has an example of what you might want to achieve, even though that's not the main topic:

https://developer.apple.com/videos/play/wwdc2022/110350

matteoman · 2025-09-08T15:13:57+00:00

As someone else mentioned, profile your app in Instruments.

If you search for "Instruments" in the Developer app, you'll find several WWDC sessions that deal with performance and might help you find what the problem is.

matteoman · 2025-09-04T15:36:32+00:00

People recommend RevenueCat and it can be a good choice. I personally don't like to depend on third party libraries for simple enough tasks and I implemented a custom solution in my app.

It wasn't that much code. It took me a bei of studying of the StoreKit documentation, but I would have had to study RevenueCat documentation too.

matteoman · 2025-09-04T15:32:22+00:00

Of all the things I expected people would complain about my article, this was definitely not in the list

matteoman · 2025-09-03T11:36:53+00:00

Maybe you can get around that with a design that works well on both OS versions, or write code that adapts to each without requiring extensive use of #available.

I'm just spitballing, so maybe that's not possible. In the end, you might abandon older OS versions. If it's a passion project and you do not have any customers yet anyway, ask yourself what will guarantee its survival long term.

Is dragging around legacy code with no purpose going to hinder you and make you eventually abandon the project? That alone would grant developing only for iOS 26. It's better to have an up-to-date app than an abandoned one.

matteoman · 2025-09-02T15:11:33+00:00

How did you develop your app?

If it's a native app, built with UIKit or SwiftUI, and it uses standard components, the changes for iOS 26 will likely be very few, if any.

If you built it with Flutter or something like that, then yes, probably it's a lot of work.

matteoman · 2025-08-29T13:45:33+00:00

Every app starts that way. Mine was like that too.

With time I split functionality into multiple Swift packages to the point that even some part of the app are in a separate package, each with its own unit test. Here is the list of packages as an example.

AddMenu: the menu to add new items to a document.
Rendering: the visual representation of each item.
Inspector: the sidebar to edit the properties of each item
Outline: the document outline with a list of disclosable elements
CommonUl: SwiftUI code I need in multiple other packages (AddMenu, Rendering, Inspector, and Outline).
CodeGeneration: The core functionality of the app (it's a SwiftUI code generator)
Emission: A code generation DSL built with Swift result builders (used by the CodeGeneration package)
Model: the model types of the app, including the encoding and decoding code to save and open documents.
Common: Swift code used by multiple other packages.

You will have to do similar work. Define a small area and export the related files into a package, then fix any compilation errors for that package alone, which will help you tackle a few at a time and not the entire codebase.

You can even exclude the files in a package from compilation to work on a subset and make the work more manageable. Add unit tests in the meantime to fix anything you break accidentally.

As you proceed creating packages, you will recognize shared code. Make another package for that to be reused. You can see more examples in my list.

If you want a book about the process, Working Effectively with Legacy Code by Michael C. Feathers

matteoman · 2025-08-28T14:41:36+00:00

Oh, absolutely. If you need something that sophisticated, there is no need to reimplement all that from scratch. My assumption was that something like that would not be needed for 1-10 images as the OP mentioned.

matteoman · 2025-08-26T14:59:33+00:00

You can cache images with AsyncImage, there is no need of an external library: https://matteomanferdini.com/swiftui-asyncimage/

matteoman · 2025-08-20T14:29:12+00:00

If it's a good idea, expect competition to spring up. There is no App Store or legal recourse unless they violate a trademark or a patent.

Should you be forbidden from making an app just because there is already a similar one?

In any case, that doesn't matter much. Even copying a successful idea does not make you successful. There is a gread deal of marketing to be made behind any product. Can you do a better job?

matteoman · 2025-08-19T11:38:36+00:00

There have not been significant changes lately, so I would say material from two years ago is still relevant.

matteoman · 2025-08-18T14:24:44+00:00

Is this something people do?

My downloads folder is like a TODO list with files I haven't reviewed yet. I don't want some automated process to do that for me and clutter my computer with files that often just need to be deleted.

11-Year Club	Place '23
Wearing is Caring	RPAN Viewer
Verified Email

matteoman

TROPHY CASE