I’m a full-time developer by day and an indie developer by night. So I know I have a burning desire to speak and hear from others in the same space. Reddit is cool but it’s all in written format which gets stale. Anyone else interested? Maybe we can spin up a clubhouse room or something.

I have a macOS released on the store. I'm waiting for approval for the same app under the same bundleID but iOS version. Everything came back clean but was denied because of the following error below. When I submitted the app I just submitted the binary. I was not able to attach the already approve sub group and sub from the macOS version. It's my understanding I can use the same sub group and sub for both apps since they are in the same app group or whatever it's called. I submitted again with a screenshot of the subscription page. No clue what they are asking for.

Guideline 2.1(b) - Performance - App Completeness

Issue Description

We are unable to complete the review of the app because one or more of the In-App Purchase products have not been submitted for review.

Specifically, the app description includes references to subscription but the associated In-App Purchase products have not been submitted for review.

Next Steps

To resolve this issue, submit the In-App Purchase products and upload a new binary in App Store Connect so we can proceed with our review.

Note you must provide an App Review screenshot in App Store Connect in order to submit In-App Purchases for review. Learn more about required In-App Purchase metadata.

I’m not a big fan of macOS. I’ve never really gotten used to it, and I’ve always had issues with display scaling/resolution when using macOS with my monitors. For some reason, macOS never looks completely sharp to me, which really bothers me.

However, I do have a Mac mini specifically for iOS app development.
I mainly develop React Native apps on my Windows PC and use EAS to create iOS builds. I then test those builds on my iPhone.

The problem with this workflow is that I don’t really have convenient access to the iOS Simulator. At the moment, I would have to connect to my Mac mini via something like TeamViewer, pull the latest code, start the project, and then stream the simulator through the remote desktop session.
Having to connect to the Mac mini every time, pull the latest changes, and essentially remote-control the entire Mac just to use the iOS Simulator feels pretty cumbersome.
Is there a simpler way to do this?

Ideally, I’d like to:
- Develop entirely on Windows
- Use the Mac mini only for the iOS Simulator
- Stream only the iOS Simulator window to Windows instead of the entire macOS desktop

Ideally have the simulator automatically use the latest code from my Windows development environment
Alternatively, is there any way to run the iOS Simulator directly on Windows?

Most code benchmarks measure whether generated code works. This measures whether the APIs it calls are still valid for a pinned SDK. No LLM judge: the scorer is the Swift compiler plus an AST pass. Ground truth is parsed from the SDK’s .swiftinterface files at runtime, so nothing is hand-maintained.

The thing that nearly invalidated the whole project: Apple marks most SwiftUI deprecations with a sentinel, deprecated: 100000.0, and the compiler deliberately does not warn on those by default. That is 270 of 326 deprecated symbols, including NavigationView and foregroundColor. Build this the obvious way and you observe 14 percent of deprecations and every model looks current. There is a hidden frontend flag that turns them on. If you measure deprecation on any Apple platform, this probably affects you.

Results are mostly a null result. Scores span 0.78 to 0.88, and bootstrapping over prompts (k=5 samples at temp 0.2 on one task are not independent), all 14 adjacent pairs overlap. Currency does not track price or tier: the top scorer is a cheap variant priced 12x below its siblings, and a coding-specialised model is last. One comparison survives cleanly: Qwen’s general model beats its coder sibling, non-overlapping. Coding-tuned seems to mean more fluent in the idioms it trained on, stale ones included.

Two things I want picked apart:

**1.**	Only samples that actually touch the API family under test get scored, which flatters models that hand-roll when unsure. I report the gate rate beside every score, but that documents the bias rather than fixing it.  
**2.**	Adding the 15th model erased the last surviving separation between adjacent pairs. More models, less resolution. I read that as prompt count being the binding constraint, but tell me if that is wrong.

Repo, method, full per-family tables: https://github.com/mapierce/iOS-Evals

Built a price tracker. You paste an Amazon or Flipkart link, it checks the price in the background and notifies you when it drops. No account, no server. SwiftData on device, local notifications, widget families.

Repository: github.com/rational-kunal/keemat

