2
1

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?

More than 1 year has passed since last update.

SwiftAdvent Calendar 2022

Day 20

【Swift、英文記事引用】SwiftUI vs UIKit in 2023

Last updated at Posted at 2022-12-20

気になる英文記事を引用して記事を書いてみました。

引用元の記事は、タイトルが「SwiftUI vs UIKit in 2022, Which Framework Should Your App Use?」とありましたので、引用しながら考察してみます。

Within the iOS development community, there seems to be a heated debate between SwiftUI and UIKit.
Both of these frameworks offer a variety of benefits, while at the same time, each has its own set of drawbacks.
However the bottom line of both UIKit and SwiftUI is simple: Apple developed both frameworks to allow developers to create powerful applications.
The easiest way to imagine the differences between these two frameworks is that Apple made them easy to use based on the type of programmer using them.
A more visually oriented programmer would prefer UIKit, while a programmatic oriented programmer would prefer SwiftUI.

上記の部分は、記事の序論になります。箇条書きで要約すると、

  • iOSの開発コミュニティの中で、SwiftUIとUIKitに関する熱い議論が交わされている
  • よりビジュアルを重視するプログラマはUIKitを好み、プログラムを重視するプログラマはSwiftUIを好む

となりますでしょうか。シンプルなイントロとなっています。引き続き、引用記事を見ていきます。

UIKit
The predecessor to SwiftUI is responsible for the rise of Apple’s programming language, Swift.
With UIKit, the ability to build user interfaces is possible even without a strong programming background. This is due to the introduction of storyboards, a drag-and-drop solution to building user interfaces. With storyboards, building powerful applications is simplified for developers. While at the same time, allowing developers to save time due to storyboards doubling as a preview.
However this comes with distinct drawbacks: building a user interface programmatically (without storyboards) in UIKit is significantly more difficult compared to SwiftUI. Not only that, but UIKit is known as an imperative framework, which simply means you are stating how to do something.
In contrast to SwiftUI, which is a declarative framework, meaning you are declaring something you want to happen. If that sounds confusing, don’t worry, this just means the way in which code is structured is slightly different between SwiftUI and UIKit.
One final detail worth noting about UIKit, is that it’s an older framework. This means as time progresses, we may begin to see less support from Apple for UIKit, as SwiftUI continues to evolve.

上記の部分は、記事のUIKitの本論の部分になります。
中身をかいつまんで箇条書きにすると、

  • プログラミングの知識がなくてもstoryboardsの導入により、ユーザーインターフェースの構築が可能になる
  • UIKitでstoryboardsなしでプログラム的にユーザーインターフェイスを構築することは、SwiftUIと比べるとかなりハードルが高い
  • UIKitは古いフレームワークである

といったところでしょうか。

SwiftUI
SwiftUI has proven itself to be an absolute game changer in the world of iOS development due to the fact that SwiftUI offers syntax that is easy to understand and is structured in a way that makes sense.
Not only this, but SwiftUI is a much more powerful library. SwiftUI will only continue to evolve as a powerful language, as Apple continues to shift its focus away from UIKit.
SwiftUI takes everything Apple learned from UIKit, and provides developers with much better features that are unavailable in UIKit. One of these features includes creating even more powerful applications while at the same time using less code than UIKit.
However this comes with drawbacks, for example building user interfaces programmatically is the norm with SwiftUI.
With SwiftUI, more attention is shed on building user interfaces programmatically. This of course results in decreased attention for storyboards, depending on the preferences of a developer, this can be viewed as either a benefit or a drawback.
Although SwiftUI is becoming the superior framework for building iOS applications, many developers have still not learned how to work with SwiftUI.
This means it could be difficult to build a team of developers that are capable of building complex SwiftUI applications. However with time this issue will begin to resolve itself.

上記の部分は、記事のSwiftUIの本論の部分になります。
中身をかいつまんで箇条書きにすると、

  • SwiftUIは、AppleがUIKitから学んだことすべてを取り入れ、UIKitでは利用できない、はるかに優れた機能を開発者に提供する
  • これらの機能の1つは、UIKitよりも少ないコードで、同時にさらに強力なアプリケーションを作成することができる点である

といったところでしょうか。

2022年の今現在、SwiftUIUIKitもimportする機会が多いかと思います。storyboardsは、Swift開発のイントロには非常に向いているかも知れませんが、複雑なアプリケーション開発が求められている中で、非推奨ものになっていく可能性も高いと個人的には考えています。
ただ、少なくともあと数年はSwiftUIUIKitもimportする状況が続くのではないかと思っています。

引用文献

2
1
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
2
1

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?