๐ฑ ๐๐ฌ๐ฌ๐ฎ๐ #๐๐ ๐ข๐ฌ ๐จ๐ฎ๐ญ!
This week's squad:
๐จ ๐ฎ๐๐๐๐๐๐๐๐๐ ๐ฐ๐๐๐๐๐ ๐๐๐๐ ๐ฐ๐๐๐๐ ๐ท๐๐๐๐๐๐๐๐๐
๐งช ๐ท๐๐๐๐๐๐๐๐๐๐๐๐
๐ป๐๐๐๐
๐ง ๐บ๐๐๐๐๐ ๐ด๐๐๐๐๐๐๐
๐ ๐ฎ๐ฏ ๐จ๐๐๐๐๐๐ ๐ฉ๐๐๐๐
๐
โณ ๐ป๐๐๐ ๐ฐ๐
๐๐๐๐๐๐
๐ฌ ๐จ๐๐๐๐ ๐ต๐๐๐๐๐๐๐๐๐๐๐๐
๐ฌ ๐ฝ๐๐
๐๐ ๐๐ ๐๐๐๐๐๐๐ถ๐บ
โค๏ธ ๐ฏ๐๐๐๐๐๐ฒ๐๐ ๐ป๐๐๐๐๐๐๐
๐ https://ios-newsletter.snappmobile.io/issues/2025-11-14-issue-66.html by @snappmobile
Added tests for fetching public lists by ID, and updated the route paths for fetching paged public lists. Tomorrow night, let's think through how we can sync these effectively. See you then!
๐ Tomorrowโs stream: https://youtube.com/live/XbdGSjvv9cc
โฎ๏ธ Playlist so far: https://www.youtube.com/playlist?list=PLRxjf93xotuofCtaxtGOcWeuxVZYJyY-m
๐ฒ Download Jiiiii: https://apps.apple.com/app/apple-store/id6472801548?pt=14724&ct=MastodonCCStreams&mt=8
#Jiiiii #DevStream #tvOS #visionOS #macOS #iOS #iPadOS #Anime #Swift #SwiftUI #Vapor #WebAuthn #BuildInPublic #TestFlight #PWA #WebPush
I'm making a seasonal anime guide app, in the open for all to experience and learn from.
Let's rethink how owners are decoded, and add more list routes!
#Jiiiii #DevStream #tvOS #visionOS #macOS #iOS #iPadOS #Anime #SwiftLang #SwiftUI #Vapor #WebAuthn #BuildInPublic #TestFlight #PWA #WebPush
Come chill with me: https://youtube.com/live/N_UquJJAdHI
Appleโs on-device LLM when asked for an SF Symbol: chaos.
Appleโs on-device LLM when asked for one emoji: extremely competent.
So Hour by Hour now uses emoji as a middle layer for icon picking. Welcome to modern computing.
Details in my blog post: https://joethephish.me/blog/apple-foundation-model-icon-picking/
#buildinpublic #swift #swiftui
On macOS, API Orbit supports tabbed requests. Switch between endpoints like in an IDE.
#APIOrbit #MacDev #SwiftUI #APItools
#TIL #SwiftUI nil View can also be put in ViewBuilder, no if let needed...
๐ LinkBay ra! Quแบฃn lรฝ liรชn kแบฟt bแบฃo mแบญt iOS, SwiftUI hoแบทcp, ะธะฝะถะตะฝะตัๅ้o_TRACKING. Hแปc sinh ca hแปc ra app. Tรญnh nฤng chรญnh: 100 rรฉcolte (bachunicipal + dรนng SWIFTData) , khรกm phรกch. Coimess tแบกi App Store. #LinkBay #SwiftUI #PrivacyFirst #iOS Developer #M cristiana
SwiftUI instrument tip: take the following steps to find the code causing long updates:
1. Right-click on a red or orange bar in the graph.
2. Choose Set Inspection Range.
3. Switch to the Time Profiler instrument.
4. Hide System Libraries.
5. Double-click a function to see the lines of code causing the long update.
Cleaned up tests, and added a new route for loading public lists by ID. Tomorrow, let's clean up the paths for loading routes by owner, and start working on loading entries for lists. See you tonight!
๐ Tomorrowโs stream: https://youtube.com/live/N_UquJJAdHI
โฎ๏ธ Playlist so far: https://www.youtube.com/playlist?list=PLRxjf93xotuofCtaxtGOcWeuxVZYJyY-m
๐ฒ Download Jiiiii: https://apps.apple.com/app/apple-store/id6472801548?pt=14724&ct=MastodonCCStreams&mt=8
#Jiiiii #DevStream #tvOS #visionOS #macOS #iOS #iPadOS #Anime #Swift #SwiftUI #Vapor #WebAuthn #BuildInPublic #TestFlight #PWA #WebPush
I'm making a seasonal anime guide app, in the open for all to experience and learn from.
Let's fix how paths are encoded in tests to support cursors properly!
#Jiiiii #DevStream #tvOS #visionOS #macOS #iOS #iPadOS #Anime #SwiftLang #SwiftUI #Vapor #WebAuthn #BuildInPublic #TestFlight #PWA #WebPush
Come chill with me: https://youtube.com/live/r0asYeNp8hE
Vague, unconfirmed and unvalidated theory about #SwiftUI thatโs growing in my head:
If you build your whole app in SwiftUI, including all navigation, etc., no UIKit/AppKit, then itโs *way* too easy to end up with huge cross-app interdependencies where a change in one tiny part of your data model changes something in some completely different place in your UI and the bigger your app and data model becomes the more likely youโll end up with random updates that your UI that you cannot understand or debug.
(This may be made worse by using CoreData and `@FetchRequest` magic)
To counter that, youโll want to cut your appโs UI into smaller fully independent chunks. A good way to do that and ensure you are not ending up with accidental dependencies across screens, is to wrap each โscreenโ in a ViewController.
Basically: use UIKit/AppKit for navigation, but use SwiftUI for creating components and combining components into a screen.
Maybe the interaction between these view controllers might be best represented by a story board. So the story board gives you a visual representation of the navigation paths in your app and the SwiftUI previews give you an interactive idea of how each screen behaves on its own.
Thoughts? Do other people encounter the same issues with too many interdependencies and unexpected updates in big pure SwiftUI apps? Does this seem like a solution to you?
For the first time in my life, something I wrote, was released as an article today ๐๐ป
https://www.createwithswift.com/prompting-users-to-review-your-app/
Iโm really happy and excited about this opportunity. Let me know what youโd wanna read about! Let me know what you think about my article. Thank you for letting me do this Create with Swift๐ซฐ๐ป
#BuildInPublic #IndieDev #iOS #Dev #iOSDev #Swift #SwiftUI