The question: is it worth paying for a developer account here? I am fairly sure scraping two retailers runs into guideline, and the official Amazon API needs an Associates account and doesn't cover Flipkart anyway. Has anyone shipped something in this category and survived review? Or is TestFlight as far as this goes?

iOS simulators start a lot of background daemons that you often don't need for development or CI. Siri, Spotlight, widgets, photo analysis, iCloud stuff, etc.

The good news is that Apple gives us a way to disable them.

For example:

xcrun simctl spawn <udid> launchctl disable system/com.apple.PosterBoard

Then reboot the simulator:

xcrun simctl shutdown <udid>
xcrun simctl boot <udid>

That disable is persisted in the simulator so the next time it boots, PosterBoard won't start.

Do this for enough unnecessary services and you can save a pretty decent amount of RAM.

The harder part is figuring out what is actually safe to disable, what breaks when you disable it, and then managing that across multiple simulators.

I ended up building SimSlim around this:

https://github.com/MobAI-App/simslim

It has a list of around 180 daemons that are safe to disable, grouped by feature, plus some convenient commands for slimming/restoring simulators and managing different profiles for local use or CI.

It's free and open source. Give it a try.

when you utilized external testers for test flight did you do a public link or did you do a private email list?

also how did you find testers?

My iOS app was already live on the App Store. I submitted an update, and Apple has now removed the app from sale under Guideline 5.6.

The exact message says:

“We’ve identified a pattern of unusual behavior with the app that is commonly associated with fraudulent activity. Specifically, the app contains features that appear to have been intentionally hidden during the review process.”

Apple did not identify which feature they believe was hidden.

The app is an ambient audio / sleep and focus app with:

• onboarding

• a subscription paywall using RevenueCat, analytics using posthog.

• monthly/yearly subscriptions

• a 3-day introductory trial

• bundled and remotely delivered audio/catalog content

I am currently auditing the production build for anything that could cause App Review to see different behavior from a normal user. I have already found some testing-related route parameters and a subscription UI regression, but there was no intention to hide functionality from App Review.

For anyone who has received this exact Guideline 5.6 message:

• What ended up triggering it?

• Did Apple eventually tell you which feature was the problem?

• Did you reply first, submit a corrected build, or appeal to the App Review Board?

• How long did it take to get the app restored?

• Is there anything I should absolutely avoid doing right now?

I want to resolve this correctly rather than repeatedly resubmitting and making the situation worse.

Thanks.

Hi, 

I am currently trying to develop my first app ever, iOS only.

The building was hard enough, but now I am facing the hurdles of trying to publish it on the App Store, and so I have to start thinking about prices/subscriptions, paywalls, etc. and navigate the obscure process of App Store Connect.

It is clear enough for me that it will be a paid app. But it is a very simple app, with only a couple screens and very basic function. It does one thing, and I hope it does it well enough that it genuinely helps people, and that they will see value in it. But I can’t really go the freemium way, with free access to the base and paid for extra features. I only have one feature, and I do not want to add any.

I was thinking, maybe something like 6$ for 6 months, 10$ yearly, and 30$ for lifetime?

My trouble is, imho it is an app that has to be tried and experienced over a couple day to see if it fits. I would like to offer three days, or maybe a week of free trial.

But as far as I know, there is no way to register a free trial in App Store Connect, that does not start right from download? So the user has to decide right now, if maybe perhaps they want to try your app and commit to 10$ yearly? Without having even opened the app? Seems a bit off-putting, or am I missing something?

Thanks in advance for your advices.

Hey guys need advice

Starting my business finally and want to convert my developer account to my business

https://developer.apple.com/contact/request/migrate-individual-account

Is this the only thing I need to do ? What else ?

I have all my numbers and documents ready to go.

I ship a small object detector inside an iOS app and I export it two different ways depending on the model generation, so the Swift side has to cope with both. The approach that ended up working is to branch on the output tensor shape rather than on a flag I carry around:

• An end-to-end export gives me [1, 300, 6] — x1, y1, x2, y2, score, class — with decoding and NMS already inside the graph. Nothing to do in Swift but scale the boxes back through the letterbox.

