{"id":44253,"date":"2024-07-29T16:09:42","date_gmt":"2024-07-29T20:09:42","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=44253"},"modified":"2024-07-29T16:09:42","modified_gmt":"2024-07-29T20:09:42","slug":"magic-lasso-redesigned","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/07\/29\/magic-lasso-redesigned\/","title":{"rendered":"Magic Lasso Redesigned"},"content":{"rendered":"

Matthew Bickham<\/a>:<\/p>\n

\n

Under the covers, Magic Lasso has been re-architected using SwiftUI<\/a> which enables a shared but tailored UI implementation across the iPhone, iPad and Mac apps.<\/p>\n\n

The move to SwiftUI delivers improved user accessibility including complete support for variable type sizing and Dark mode. In the future, multilingual support will also be considerably easier to rollout.<\/p>\n\n

Over 95% of the app’s UI is now written in SwiftUI, an increase from less than 30% this time last year<\/a>.<\/p>\n<\/blockquote>\n\n

Matthew Bickham<\/a>:<\/p>\n

What I did notice going through the process though is that if you base the implementation on the SwiftUI defaults you will definitely get some strange, and especially on macOS, less than ideal behaviour. This led me to not use some of the inbuilt SwiftUI approaches for certain UI elements. Instead, I created custom implementations that better fit within user expectations and best practice iOS and macOS conventions.<\/p>

[…]<\/p>

A huge part of the work was actually prototyping approaches in SwiftUI to see what works well and what doesn’t. Once a clean path was discovered, the final implementation was relatively straightforward but it was based upon those learnings. The hard part was ensuring simplicity and not falling into the many traps of weird behaviour that are present in the System Settings UI for instance.<\/p>

Personally I prefer working in SwiftUI now – probably because I no longer need to implement two similar UIs in both UIKit and AppKit.<\/p><\/blockquote>\n\n

Previously:<\/p>\n