I have an MVP that I'm pretty proud of and I'm ready to release a beta, but for some reason I'm shy to release it. That doesn't make a whole lotta sense.

It’s my birthday weekend and I’m running a special sale on my #Swift and #SwiftUI books - just for my followers, and just for the next 48 hours!

Use the code BDWK25 at checkout to get 20% off any book or bundle:
https://books.nilcoalescing.com/

Very proud how far I’ve come in a year. Tho I’m still barely surviving as an indie developer , I feel like I’ve survived the hardest part.

Creating a product people actually enjoy using. We’ve built a small but growing community.

But unfortunately that’s not enough, I have to get the word out…which means me posting more on social media…
#indiedev #SwiftUI #iOS #macos #aitools #research #search #apple #apps #pleaseboost

Getting Started: macOS Apps with SwiftUI http://leanpub.com/courses/leanpub/macos-apps-with-swiftui by Grace Huang is the featured course on the Leanpub homepage! https://leanpub.com #appdevelopment #macOS #SwiftUI

A ViewModel is a very specific concept. If you think you need a ViewModel in #SwiftUI (probably not necessary because SwiftUI has formatters like AppKit), I'm pretty sure it should be a struct (representing the projection of the actual model to the values required by the View).
Not, ever, a StateObject.

I'm working on a #SwiftUI view modifier that calculates a foreground Color that maintains sufficient contrast with the background and also takes the font into account. This can improve #accessibility without too much design-time overhead.

It's using APCA by @Myndex.

Heeeelp!

What does the following error mean, and how do I fix it? It happens, when I call `modelContext.save()` in a SwiftUI view.

"SwiftData/ModelCoders.swift:105: Fatal error: Composite Coder only supports Keyed Container”

Edit: Solved! It appears SwiftData does not support Duration properties in models. Changing it to a TimeInterval instead fixes it.

Getting Started: macOS Apps with SwiftUI http://leanpub.com/courses/leanpub/macos-apps-with-swiftui by Grace Huang is the featured online course on the Leanpub homepage! https://leanpub.com #macOS #programming #SwiftUI

Just moved over from mastodon.design, so it's time for another #introduction!

I'm Toni

I’m a software #designer, though I’m spending more and more time writing code, mostly in #swiftui and #react

When I'm not heads down at work, you'll catch me #cycling, eating my weight in oranges, walking with my dog Xenon, or just getting lost in a new #book, #anime, or #manga.

I’m also a passionate #yugioh collector, #nba fan and I play #guitar occasionally.

More → https://www.toni.li/about

Once again I have stumbled onto something I don’t understand.

In the entry point for my app I set a NavigationContext in the environment, and when I run the app and navigate between views, at some random point, it throws the error in the second image, and the debugger indicates it is on the “struct FooApp: App {“ line.

What is going on? Help!

In the subviews I am accessing the context from the env like so: “@ Environment(NavigationContext.self) var context”.

Well ain't this a spooky feeling. First time ever. Bracing myself for my first rejection I'm assuming it's some sort of rite of passage.

Custom images from an asset catalog don't automatically resize with text. If an image is not purely decorative, we should ensure it scales appropriately when users adjust their preferred font size. We can easily do it with the ScaledMetric API in SwiftUI: https://nilcoalescing.com/blog/AdaptingImagesAndSymbolsToDynamicTypeSizesInSwiftUI/#scaling-custom-images
#SwiftUI #iOSDev

Learning about railroad tracks with paths.