Joachim<p>You cannot make two views in different hierarchies the same size. Containment-based layout is good enough. </p><p>The <a href="https://hachyderm.io/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftUI</span></a> View Body instrument only shows body executions despite a lot of work happening in other parts of the code. Leaf views like Text and container views like V/HStack also don’t have body getters so they also don’t show up. Having view bodies from your own named views show up + *some* SwiftUI views is good enough. (Note: the SwiftUI instrument in Instruments 26 was *significantly* improved. I believe it fixes some of these issues no have not formed an opinion on it, yet)</p><p>A SwiftUI Form view in the grouped style is embedded into its own scroll view. In the grouped style it’s not in a scroll view. There is no way to get rid of the scroll view around a grouped form to eg embed it in your own scroll view with additional UI. Having Form only work well if it’s filling the whole content of the current container is good enough. </p><p>Being able to completely disable interactive dismiss of sheets is good enough. There is no need to have a delegate callback (like in UIKit) that would allow putting up a confirmation dialog if data would be lost by „swipe to dismiss“. You can either turn it in or off, that’s it. </p><p>Applying a background modifier to a Grid does not actually set the background of the grid but only of all the individual grid elements. That’s good enough. </p><p>Our design Toolkits for Figma and Sketch still contain the default cell styles from UIKit (single label, title + subtitle label, label + value) but there isn’t actually any way to easily create these in SwiftUI. It’s good enough to have devs work with designers to figure out what the precise measurements, fonts etc. in Figma are to try to replicate what‘s sold to designers as a default component in SwiftUI. </p><p>Who needs a target-action-first-responder pattern in menus? Action closures should be good enough for everyone. It you really want to, you can just call NSApplication to invoke that responder chain manually from the closure. </p><p><a href="https://hachyderm.io/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOS</span></a> <a href="https://hachyderm.io/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a></p>
101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.
Administered by:
Server stats:
477active users
101010.pl: About · Status · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.5.0-alpha.2
#uikit
2 posts · 1 participant · 0 posts today
Joachim<p>I think I just figured out why I (and I think several other <a href="https://hachyderm.io/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOS</span></a> developers who have used <a href="https://hachyderm.io/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a> before) have developed somewhat of an animosity against <a href="https://hachyderm.io/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftUI</span></a>: </p><p>SwiftUI makes simple things really simple. It also makes some very specific complex things simple. </p><p>But despite the theoretically really high customizability (it’s all custom views with lots of modifiers overall), that‘s at first glance much higher than UIKit, getting things *just right* and creating a solution that feels just *excellent* is really hard. And by now I’m convinced that creating excellent solutions that really fit in well with the OS and offer a great, frictionless UX to people using your app is *harder* in SwiftUI. </p><p>However, creating a solution that works and is good enough is *easier* in SwiftUI. With it you fairly quickly arrive at a solution where it’s hard to argue that the small pieces of friction, the slight irregularities in the UI, the bits where people can accidentally „hold it wrong“, that these things should be removed. </p><p>I believe these bits of friction occur more often in SwiftUI and are harder to remove than in UIKit. </p><p>Add to that the higher initial cost of getting a working solution in UIKit at all and this *strongly* tips the balance in favor of „good enough“ UX when using SwiftUI, and away from excellent UX. </p><p>And I hate that about SwiftUI.</p>
Nico Reese<p>This is 2023. See that wild blip? That's one repost from <span class="h-card" translate="no"><a href="https://mastodon.social/@stroughtonsmith" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>stroughtonsmith</span></a></span>'s showcases that generated roughly 1000€ in just a few hours. You can see this was kind of the start of an upward trajectory of natural purchases without any big press coverage. It's clear there's a lot more opportunities waiting, maybe it's time to do something about it. <a href="https://mastodon.social/tags/BuildInPublic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BuildInPublic</span></a> <a href="https://mastodon.social/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftUI</span></a> <a href="https://mastodon.social/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a></p>
Nico Reese<p>This is what you can expect from an app that's in a relatively crowded category without running ads and barely any press coverage using a mixture of lifetime in-app purchase and subscription. Could I do much more? Yes. Am I too lazy to seize all the opportunities? Also yes.</p><p><a href="https://mastodon.social/tags/BuildInPublic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BuildInPublic</span></a> <a href="https://mastodon.social/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftUI</span></a> <a href="https://mastodon.social/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a></p>
Taylor Arndt<p>iOS devs: do you really need that custom control?<br>I keep seeing custom sliders, buttons, and form fields in audits—often not accessible. Native UIKit and SwiftUI components support VoiceOver, manage focus, and evolve with iOS.<br>So why reinvent the wheel?<br>When do you go custom—and how do you make sure it’s accessible?<br><a href="https://iosdev.space/tags/iOSDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOSDev</span></a> <a href="https://iosdev.space/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftUI</span></a> <a href="https://iosdev.space/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a> <a href="https://iosdev.space/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Accessibility</span></a> <a href="https://iosdev.space/tags/A11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>A11y</span></a> <a href="https://iosdev.space/tags/InclusiveDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InclusiveDesign</span></a> <a href="https://iosdev.space/tags/MobileDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MobileDev</span></a></p>
Brian Gerfort🇺🇦:shuttersnitch:<p>Speaking of code.. Does anyone know of a way to call the handler of a UIAction in a way that won't upset App Review? <a href="https://mastodon.nu/tags/Xcode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Xcode</span></a> <a href="https://mastodon.nu/tags/iOSDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOSDevelopment</span></a> <a href="https://mastodon.nu/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a></p>
Krzysztof Kołacz<p><strong>iOS 26 zdradza możliwe plany Apple na składanego iPhone’a</strong></p><p>Podczas sesji <a href="https://imagazine.pl/tag/WWDC25/" rel="nofollow noopener" target="_blank">WWDC 2025</a> Apple subtelnie zasugerowało nadchodzące zmiany sprzętowe. </p><p>Podczas jednej z sesji dla deweloperów „Make your UIKit app more flexible” ujawniono, że aplikacje zbudowane przy użyciu iOS 26 SDK nie będą już skalowane ani „letterboxowane” na nowych rozmiarach ekranów — co może oznaczać przygotowania na zupełnie nową kategorię urządzeń.</p><p>Dotąd Apple automatycznie dopasowywało starsze aplikacje do nowych ekranów, np. wyższych iPhone’ów czy nowych iPadów. Od iOS 26 to się zmienia — co zdaniem wielu analityków może być najmocniejszą jak dotąd wskazówką, że składany iPhone jest bliski premiery.</p><p>Dodatkowo, wcześniejsze przecieki z Weibo sugerują, że Apple testuje składany prototyp z ekranem wewnętrznym o proporcjach 14,1:10 i zewnętrznym 14,6:10 oraz bocznym Touch ID.</p><p>Nowe zasady projektowania interfejsu i zmiany w SDK wyraźnie wskazują na to, że Apple szykuje się na urządzenie z nietypowym formatem ekranu — co idealnie pasuje do spekulacji o nadchodzącym składanym iPhonie.</p><blockquote><p><a href="https://imagazine.pl/2025/06/13/czego-nie-pokazano-podczas-wwdc-2025-czesc-3/" rel="nofollow noopener" target="_blank">Czego nie pokazano podczas WWDC 2025 – część 3</a></p></blockquote><p></p><p>Podobne nowości, których nie wymieniono podczas Apple Event otwierającego tegoroczne WWDC 2025, a które pojawiły się na sesjach deweloperskich — omawiam w trzech częściach wpisów im poświęconych <a href="https://podcasts.apple.com/pl/podcast/397-m%C4%99drzec-szkie%C5%82ko-i-oko-czyli-wwdc-2025/id1329043441?i=1000712702651" rel="nofollow noopener" target="_blank">oraz ostatnim odcinku mojego podcastu</a>.</p><p></p><p><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/apple-fold/" target="_blank">#AppleFold</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/apple-przecieki/" target="_blank">#ApplePrzecieki</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/digital-chat-station/" target="_blank">#DigitalChatStation</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/elastyczny-interfejs/" target="_blank">#elastycznyInterfejs</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/ios-26/" target="_blank">#iOS26</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/ios-sdk/" target="_blank">#iOSSDK</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/ipados-26/" target="_blank">#iPadOS26</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/iphone-2026/" target="_blank">#iPhone2026</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/iphone-fold/" target="_blank">#iPhoneFold</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/nowe-urzadzenia-apple/" target="_blank">#noweUrządzeniaApple</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/nowy-rozmiar-ekranu/" target="_blank">#nowyRozmiarEkranu</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/plotka/" target="_blank">#plotka</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/plotki/" target="_blank">#Plotki</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/skladany-iphone/" target="_blank">#składanyIPhone</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/uikit/" target="_blank">#UIKit</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://imagazine.pl/tag/wwdc-2025/" target="_blank">#WWDC2025</a></p>
Kuba Suder • @mackuba.eu on 🦋<p>"Five years in, SwiftUI is no longer the future of Apple platform development. It’s the present. And UIKit? It’s starting to look like Objective-C, still there, still supported, but clearly not where the innovation is happening." <a href="https://martianbase.net/tags/wwdc25" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wwdc25</span></a> <a href="https://dimillian.medium.com/whats-new-with-swift-26-f17e98b07c87?sk=cdba6cf719ad38e5456bc91a74afc6c6" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dimillian.medium.com/whats-new</span><span class="invisible">-with-swift-26-f17e98b07c87?sk=cdba6cf719ad38e5456bc91a74afc6c6</span></a></p><p><a href="https://martianbase.net/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftUI</span></a> <a href="https://martianbase.net/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a> <a href="https://martianbase.net/tags/iOSDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOSDev</span></a></p>
Marcin Krzyzanowski<p>Notepad.exe 1.1 - iOS support is live! 🚀<br>Build <a href="https://mastodon.social/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftUI</span></a>, <a href="https://mastodon.social/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a>, whatever - each playground gets its own iOS simulator. No setup, just run. go get it: <a href="https://notepadexe.com/news" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">notepadexe.com/news</span><span class="invisible"></span></a></p><p><a href="https://mastodon.social/tags/WWDC25" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WWDC25</span></a> starts tomorrow! Perfect timing to mess around with new APIs.</p>
Marcin Krzyzanowski<p><span class="h-card" translate="no"><a href="https://mastodon.online/@martind" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>martind</span></a></span> <span class="h-card" translate="no"><a href="https://cosocial.ca/@shayman" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>shayman</span></a></span> especially for you <a href="https://mastodon.social/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a></p>
Nico Reese<p>Seems like Apple also struggles with layouting, especially with larger text sizes. <a href="https://mastodon.social/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftUI</span></a> <a href="https://mastodon.social/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a> <a href="https://mastodon.social/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOS</span></a></p>
sam henri gold<p>did *anyone* know this was a thing? the animation the Photos app does when deleting an item is just…a built-in, standard UIKit animation <a href="https://developer.apple.com/documentation/uikit/uiview/systemanimation" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">developer.apple.com/documentat</span><span class="invisible">ion/uikit/uiview/systemanimation</span></a></p><p><a href="https://hachyderm.io/tags/iosdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iosdev</span></a> <a href="https://hachyderm.io/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>swift</span></a> <a href="https://hachyderm.io/tags/uikit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>uikit</span></a></p>
Jaanus Kase<p><a href="https://iosdev.space/tags/AppKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AppKit</span></a> <a href="https://iosdev.space/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a> <a href="https://iosdev.space/tags/CollectionView" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CollectionView</span></a></p><p>Any (NS/UI)CollectionView fans here? I’m trying to make a good collection view UI. It is just a simple flat scrolling column of things, should be simple layout.</p><p>I want the cells to size themselves to the SwiftUI content in them, which they almost do, but not when I resize the window and things start to wrap differently.</p><p>What am I missing? How should I make the heights respond better to window resizing?</p><p>Code: <a href="https://gist.github.com/jaanus/66e3d863941ba645c88220b8a22970e1" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">gist.github.com/jaanus/66e3d86</span><span class="invisible">3941ba645c88220b8a22970e1</span></a></p>
bitbonk<p><span class="h-card" translate="no"><a href="https://mastodon.social/@woolie" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>woolie</span></a></span> <span class="h-card" translate="no"><a href="https://tapbots.social/@todd" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>todd</span></a></span> <span class="h-card" translate="no"><a href="https://tapbots.social/@ivory" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ivory</span></a></span> Ah right. So it might be that this is a <a href="https://mastodon.social/tags/Catalyst" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Catalyst</span></a> problem only and wouldn’t be a problem with <a href="https://mastodon.social/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftUI</span></a> or <a href="https://mastodon.social/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a> <a href="https://mastodon.social/tags/AppKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AppKit</span></a> <br>(I am not an apple developer, so I have no clue.)</p>
Nico Reese<p>30 seconds into a <a href="https://mastodon.social/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftUI</span></a> app and the toolbar divider does not disappear when completely scrolled to the top like any other <a href="https://mastodon.social/tags/AppKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AppKit</span></a> or even <a href="https://mastodon.social/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a> <a href="https://mastodon.social/tags/Catalyst" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Catalyst</span></a> app. God, have mercy. So frustrating that I have to lose out on all the SwiftUI goodies just because the damn framework can't even get the basics right.</p>
GregInTheNorth<p>With the irreplaceable help of <span class="h-card" translate="no"><a href="https://twit.social/@kharrison" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kharrison</span></a></span>'s Modern AutoLayout book, and a lot of thinking, I have got the core initial layouts working in UIKit. This is a UITabBarController (WWDC 2024 style) and programmatic split pane views, with a segmented control on the top of one. Mac Catalyst continued to morph this layout onto MacOS well. Never done layouts and controls purely in Swift before.</p><p><a href="https://mastodon.social/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a> <a href="https://mastodon.social/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOS</span></a> <a href="https://mastodon.social/tags/MacCatalyst" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MacCatalyst</span></a> <a href="https://mastodon.social/tags/macos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macos</span></a> </p><p><a href="https://kharrison.gumroad.com/l/albook" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">kharrison.gumroad.com/l/albook</span><span class="invisible"></span></a></p>
Jonathan Joelson<p>Do any iOS devs have experience migrating an existing set of custom <a href="https://mastodon.social/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a> design system UI controls to <a href="https://mastodon.social/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftUI</span></a>? Is wrapping with UIViewRepresentable an effective technique or is it better to reimplement controls with SwiftUI?</p><p>I’ve heard about layout bugs when using UIKit controls in a SwiftUI view hierarchy, but I don’t have a sense for how common or debilitating they are.</p><p><a href="https://mastodon.social/tags/iOSDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOSDev</span></a> <a href="https://mastodon.social/tags/DesignSystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DesignSystems</span></a></p>
Nico Reese<p>I saw an article recently that showed how you could correctly set the selection style in <a href="https://mastodon.social/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a> <a href="https://mastodon.social/tags/Catalyst" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Catalyst</span></a> to the way AppKit does it instead of the accent color. Something with selection prominence. Can't find the article nor the API for that any more. Anyone knows?</p>
Nico Reese<p>It's 2024 and <a href="https://mastodon.social/tags/UIKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UIKit</span></a> and <a href="https://mastodon.social/tags/Catalyst" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Catalyst</span></a> still insist on translating the view controller title to the window's subtitle and make the main title... the app's name? Why? Is there a non-hacky way to not do this?</p>
Steve Troughton-Smith<p>⭐️ I'm trying something completely new for 2025 as a (time-limited?) experiment:</p><p>I’m offering the complete Xcode/Swift source code to Lights Off (Universal, for iPhone, iPad, Mac and Vision Pro) for sale, to do with as you want, to re-brand or incorporate into your own apps/games, for a one-time purchase.</p><p>If successful, maybe I will offer more shipping, discontinued or unreleased apps in this manner in the future, maybe not — we'll find out!</p><p><a href="https://mastodon.social/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>swift</span></a> <a href="https://mastodon.social/tags/uikit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>uikit</span></a></p><p><a href="https://steventroughtonsmith.gumroad.com/l/dtfqn" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">steventroughtonsmith.gumroad.c</span><span class="invisible">om/l/dtfqn</span></a></p>
TrendingLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload