Did you know?
Commit Photos uses on-device processing only - your library never leaves your Mac. Fast, private, and secure.
Did you know?
Commit Photos uses on-device processing only - your library never leaves your Mac. Fast, private, and secure.
Apple sent out an email telling devs to update their app metadata for new age rating requirements. I can’t see anything that can be changed, at least not without submitting a new build.
They specifically mention doing this now to save time before you submit new builds.
Do they ever make any of this easier?
I would already have released Cartographer if I could settle on monetization.
I'm painfully aware of how hard it is to get traction for anything more than free. It won't be free.
I'm not the only #indieDev who goes thru this. I believe many apps just aren't built because devs can't make anything close to a living wage from them. On the other hand the stores are filled with vibe coded, copycat crap.
Free/Freemium pricing has killed so much of the app ecosystem.
Some of the most annoying issues are the things that don't work reliably for you but you're 98% certain they're developer problems and are likely to be fine on user devices.
For example I'm having troubles with a MapView showing the actual user location. Works sometimes. Works better with a simulated location while debugging. Doesn't always display when the app is run outside #Xcode
Here is a fun one:
if you have a #SwiftUI customizable toolbar and an optional inspector view, when the inspector becomes visible any optional toolbar items being shown will disappear.
I’m looking to store sensitive data, such as API keys or user tokens, in a secure manner. Naturally, I assumed the Keychain would be the right place for this. However, I’d prefer that these items not appear in the Keychain Access app.
Would setting kSecAttrIsInvisible be the correct approach, or is there a better alternative?
#macosdev #indiedev #iosdev #swift
macOS Tahoe will be the last new macOS release to support any Intel Macs. All new releases starting with macOS 27 will require an Apple Silicon Mac.
Excited to announce v0.4.0 of our offline dictation tool! This is "The Cross-Platform & Modernization Update".
Highlights: Full, native macOS support
Massive stability & reliability overhaul
Intelligent RAM management
Easier setup
Your private, open-source assistant for Windows, Linux, and now Mac!
Release Notes & Download:
https://github.com/sl5net/Vosk-System-Listener/releases/tag/v0.4.0
Let’s say I want to display > 100k items from #SwiftData in a Table view in #SwiftUI: is there a way to do that lazily so performance doesn’t become a nightmare? Or do I need to use AppKit’s NSTableView instead? #macOSDev #Swift
After 27 years, software engineer Doug Brown found a secret photo of the Apple Power Mac development staff, hidden within certain Mac G3 ROM chips.
New Testflight build for Cartographer, my GPX viewer/editor app for #MacOS.
Adds the ability to edit any route/path via drag and drop of waypoints.
Very close to shipping. I need to stop adding new features and just ship and iterate or I'll never finish. I'm using the app all the time and it works well.
After 27 years, software engineer Doug Brown found a secret photo of the Apple Power Mac development staff, hidden within certain Mac G3 ROM chips.
Good Artists Copy; Great Artists Steal. I can't believe I drew this icon.
Please don't sue me, Bono. ehh I mean unknown artists, I've never seen before.
#macosdev #indiedev #applemusic #buildinpublic
Account auto-completion has arrived in #Oliphaunt!
Start typing @ in the composer and you’ll get a native-style auto-completion window — right at the caret, just like in Xcode. No clunky bars or overlays — this is proper #Mac behaviour.
It’ll be available in the next build.
Is #Oliphaunt the first Mastodon client to do it like this?
If you're looking to see how long a piece of your #Swift code takes to execute (and you can’t/don't want to bother with Instruments) look at ContinuousClock.
It can be used like this:
let clock = ContinuousClock()
let elapsed = clock.measure {
<the code to evaluate…>
}
print(“That took: \(elapsed))
Handy for caveman optimizations.
Docs are limited but here:
https://developer.apple.com/documentation/swift/continuousclock/
#SwiftUI is great at making it easy to update your views when data changes. This can lead to costly view redraws if your view is complex. A redraw may cause the app to feel slugish.
I did some refactoring on my Cartographer app today to speed up my NSViewRepresentable MapView rendering to save over a second in redraw time.
I was taking 1.5+ seconds to display a dialog after a point was selected. It's now 300-500 milliseconds and that feels ok.
Is it only me or is a typical NavigationStack on macOS really that bad? It just accumulates more and more memory, which is really bad for an app that could endlessly go deep into a navigation structure.
I moved now to a custom Navigation Stack that basically recreated the screens by a representation of an Enum and so far I can keep my app pretty low on memory.
#swiftui #macosdev #swift #indiedev