Abra B.V.’s Post

Most developers sleep on macOS Accessibility APIs. That's a mistake — they're one of the most powerful and underused tools on the platform. I built a small app to explore how they work, especially with Safari and iOS Simulator. Watch it dissect live UI trees, log real-time accessibility events, and even trigger actions like AXPress on any element in any running app. Code is open source. Dig in: https://lnkd.in/gXY6mFyU

Xterium Update is LIVE! (v2.6.0) May 4, 2026 The latest version of Xterium is now available on Android & iOS — bringing better performance and smarter features to your experience. What’s New: - Google Drive Backup & Restore now available for Android users - iCloud backup & Restore for iOS is currently in development - Improved transfer handling with transfer_allow_death when Transfer Keep-Alive is disabled

You've needed UIKit just to add an A-Z index strip to a SwiftUI list. iOS 26 ends that. sectionIndexLabel attaches to any Section inside a List and registers a single-character label for the trailing scrubber — the familiar Contacts-app navigation strip. Users tap or swipe it to jump directly to that section. Add listSectionIndexVisibility with the visible option to the List itself to activate it. Two modifiers, no delegate, no bridge. Before iOS 26, getting this into a SwiftUI app meant wrapping UITableView in UIViewRepresentable, implementing sectionIndexTitles on the delegate, and wiring scroll callbacks manually. Now it works natively, with automatic scrolling, proper haptics, and full Dark Mode support. If your app has more than a handful of alphabetically grouped sections, this is the right time to add it. #SwiftUI #iOSDev #SwiftLang #iOS26 #Swift #MobileUI #AppleDeveloper #iOSProgramming

BMindful is better on iOS. Built for busy professionals who end the day with a full head and want a private way to check in, spot patterns, and choose one practical next step. Clearer signals. Better follow-through. https://lnkd.in/eFA5ZEuV

Unpopular opinion: Compose Multiplatform sharing UI between Android, iOS, and desktop is overrated. Here's what actually works. By focusing on the basics and using standard libraries, you can create efficient shareable UI components. Here’s a streamlined way using Compose’s Modifier: ``` fun Modifier.customAlignment

I’m building a macOS desktop application in Swift and planning to distribute it directly from my website (not through the Mac App Store). My setup: App is signed and notarized by Apple Users download the DMG from my official website The app includes a 3-day free trial After the trial expires, users must enter a license key to continue using the app I do not want to build my own payment system or backend I only need license key generation and verification Which platform would you recommend for this use case? I’m considering options like Gumroad, Paddle, and Lemon Squeezy. My priorities are: Automatic license key generation Simple API for license validation in Swift One-time payments Minimal setup Good support for indie developers What platform are you using for your macOS apps, and which one would you recommend?

Every broken link is a tiny betrayal of trust. A frustration every user already knows. So instead of building a "feature showcase," I designed the piece around friction itself. Wrong screens. Broken redirects. Dead ends. The goal: make the problem instantly recognisable — before the solution even shows up. Because the hardest part of motion design for SaaS isn't smooth UI animation. It's clarity in under 30 seconds. Every transition, pacing decision and typography cue to one idea: One link. The right path. Every time. I wanted the motion language to feel like the product — fast, certain, routing in real time. Congrats to Falconiere Barbosa on shipping Routo solo, and thanks for trusting me with the story. See it live → https://routo.io #MotionDesign #SaaS #BrandStorytelling #ProductLaunch #BuildInPublic

Test and debug on 30+ iOS and Android devices, right from your browser. Run your actual built binary on a virtual device inside Primio. No Xcode. No Android Studio. Nothing on your machine. When something breaks, you see exactly why. We stream the device's live logs right next to the app as it runs. One click copies them. Paste them back into your prompt, and Primio reads the actual error and fixes it. Test. Debug. Fix. Without leaving the tab. Simulate biometrics, rotation, system keys, camera media. Live log stream on by default. Run it before you ship.

We got featured in ITBriefUS 🙌 They covered our new radar freshness indicators - now live on iOS & Android. See exactly how old the radar data is at any point on the map. Because "LIVE" doesn't always mean what you think it does. Be one of the first to try it 👇 https://lnkd.in/d7BMefUt

Something that caught me off guard while implementing QR-code navigation in SwiftUI. I had deep linking working perfectly, custom URLs resolving, navigation flowing, everything smooth. Then I added QR codes and suddenly nothing worked. Turns out I was only handling half the picture. There are actually two separate systems at play in iOS: Custom URL Schemes (myapp://) are handled by .onOpenURL and are great for OAuth callbacks, app-to-app communication, and SDK integrations. Most tutorials stop here. Universal Links (https://myapp.com) are handled by .onContinueUserActivity and cover QR codes, Safari, emails, Messages, push notifications, basically everything user-facing that originates from the web. The fix was straightforward once I understood the distinction: use both handlers and route them through the same logic. The bigger realization? Universal Links are almost always the better choice for anything users actually interact with because they gracefully fall back to your website when the app isn't installed. Custom schemes just... fail silently. If you've ever wondered why your deep links work in some contexts but not others, this is probably why. Worth knowing before you ship your next QR code feature. #iOS #SwiftUI #Swift #DeepLinking #UniversalLinks #iOSDevelopment #MobileDev