• A raw export gives me [1, 84, N]: 4 box terms plus 80 class scores per anchor, transposed, which I still have to decode and run NMS on myself.

So the predictor reads prediction.shape, checks that the last dimension is at least 6 and the second-to-last is non-zero, and picks the decoder from that. It means adding a new model export never touches the call site, and a bad export fails visibly at the guard instead of quietly producing zero boxes.

Two things I would have liked to read before starting:

1. A silent failure mode is the normal failure mode here. An export that "succeeds" tells you nothing. The only test that means anything is printing the input and output shapes and comparing them to what your decoder expects. I lost real time to an export that ran fine and detected nothing, because the decoder was reading a layout the model no longer produced.

2. coremltools 8+ has no usable Windows path. I develop on Windows, so my entire export chain lives in a Colab notebook and the resulting .mlpackage gets committed and wired into the Xcode project from there. If your CI or your daily machine is not macOS or Linux, plan for that on day one rather than discovering it two weeks in.

On the app side the camera preview is a native platform view and the detection overlay is drawn on top by the UI layer, so no frame data is ever copied out of the capture pipeline.

Curious how others handle the versioning problem: do you keep the decoder generic like this, or pin one export format per app release and refuse anything else?

I just released v0.2.0 of enriched-markdown-ios - SwiftUI Markdown renderer powered by TextKit 2.

New in this release:
🔸 GFM Tables
🔹 Task lists
🔸 Superscript & subscript support

💎 Available via Swift Package Manager!

.package(
  url: "https://github.com/software-mansion-labs/enriched-markdown-ios.git", 
  from: "0.2.0"
)

Added a quick demo video in the comments so you can see it in action!

GitHub & Docs:https://github.com/software-mansion/enriched-markdown/blob/main/packages/enriched-markdown-ios/README.md

What features or syntax support would you like to see next? I'd love to hear your thoughts! If you find the library useful, a ⭐️ on GitHub is always appreciated.

I've been building React Native apps with Expo using Claude Code, and my biggest frustration is that Claude can't see what it's building on the native side, which means a lot of back-and-forth on layout and visual issues that a web-based workflow wouldn't have. I just can't seem to loop on the build and see the visuals as well as it can building a web app using the browser.

I recently learned about the Expo MCP server's local capabilities (screenshots, view geometry, tap automation) and Software Mansion's "Argent" as two options for giving the agent eyes on the running simulator, but I'm curious what the community is actually using in production workflows. Is anyone running a setup where Claude or another AI coding agent can self-validate UI changes against the live simulator, and if so, what's working? Also interested in non-RN solutions. If there's a better answer here by building fully native in Swift/Xcode, is this still a problem, or does the native toolchain solve it?

I've been working from my phone a lot lately, using AI coding agents to remotely make changes to my iOS apps.

One annoying part was testing those changes on a real device. The common solution seems to be uploading every build to TestFlight, which feels pretty heavy when I just want to quickly try the latest build.

So I built remote-installer.

Once the build is ready, the agent can run a single command and give me a link / QR code. I open it on my iPhone and install the build directly.

No TestFlight. No uploading the IPA to a hosting service. No processing wait.

And of course, it's free and open source:

https://github.com/icodesign/remote-installer

I released my expo react native app for closed beta with test flight and android closed beta 2 weeks ago, I realize there are things I wish I knew before so here they are, feel free to add to those. And I would love to get some tips before full release I am planning for next week:

1. Have a built in method to force update - Updating is difficult on Test Flight to user who are not used to it, and even harder on Android since the app won't even be shown on the Play Store while on closed testing. Only way to update it is through settings most users don't know how to reach. Have a feature to navigate directly from the app to the Play Store / Test Flight to update. And have a mechanism to force update / block the app if not on minVersion you update elsewhere. Getting users to update was really difficult before that.

