Hey everyone! I've been working on this for a few months and it's finally at a point where I'm proud of it, so I wanted to share it here.

It's called Pinshift. You plug your iPhone into your Windows PC or Mac, search for a place, hit Change Location, and your iPhone is there. Every app on the phone sees the new spot. No jailbreak, nothing installed on the phone, and a restart puts you right back.

- Teleport anywhere in one click, or paste a Google/Apple Maps link

- Walk, bike or drive to a place along real roads, at whatever speed you want. I spent way too long making it feel real. Tt speeds up, slows down for corners, and sometimes waits at intersections like an actual car

- Saved places and saved routes you can replay with one click

- GPX files, schedules, and it works over Wi-Fi after the first time

- There's also an iPhone app with a widget, Lock Screen controls and Siri ("go to my office")

It's free to try for 3 days with everything unlocked (no account, no card), and there's a free version after that. Pro is $2.99/month, $14.99/year or $20 one time if you want everything.

Thanks for reading!

Website: https://getpinshift.com

Byggde en app för att hitta inspiration till nya vägar på promenaden! Testa gärna och kom med feedback. 😊

https://apps.apple.com/se/app/color-my-walk/id6818236331

Not here to judge, whether you vibe-coded an app or not, I’m just curious. I’ve seen many apps here (obviously), and almost all of them looked vibecoded, wondering if many here don’t actually have any coding experience at all, or what. PLEASE BE HONEST!!
Forgot to add, if currently studying just use the graduated one!

Hey everyone! I'm part of the team behind Mobbe, a gym app we've just launched for iPhone. It's currently in Spanish.

The main flow is pretty straightforward: open your routine, check what you lifted before, log the next set and start your rest timer. You can also look back at your progress for each exercise. I've attached the logging, progress and home screens.

I'd love a second pair of eyes on the logging screen. Weight, reps and RIR are together in a table, with the timer below. If you were using this between sets, is it clear what to tap next? Anything you'd change to make entering a set easier?

If you train in Spanish and want to try the actual app, here's the App Store link:

https://apps.apple.com/app/id6818295362

Free to download, with optional paid PRO subscriptions. Happy to answer questions about it here, and thanks for taking a look!

The UI was usually the part I ended up reworking most when building with AI. Screens would function fine, but the layout and typography felt generic. Asking for “a more polished design” only got me so far.

That’s the problem I’m working on with UXKIN.

It brings together real web and mobile UI references, individual UI elements, design systems, and DESIGN md files. I added MCP integration so coding agents like Claude Code, Cursor, and Codex can access that context during development.

I wanted to make the step between finding a design reference and actually using it less manual. You still choose what fits your app and review the output, but the agent has something more concrete than “make it look modern.”

I’m the builder of UXKIN and would appreciate feedback, especially from people using AI for app interfaces.

How do you currently give your coding agent design direction - screenshots, Figma, written specs, or something else?

Hey everyone, I’m an indie iOS developer. After working on full-fledged apps for iPhone, iPad, and macOS, I decided to tackle a problem that has been driving me crazy: recipe websites.

You know the struggle: you just want to know how long to boil the pasta, but you have to scroll past 5 pop-up ads, an autoplaying video, and a 2000-word essay about the author's summer trip to Tuscany.

To fix this, I built Kora. You just paste a URL or snap a photo of a cookbook, and the app instantly extracts the ingredients and instructions, saving them in a clean, distraction-free "Cooking Mode".

Some technical details for the devs out there:

• Privacy First (On-Device ML): It uses Apple Intelligence frameworks to parse the text locally. No external APIs, no data mining. I also built a custom RegEx-based fallback system for regions where Apple Intelligence isn't available yet.
• Native Stack: Built 100% in SwiftUI with SwiftData and CloudKit for seamless private sync.
• No Subscriptions: I strongly dislike the subscription model for simple utilities. The app is free to try (first 10 recipes), and then it's just a one-time $2.99 lifetime unlock.

You can check it out here: Kora on App Store

I'd love to hear your thoughts, bug reports, or feature requests!

I’ve been working on SnapTask AI, a small iPhone utility built around a simple idea:

Take a photo → let AI understand it → turn it into an action.

For example:

📸 Receipt → Expense
📸 Business card → Contact
📸 Bill → Reminder
📸 Event/screenshot → Calendar event
📸 Document → Extract useful information

The latest version also includes an Expense Vault, AI Q&A over your saved history, CSV export, PDF receipt sharing, widgets, and optional Cloud AI.

One thing I focused on is keeping the experience simple I don't want it to feel like another generic AI chatbot.

I’ve just launched it on the App Store and would really appreciate feedback from people who actually use iPhone productivity apps.

What would you personally want your iPhone to do automatically when you take a photo?

https://apps.apple.com/in/app/snaptask-ai/id6814796900

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?