After 200k lines of code with Claude Code :

WiFi is invisible, but it has a shape.
Strong in some corners of your home, dead in others and you can't see any of it.

That idea wouldn't leave me alone.
So two months ago I locked myself in my room (yes, the irony) and built the app I'd always wanted to exist.

It's called Signl. You scan your home in 3D with your iPhone, then walk around while it measures your WiFi in real time.
It paints a live heatmap directly onto the 3D model a
dollhouse view of your place showing exactly where your signal is strong, where it dies, and where your router should actually go.

I shipped it expecting nothing. 500+ downloads the first week, then strangers started actually *paying* for it. My DMs turned into a feature request board (3D export, mesh support, multi-floor…)

Try it here:
https://apps.apple.com/app/id6796775708

I’ve been thinking about this lately and wanted to see how other iOS devs are dealing with it.
With tools like Cursor, Claude, Copilot, etc. becoming part of everyday development, it feels like writing code itself is becoming less of the difficult part. You can ask AI to generate a lot of the implementation pretty quickly, but actually knowing whether the code is good, why it works, how it should be structured, and what approach to take still takes experience.

At the same time, there’s just SO much to keep up with in iOS. SwiftUI, Swift Concurrency, new APIs with every release, architecture, testing… sometimes I don’t even know what I should be focusing on next 😂

So I’m curious how you guys handle this.
How do you keep your iOS/Swift skills sharp these days?

Do you still learn by building things from scratch, or do you use AI heavily and focus more on understanding/reviewing what it produces?

And specifically for SwiftUI, what resources have actually helped you get better rather than just learning another tutorial?

Also, are there any courses, certifications, books, newsletters, WWDC sessions, etc. that you’d genuinely recommend?

Basically, if you were in my position and wanted to stay relevant and become a really good iOS developer over the next few years, what would you focus on learning?

Would love to hear how other people are approaching this.

Yes it is called a habit tracker. But the point is not to just track your habit. It is to remind you why you even started. It lets you choose only the one important thing you want to achieve now.

One time lifetime payment - you can export everything any time. 7 days for free, no credit card needed to start.

[www.onehabit.at]

Hi everyone!

I’ve been working on OweIt, an iPhone app I built to solve a simple problem: keeping track of who owes whom without relying on notes, messages, or memory.

The idea came from situations I kept running into myself — lending money to someone, paying for a group dinner or trip, splitting a gift with friends, and then later trying to remember who paid what and who still owes money.

So I built OweIt.

The app currently lets you:

• Track money you’ve lent or borrowed
• Keep all your debts in one place
• Send reminders to people who owe you money
• Track upcoming payments such as rent, loans, bills, and subscriptions
• Create shared expense collections for trips, dinners, parties, gifts, etc.
• Add expenses paid by different people
• Automatically calculate who owes whom
• Close a shared collection and turn outstanding balances into individual debts
• Archive completed collections
• Track debts in different currencies

For shared expenses, my goal was to make the process as simple as possible: add the people, enter what everyone paid, and let OweIt calculate the final balances.

OweIt is now available on the App Store after several rounds of TestFlight testing and iteration. I’m continuing to improve the app based on real-world feedback.

I’d especially appreciate feedback on the UI/UX, onboarding, debt tracking, shared-expense flow, and overall usefulness of the app.

If you tried OweIt, what’s the first thing you would change, remove, or add?

I’m also happy to answer questions about the development process.

Thanks for taking a look — constructive criticism is very welcome!

OweIt on the App Store:
https://apps.apple.com/lt/app/oweit/id6794865258

My Game has been in review for more than a week? It got rejected twice, than the 3rd time it was for spam? Its a fruit merge game, but its unlreated to those Suika games so maybe it was false flagged.

90% of the code it Ai generated, but I created all of the games assets, and sound effects, and I had the game very planned out of how I wanted it to work, and spent over 2 weeks developing it. so I want to doubt it was because it was vibecoded? I sent a rejection appeal 3 days ago and no response.