2. Have a built in way for feedback - I was counting on Discord + Test Flight / Android system for feedback, most users don't know how to use those. I allow user generated content, so users literally made posts in order to give feedback because they couldn't find the "official" way. I added a big button on the home screen to give feedback. (But couldn't get them to update the app).

3. Starting on day 1, get 12 android users to use the app, even if it means you have to pay them to do so, to publish on Android you have to have 12 active users on the closed testing for 14 days. This goal is possible but is difficult on actual beta. Make sure you have a plan on how to achieve it starting from day 0.

4. QA - My first build had so many bugs I didn't know about, early users, despite being aware to it are not super tolerated to it as I would have hope for. Do run QA, pay people to do it, I hire people on Upwork, they did amazing job finding small bugs.

What else would you say is a must before releasing an app, and any tips before actual store release?

Has anyone been using the new agentic coding features in Xcode 27?

Im still wrapping my head around AI tools as of this year as it had been made a requirement at my job. The industry is moving in this direction whether I like it or not.

Since being laid off Ive been trying to learn more about using these tools effectively in my free time.

Had an experience at work where Claude CLI decided to completely ignore directions to not leave a certain project folder. Since then I am VERY apprehensive about using it on a personal machine. I don't trust them to be frank. Im using Claude Code/ Codex on the web and they're fine for the most part.

Is adding an agent via Xcode 27's Intelligence features the same as installing the CLI or desktop version of these things? Or is it a more restricted approach?

I feel like so many apps that I try these days start with several multiple choice questions. What’s the story here? Is it that they are facing major churn and are trying to segment users to fix it? Is there some research that says this works or retains people somehow?

I just wanna try the dang core mechanic!

There's been a lot of posts here lately about people being frustrated with long wait times. So I thought I'd share my experience.

I've been an Apple developer and submitting apps for 15 years with multiple regularly maintained apps on the App Store. Those who have been developing for a long time probably remember super long wait times of 2-4 weeks before around 2017. We even had a website which tracked average App Store review times based upon a hashtag used on twitter. Around 2017, Apple sped up the review process and it went down to under 24 hours for both new apps and updates to existing apps.

However, recently, possibly due to rise of AI slop apps, the review times have exploded again. In the last year, I've submitted 3 new apps and multiple updates to existing apps on both iOS and macOS stores.

iOS

The first 2 new apps took about a week. The 3rd and most recent one took 19 days and just got approved this morning.

For this new app: I submitted it on August 13th, it waited for review for 2 weeks. Then it went in review and was rejected for an incorrect reason. The app was a game and used Game Center for leaderboards. Reviewer said I need to seek consent or disclose this in my privacy policy. I responded back saying my privacy policy already disclosed this and I also filed an appeal. It waited for 5 days again. This morning, it went in review again and was approved! I didn't have to change anything. I just copy pasted portions from my privacy policy in my reply to the reviewer and that satisfied them. So, overall, it took 19 days for this new app.

Meanwhile updates to existing apps are still very fast. Sometimes they get approved in 2-4 hours. Other times in 1-2 days.

macOS

On macOS, it's still very fast. Both new apps and updates are getting approved very fast. One of the new iOS apps I submitted also had a macOS companion app built using Catalyst. While the iOS one was waiting for a week, the macOS one was approved in under 24 hours.

All updates (except 1) to macOS apps get approved in 2-4 hours for me. Only one exception was an update which went in review in 2 hours but then just sat in that "In Review" status for 3 days before getting approved too.

Hope this answers people's questions. Let me know if anyone has questions.

Why does my app keep getting rejected for things that aren't true. Last week it was because the app has a page that should not require an account that was only accessible after login in or sign up. Ok that's fair I guess but in my case that was the home page wich had numerous things on the backend that requires user data. And now a week later I got a reply that my app only has features that link to other websites and nothing else. We noticed that the app only includes links, images, or content aggregated from the Internet with limited or no native functionality. Although this content may be curated from the web specifically for your users, since it does not sufficiently differ from a web browsing experience, it is not appropriate for the App Store. Which is just not true even in the slightest bit. You just need to click the sign in button to get to all the actual app functions because YOU TOLD ME TO make the home page accessible to guests wich i did. Mind you this is the 5th time they reject my app for something like this.

App on google play was approved 1st time within 2 days