Oleksii Kolomiiets
@kolomiets123.bsky.social
📱iOS Engineer @snappmobile.bsky.social passionate about SwiftUI, clean code, and user-centric design | SnappMobile iOS Newsletter
Awesome. Thank you for heads up and Apple for doing their job 😃
November 24, 2025 at 5:19 PM
Awesome. Thank you for heads up and Apple for doing their job 😃
The „bug” was only in visible part, because when button is disabled, it shouldn’t interact. I haven’t checked it with recent versions. Maybe it’s already fixed.
November 23, 2025 at 8:47 PM
The „bug” was only in visible part, because when button is disabled, it shouldn’t interact. I haven’t checked it with recent versions. Maybe it’s already fixed.
Personally? I'd prefer not to see those deps. Example apps should only use the SDK they're created for, staying within the platform versions your SDK supports. Keeps things clean. 📦
November 12, 2025 at 8:35 AM
Personally? I'd prefer not to see those deps. Example apps should only use the SDK they're created for, staying within the platform versions your SDK supports. Keeps things clean. 📦
But here's what got me thinking: any dependencies the example app needs must be in the package configuration, which means they show up when users add your SDK as a dependency. Users get frameworks they didn't ask for - only because the example app needed them.
November 12, 2025 at 8:35 AM
But here's what got me thinking: any dependencies the example app needs must be in the package configuration, which means they show up when users add your SDK as a dependency. Users get frameworks they didn't ask for - only because the example app needed them.
See you there 👋
October 20, 2025 at 4:53 PM
See you there 👋
