Latest version of my app, Discretion, has been released.
It provides privacy first photo sharing for iPhone, iPad and Mac. Give it a go.
RTs appreciated 🙏
#BuildInPublic
https://t.co/C16k39ZlbW
Apple Intelligence for Masterminds is only available for pre-order and is already a bestseller in the Apple Development & Programming category on Amazon! Thank you guys for all the support! https://t.co/h7R0ydVL5Y #ai#neuralnetworks#appleintelligence
Whenever I see someone ship a massively complex or cool feature / project my first thought is "Damn! How'd they know how to do that? That's so smart!".
And then I remember that the road to get there was most likely messier and harder than it looks.
Don't compare yourself to other's outcomes; they most likely worked really hard to get where they are.
Honestly, the biggest Swift Concurrency trap you can set for yourself is thinking that you need to know _everything_.
Most apps don't need a ton of concurrency. They don't need to use the more complex and powerful features.
Most of the apps I've worked on fetch some data from the network and present that data in a list. No expensive processing, no heavy tasks that run in a background thread.
Don't overcomplicate things unless you have to. Measure performance with Instruments, don't offload to the background "just in case".
Swift 6.2's default settings reinforce this which IMO is a good thing. It helps you get started with a simple setup and allows you to make things more complex if and when needed. That's how code should be written.
If your first thought is to make everything concurrent and async for every project you work on I can promise you, you're making things harder for yourself and you really don't have to.
With Xcode 26 your projects will automatically include a setting that runs code on the main actor by default, making your decision to introduce concurrency more conscious and explicit.
To configure this setting for existing projects (or to opt out in your new projects), you can set default actor isolation in build settings:
I've been tracking pomodoros with Chrona. An app I made to log, summarize, and rate my productivity. It's been a huge boost, especially since I'm able to visualize how well I'm doing with my work. It's pretty cool 😁
https://t.co/fsC5IbiYh8
📖 New blog post available!😱
Are you ever worried about overusing actors in Swift? Or are you worried about introducing more concurrency with actors?
Mutex might just be what you're looking for: https://t.co/MouzRZArO7
My first Product Hunt release tomorrow! Any support appreciated 🙏.
Let me know your Product Hunt Profiles so I can follow you.
Discretion: Privacy toolkit for sharing photos
for iPhone, iPad and Mac
https://t.co/gTmS8w5660
My first Product Hunt release tomorrow! Any support appreciated 🙏.
Let me know your Product Hunt Profiles so I can follow you.
Discretion: Privacy toolkit for sharing photos
for iPhone, iPad and Mac
https://t.co/gTmS8w5660
I think it's about time I ship my first app of the year this week...
Track pomodoros, write down what you did, and review your productivity in graphs. It's a simple idea, but it's been working _really_ well for me these past few weeks. 😁
Just a few more small things to fix before I'm ready
I’ve released an update for Discretion today. It now enables you to create Genmoji face masks on iOS devices with Apple Intelligence support. There’s also a Feature Roadmap which allows you to vote for your favorite proposed features.
#BuildInPublic#iOSDev#indieDev