SwiftUI is more than just a developer convenience

Posted in Apple

Apple announced SwiftUI at this year’s WWDC. It’s a new framework that will allow developers to build apps for iOS, Watch and Mac, all using the same codebase.

Cult of Mac sums it up nicely:

For an app to work on all three platforms, the developer needs to produce three separate versions of the user interface code. SwiftUI promises to change all this, because the same framework is native on all Apple platforms

Most talk has been about the obvious – it will encourage developers of iOS apps to also build a Mac and Watch app. And it’s that, of course, but I reckon there’s a tactical angle from Apple too.

A lot of developers who build an iOS app do so in something like Ionic or Xamarin instead of using native code for each platform. That means that they can reach both iOS and Android markets using one codebase and a few UI customisations for each.

Now that SwiftUI’s here, it makes it more difficult for developers who might have automatically reached for their cross-platform mobile framework of choice. They have to decide whether they want to produce an app for iOS and Android or an app for iOS, Mac and Apple Watch.

Of course, it depends on the app, but I bet a lot more devs are tempted to ditch Android and go for the Mac market instead.

Get them delivered!

If you enjoyed this and want all the latest articles delivered to your inbox every month, pop your email in the form below.

I don’t collect any data on when, where or if people open the emails I send them. Your email will only be used to send you newsletters and will never be passed on. You can unsubscribe at any time.

More posts

Here are a couple more posts for you to enjoy. If that's not enough, have a look at the full list.

  1. Lazy loading images without JavaScript

    Non-JavaScript lazy loading is a great progressive enhancement for image-heavy pages on the web. Just a simple HTML attribute and you’re away!

  2. The briefest of histories of responsive images

    There are a lot of things to consider when using images on the web. But why is it so complex? And how can we tackle that complexity?