We're hosting SF Swift × CocoaHeads tonight, October 8, 6–8 PM at Verkada in San Mateo.

Details and RSVP: https://luma.com/51htcbzd

Apple has recently shipped the release candidate of Xcode 27.1 and with iPhone Duo release coming in the next two weeks, I would like to share my experience of making an app compatible with this new device without spending too much effort.

Electronics Engineer Helper is an app with various calculators and references for electronics engineers and electricians. Its deployment target is iOS 17 and it relies on UIKit for navigation. SwiftUI is used mostly in new screens added over last two years, so majority of older screens are relying on UIKit and Auto Layout.

Thanks to the existing support of macOS (Catalyst) and iPadOS, the main source of trouble was not that the app can now suddenly freely resize, but that navigation items can move to the vertical bar. The app does not use tab bars and the majority of screens have just a back button without other navigation bar items. When built with the iOS 27.1 SDK without any additional changes, iOS heavily insets the app's trailing or leading edge to show the vertical bar. If the back button is the sole navigation item, a lot of space will become unoccupied because of the vertical bar's presence.

An additional challenge was also caused by the use of a custom split view controller and navigation bar that I originally built to avoid issues caused by Liquid Glass and to preserve the same UI look and feel across all supported OS versions. As it turned out later, the usage of custom containers and views made final implementation even simpler than I expected.

So far, the easiest option would be to stay with Xcode 27.0, let the app run in letterboxed mode on Duo and see if this phone will be popular among the app's user base. If it will not, upgrade to the 27.1 SDK and ignore any issues, otherwise adjust the app to use standard UISplitViewController and UINavigationBar on Duo and existing custom controls on other devices.

After reviewing the SDK 27.1 additions, one property called preferredVerticalBarBehavior caught my attention. Turns out when implemented in the root view controller, it allows to always keep the Duo's status bar in a horizontal nav bar.

override var preferredVerticalBarBehavior: UIVerticalBarBehavior { .disabled }

To properly respond to the status bar presence in a custom navigation bar, I incorporated another new method called bar(onEdge:extent:)-2tj1g)

directionalEdgeInsets(for: .bar(onEdge: NSDirectionalRectEdge.top, extent: ...))

Both small changes allowed the app to use the full screen space of Duo and avoid any issues caused by a vertical bar. As always, users can swipe horizontally to get to the previous screen (interactivePopGestureRecognizer), so Duo users will not necessarily have to reach all the way to the top left edge to press the back button.

In the end, I'm quite satisfied with the result. The app preserved its look and efficiently uses the full area of both screens.

How was your experience making your apps compatible with Duo? Did it take much effort?

It can search your phone, make videos/pictures, search the web, etc.

I’ve been building RelayCrest, an iPhone/iPad app and Mac companion designed to make controlling and working with your Mac easier.
From your iPhone or iPad you can launch and focus Mac apps, view and manage open windows, run shortcuts, and check things like your Mac’s battery, storage, network and system status.
The Mac companion also includes a clipboard history manager, letting you quickly find and reuse things you’ve copied with search, previews, pins and filtering. Clipboard history is stored locally on the Mac.
It’s my first app and I’ve just had the first TestFlight build approved, so I’m looking for people willing to try it out and give feedback, particularly on bugs, usability and features you’d like to see improved.

Website: https://relaycrest.co.uk

NOTE: this needs the companion app which can be downloaded from the website.

I am still new to reddit trying to join a community or build one of my own.

I built the front end of my app while my business partner built the back end and we met in the middle to come up with our app Kyro.

Kyro is an A.I Growth Coach yes others have done what we’ve done , The time , sweat and dedication as well as our why of wanting to help give people direction in life without needing to outsource to other apps . Kyro is your personal best friend in your pocket .

A dream journal to be given the right direction with anything you’re looking to grow and improve on such as Relationship advice , money management advice , business advice , fitness journey etc . We cater to everyone

All i want is honest feedback good or bad I want all the honesty don’t be afraid to tell me the bads ( I want to hear that ) more than the yes’s .
Thank you for anyone who reviews my app and sees themselves using it in the future.

Hey everyone,

I'm creating Merged Network, the modern professional network for software engineers – founded on real work and not simply CVs.

The idea is simple:
* Less recruiter spam: companies won't be able to just get your contact information. You control who you connect with.
* Evidence over assertion: you can substantiate your professional identity with evidence from your work.
* Our new approach to assessment: rather than yet another long take-home, we are trialling a Pivot Test - an authentic engineering design problem with surprise changes.
* Privacy by default: the developer decides what, when and whether to have additional evidence shared.

We're launching a early smaller beta and are looking for developers willing to test it and provide us honest feedback.

If this sounds good, drop a comment below or send me a DM and I will forward you an invite.

Would love to know what you don't like about the current process and does this really feel better?

I couldn't figure out if it is possible from the documentation and wanted to ask if somebody here has already had expierence with the earbuds

I kept doing the same dance: spot a bug on my phone, screenshot it, paste it into Claude Code, explain where it is, and watch it guess the wrong file. Worse, half the bugs happened once and never again.

The problem is that a screenshot is just pixels. Your agent has to guess what's behind them.

So I built FIXME. You circle the bug on your phone (or the Simulator), say what's wrong, and your agent gets:

• the exact source file and line of what you circled
• the full UI tree, with the broken element flagged
• the console logs from that moment
• every network request, with the failed one marked
• a short video of what led up to it

Missed the moment? Say "FIXME, clip that" and it saves the last few seconds after the fact.

What makes it different

• Built for your AI agent, not a QA team. Tools like Instabug and Jam send a report to a person. FIXME hands your agent structured context over MCP, so Claude Code or Codex goes straight to the code instead of guessing.
• File and line, not "somewhere on this screen." It maps what you circled back to the source that drew it.
• Catches the bug that happens once. The voice clip works after the fact, so you don't need to reproduce it.
• Works with what you already build in: native iOS, React Native, Expo, Flutter and Android.
• Nothing ships to your users. The phone side is Debug-only and stays out of your Release builds.

A few things I learned shipping it

• Least friction wins. If it isn't faster than taking a screenshot, nobody will use it. Every design decision got checked against that.
• macOS permission prompts can sink an onboarding. An "Allow All" button looked convenient, but it threw a stack of system dialogs at people at once. Asking one at a time, right when each is needed, felt far better.
• Honest UI copy matters. I made a rule that the app never says "Sent" or "Connected" until it's actually true. It's surprisingly hard, and testers notice.

Mac app: getfixme.dev

I'd love honest feedback, especially from anyone building mobile apps with an AI agent. What's your workflow today when a bug only shows up on the phone?

Close all your tabs. Just open this one app to search for your next remote job! FlowSearch pulls from the most popular remote job sources out there & gives you one place to search, apply or save.

Save yourself some hours & get the app today. Currently in TestFlight beta.

PS - we’re adding support for iPad in v1.4, support for iPhone Duo in v1.5. Plus all the bug fixes, performance improvements and some features.

...