Ich habe gerade ausführlich den Obsidian Web Clipper im ObsidianGuide behandelt, da landet eine neue Catalyst-Version 1.13.1 von Obsidian auf meinem iPad, die das Clippen von Webseiten und anderen Inhalten über das Sharesheets deutlich vereinfacht, damit lassen sich Inhalte direkt aus vielen Apps heraus in Obsidian speichern. Da es sich im Moment um eine Funktion...
Ich poste gerne Bilder auf Bluesky. Leider bin ich jedoch nicht der Held, wenn es um Bildbeschreibungen geht. Zumindest wurde mir das so mitgeteilt. Sehr problematisch wird das Ganze, wenn es schnell gehen muss, weil man von unterwegs mal eben kurz ein Bild teilen möchte. Post mit Bildern ohne Beschreibung sind allerdings zurecht nicht gerne...
Updating an open source library taught me a valuable lesson for making your codebase agent-friendly — small steps can have a big payoff.
If you save a URL to Apple Reminders — via the Share Sheet or Siri — it goes into the reminder's URL field. This sounds fine until you try to do
Siri doesn't just need a makeover, it needs a new vision for automation. And that's a job Skills can help with.
I spoke at NSSpain this year and gave a wide-ranging talk AI, building from the fundamentals to real-world uses — with something for everyone.
Leo Dion and I discuss building Plinky from scratch, the technical decisions behind using SwiftUI and Vapor, creating delightful user experiences, and the journey from working at Twitter to becoming an indie developer.
Introducing Monarch, a simple yet flexible migrations library for Swift that helps manage user data changes across app updates with minimal hassle.
Open sourcing Recap, a Swift library for creating beautiful What's New screens to highlight app updates and keep users informed about new features.
Plinky was featured in Indie App Spotlight Issue 20, where we discussed the app's origin story, design philosophy, technical implementation, and the journey of building a successful indie app.
Peter Witham and I discuss the incredible experience of having Plinky featured on the App Store, the journey of indie app development, and how doing good work creates opportunities.
The story behind Plinky, my personal app for saving and organizing links that makes it incredibly easy to save links for later.
I joined the Github DevRel team to discuss building Boutique, my "magical" library for data persistence. We also dive into my journey from Twitter to indie development, and the harsher realities of open source maintainership.
Personal reflections on building Boutique and Bodega open source projects, covering the ups and downs of creating something valuable for the Swift community.
Introducing Boutique, a new architecture that reimagines MVC for SwiftUI by adding a Store layer to handle state management and data flow in a familiar, approachable way.
Building maintainable, flexible color palette systems for iOS and macOS apps using asset catalogs, semantic naming, and SwiftUI integration.
Learning how to make GraphQL requests from scratch without libraries like Apollo, exploring the fundamentals of GraphQL client-side implementation in Swift.
Leo Dion and I discuss scaling app development to thousands of people and millions of users at Twitter, communication, documentation, and the complexity of holding moral frameworks at a global level.
Exploring API design patterns for balancing implementation exposure, using the example of creating view controllers with header views in four different approaches.
Introducing ViewData, a declarative architecture pattern for transforming models into views that offers a maintainable alternative to MVVM for iOS development.
Continuing the ViewData architecture discussion, covering complex views, performance considerations, and practical implementation strategies.
Like everyone, I was shocked by Apple’s surprise reveal of SwiftUI at WWDC last week. We’ve heard rumors of some kind of declarative, multi-platform framework coming sometime in the future, but I don’t think anyone expected we’d see it so soon. This seems like a huge change, a beginning of a completely new chapter for app developers on Apple platforms. I’ve watched most of the session videos about SwiftUI and I’m incredibly excited and eager to start using it in practice. Here are some first impressions and thoughts about SwiftUI after reading about it and playing with it for a few days: Difficulty: Prepare to feel like you’ve just started learning Mac/iOS programming… This is a completely new thing which works in a completely new way, and it’s hard to switch your brain to a new mode. You will be thinking “How the hell do I do X” every step of the way. And it’s ok, because even ignoring the paradigm change, this is just a completely new API, we don’t know the names of all the classes and methods by heart and it will take time before we’re somewhat familiar with them. We’ll need to figure this thing out together - over the next months there will be thousands of blog posts, tutorials, books, screencasts and conference talks. People sharing tips, techniques and best practices. This will make it much easier to learn how to use these new APIs and how to do it well. (Some crazy people have already started last week!) Things I’ve had the most trouble with so far: layout, whenever it goes beyond the simple horizontal or vertical flow - how to put this thing in that place or make sure it has such size - things that would be trivial with AutoLayout, here I often don’t even know where to start bindings - which kind of property to use and how, where to use the ‘$’, how to make sure the UI gets notified of a given change (or even how to get the thing to compile at all) arrangement of modifiers - in what order I should put them if I want to apply several different effects Project state: This is definitely a beta thing at the moment. Some things just don’t work yet, the compiler is often extremely unhelpful, showing very cryptic error messages or showing them in a wrong place, and the reference documentation is incomplete. Autocomplete only works about half of the time. This will hopefully get better by September, although I suspect it won’t be completely perfect by then. Also not every feature from the native frameworks that we might need is exposed in the new API, and that’s kind of by design - that’s why we have NSViewRepresentable and UIViewRepresentable. Hopefully more and more shared and platform-specific things will get added in future versions (and hopefully we won’t have to wait until June 2020 to see anything new). Potential: We’ll only know for sure once we start using SwiftUI in real, full size apps, but judging by what we’ve heard so far, the potential for saving us work, speeding up development and eliminating bugs is huge. I can’t wait…
Join me on The Learn Swift Podcast where Steven Sherry and I discuss contracting, computing history, philosophy, Smalltalk, and even a little bit about Swift.
An interview with Sam Jarman covering my career journey, the NYC tech scene, consulting vs full-time work, and advice for building a successful software career.