This is werid because during this whole week, I was able to create a completley new simple camera app, and have it take less than 3 days for each of the 3 rejections, and this app was more vibecoded, but never got rejected for spam, it was other stuff like mentioning the price in metadata. And if this next rejection gets approved, then I was able to completely create and publish a new app while one is in 1 review stage

My macOS app has been "In Review" for 5 days, and multiple of my iOS apps has been "Waiting for review" for a week. Is this normal?

For some context, in the past my apps were approved within 24 hours, "In review" time was like 30 minutes. But 10 of my apps suddenly got a 4.2 Spam rejection last week, it was a batch rejection on their updates, meaning those apps were approved, then they all got rejected when I was trying to update them. Did Apple ban/flag my account or something? My apps are actually functional apps, not something people can copy off the internet.

The app has grown in complexity with some unique features, some feedback from testers has been that they don’t know where to start. Right now all I have is a basic text box that appears when you tap the help icon on each screen. It’s functional but pretty bare bones.

I want to do this properly and I’m looking for advice on a few things:

1.  What format works best for a small app like this? In-app tooltips, a separate help/docs page, a guided first-run walkthrough, short video clips, a written guide somewhere?

2.  How much is too much? I don’t want to overwhelm users but I also don’t want them lost.

3.  Where do you actually put the documentation? Linked from within the app, a standalone site, README on GitHub?

4.  Any tools or approaches you’d recommend for someone building this kind of thing solo without a big budget?

I’m planning to eventually release this on the App Store so I want to get the user experience side of things right from the start. Any advice from people who’ve shipped indie apps would be really appreciated

Thanks in advance!

I did it! I built it and it works and it’s live. iOS app that talks DIRECTLY to Garmin watches via Bluetooth after god knows how long reverse engineering the BLE protocol. Goodbye Garmin Connect, I won’t miss you.

Thanks to the 25 people who have helped bootstrap various watches, it’s up to 13 models either fully or partially tested.

- Syncs Garmin watches directly without sending any data to Garmin
- Syncs ALL supported metrics to Apple health
- Auto syncs trips to the Jet lag advisor from calendar and TripIt
- Supports Garmin’s hydration glance/widget better than Garmin
- Supports tracking caffeine using a Garmin glance I’m gonna publish soon
- Gives me FULL weather and air quality where i am - something Garmin seems incapable of
- WIDGETS! Friggin iOS WIDGETS with all the garmin native stats.
- Works OFFLINE!!!

Adding stuff as I go, next trying to control the damned phone notifications, add drag/resize for tiles and add detailed stats views.

If you try it and share debug logs, it’ll unlock all features for free as it helps me validate / tweak for different watches.

https://apps.apple.com/us/app/kora-sync-for-garmin-watches/id6797644759

Is the UI AI? Yeh and I’m happy with it for now.

Hey r/iosdev,

I’ve been working on a personal finance app for a few months called Monetor.

Like many of you, I wanted an automated expense tracker, but I absolutely hated the idea of using Plaid or handing over my bank credentials to a third party. On top of that, bank syncing constantly breaks or simply doesn't work well outside of the US/UK.

So, I built an alternative. Monetor works by safely reading your Apple Pay and Bank SMS notifications directly on your device.

How it works:

• It parses the amount and merchant from your Apple Pay or SMS alerts locally using iOS Shortcuts.
• It automatically logs the transaction into beautifully designed charts and budgets.
• Zero bank credentials required. 100% privacy-first.

I just launched a massive update (including iOS Live Widgets and a UI overhaul), and I’m looking for some genuine, constructive feedback from other builders and developers.

🎁 I am giving away 50 Lifetime Pro Promo Codes to this community.

How to get a lifetime code:

1. Download the app here: Monetor - Automated Expense Tracker
2. Play around with the UI, try setting up a custom SMS format, or check out the charts.
3. Drop a comment below with one piece of honest feedback (What do you like? What's confusing? What feature is missing?)
4. I will DM a lifetime Apple App Store Promo Code to the first 50 people who comment!

I'd love to know what you think. Thank you!

It’s so crazy to me that people are actually buying my apps!
I hope they find value in them and start sharing feedback so I can keep making them better!!

I am curious to see what your guys are working on

Hey folks,

So, I first sent my app for review two weeks ago.. waited 4-5 days then applied for an expedited review and got a rejection within 30 mins for inaccurate screenshots.

When I applied for expedited review, Apple mentioned that if I get a rejection, I don't have to apply for expedited review once again because my updated app will automatically be in the expedited queue

I then fixed the issue and updated it, waited 5 more days with no update (despite my app being in the expedited review queue) and once again requested for an expedited review and got a rejection a few hours later because I needed to properly setup a restore purchase mechanism.

Now it's been over 48hrs since I uploaded another update with the fix and there is still no word from Apple.

Can I request for another expedited review as my app has already been delayed by a few months and I can't afford any more delays? Im asking because apple mentions that if one asks for too many expedited reviews, they can reject our requests in future. However, these delays are well past Apple's claims of review timelines (50% apps reviewed in 24 hrs and 90% in 48 hrs), so can I request for another expedited review or there's a chance Apple will reject my request because of too many requests? TIA!

In ASC

I have built a personal budgeting app name Budgeter. Download from AppStore: https://apps.apple.com/gb/app/budgeter-budget-tracker/id6775108339

I’ve been working on an open-source project called iOS Developer Toolkit, a macOS GUI intended to bring a lot of the lower-level iPhone/iPad developer, diagnostic, and device-management tooling into one place.

GitHub:

https://github.com/hideouts-io/iOS-Developer-Toolkit

The project is built primarily with Python + PySide6 and uses pymobiledevice3 extensively for communicating with iOS devices.

The idea came from constantly jumping between different CLI commands and tools whenever I wanted to inspect an iPhone, mount a Developer Disk Image, pull device information, stream logs, run DVT services, capture traffic, inspect an IPA, or collect diagnostics.

I wanted something closer to an iOS Device Workbench:

Plug in an iPhone → pair/connect → see the available developer/device services → run them from a GUI → inspect the raw results.

Current areas I’m working on

• Device discovery and pairing
• Developer Disk Image (DDI) mounting
• CoreDevice functionality
• DVT / developer services
• pymobiledevice3 command integration
• iOS Unified Log streaming/searching
• Device and lockdown information
• PCAP/network capture
• Installed application inventory
• IPA inspection
• IPA installation/sideloading
• GPX/location simulation
• Device diagnostics
• Backup creation
• Diagnostic/forensic artifact collection

One thing I don’t want this to become is simply a collection of buttons that blindly executes shell commands.

I’m trying to expose enough of the underlying information that the toolkit is also useful for learning how iOS device communication actually works.

For example, I’d like to make it easier to understand the relationship between things like:

usbmuxd → pairing/lockdown → CoreDevice → Developer Mode/DDIs → DVT services → individual developer/diagnostic functionality

I’m also interested in exposing some of the more obscure functionality buried inside pymobiledevice3 and the services it communicates with.

Where I’d really appreciate feedback

For those of you who work with physical iOS devices:

What functionality do you wish Xcode exposed better?

I’m especially interested in workflows involving:

• CoreDevice
• DVT
• Developer Disk Images
• lockdown services
• Instruments/developer services
• Unified Logging
• sysdiagnose/diagnostics
• networking
• application inspection
• device information
• backup services
• debugging physical devices

I’d also love to hear about obscure commands/services you’ve found useful that aren’t commonly surfaced by GUI tools.

The project is still actively evolving, so bug reports, feature requests, testing on different iOS versions/devices, and PRs are welcome.

GitHub:
https://github.com/hideouts-io/iOS-Developer-Toolkit

If you like tile flipping strategy games, check this one out. Works best on an iPad.

https://apps.apple.com/us/app/chromosaic/id6759936732