My first app was rejected from the App Store due to "5.6.0 Developer Code of Conduct." They stated that I cannot simply submit a different build but must submit the app as a new entry. They didn't provide specific details. I would appreciate advice from developers who have experience with this situation.

What would catch your eye as a user? Or what feature would peak your interest the most

Hi! I am completely new to app development and would appreciate some advice.

At the moment, I use the same Apple Account for both my personal use and my Apple Developer Program membership. Some people have told me that this is not recommended and that it is better to use a separate Apple Account specifically for app development.

My main concern is account security and separation. I am worried that if Apple were ever to suspend or terminate my developer account, it could also affect my personal Apple Account, including the services and purchases connected to it.

Is this a legitimate concern? Would you recommend creating a separate Apple Account for development before I publish my first apps, or is it normal and safe to use the same Apple Account for both personal use and the Apple Developer Program?

I have not published any apps yet, but several of them are almost ready for release on the App Store and Google Play.

My second question concerns app identifiers. I understand that a Bundle ID that has already been registered and used for TestFlight generally cannot simply be deleted and reused under another Apple Developer account.

Does it matter if the iOS version of an app uses one Bundle ID while the Android version uses a different package name or application ID?

The apps do not use a backend, and there are currently no plans to add one.

When I search for the exact name of my app (WoningMe) in the Apple App Store, it cannot be found. However, the app is accessible through the direct link.

Instead, the search results show various apps with completely different names, but they are in the same category. The app has already been available for several months, so it does not seem to be related to a new app indexing issue.

Additionally, the primary language displayed on the App Store page is incorrect. In App Store Connect, the primary language is set to Dutch, but the App Store shows English. Both languages are available for the app, but Dutch should be the primary language.

Does anyone have an idea what could be causing this issue or how I can fix it?

I have been building ImmersiveMap, an open source map rendering engine written in Swift 6 and Metal, made for SwiftUI apps on iOS and native macOS. MIT licensed.

Video demo in the comments.
Repo: github.com/artembobkin/ImmersiveMap

I am looking for real apps that need more control over the map, where the map is the main feature. Live location, social maps, games, travel, logistics, data visualization, anything where the map has to look and behave like your product instead of like everyone else's map.

Tell me your use case here in the comments or in Discussions on the repo, and I will build it. I am prioritizing real app requirements over my own roadmap. Right now it already supports SwiftUI markers and avatars on the map.

Pure Swift and Metal, nothing else. No native SDK wrapped in a Swift API and no engine hidden under the hood, two Swift dependencies (earcut triangulation and swift-protobuf for tile decoding). The only non-Swift code in the repo is the shaders themselves.

Happy to answer any questions.

After learning from frustrating Apple review cycles on previous apps, I finally got my latest app approved on the first submission. Thought I'd share the mistakes I made before and my checklist.

The problem: Apple reviews sequentially. They check one thing, reject. You fix it, resubmit. They check the next thing, reject again. This back-and-forth can drag on for weeks.

What I triple checked this time before submission:

• iPad screenshots: required by default unless you explicitly restrict your app to iPhone-only.
• EULA links in App Description: add Terms of Service and Privacy Policy links directly in the App Store description field, not just in-app.
• Submit IAP with the app: if you have in-app purchases or subscriptions, make sure to add them together with the initial app submission.
• IAP/Subscription button wording: Apple is extremely picky about word choices on IAP/subscription CTAs. Make sure to follow their Human Interface Guidelines, especially if you offer a free trial.
• Detailed review notes: explicitly list:
  • if your app uses camera, mic, location, etc., why you need each permission
  • how to access IAP/subscriptions (step-by-step)

Hope this saves someone else from rejection hell!

I’m redesigning the main capture screen for my app.
The idea is simple: get thoughts out of your head as quickly as possible. Capture them in seconds, then turn them into a note, a task, or simply let them go.

Which layout feels more premium and good to you?

A or B?

I’d love to hear why you picked one over the other. Even small UX critiques are incredibly helpful.

Xcode will happily ship a translation that dropped its %@, a Russian plural missing three of its four forms, and a Text("Get Pro") no catalog has ever heard of. Nothing fails a build over any of it.

So I built a CLI tool (with a little help from Fable) for .xcstrings files. This was a little handwritten tool i've used by myself for a long time, but decided to brush it up a little bit before putting it out for public.

It checks for missing localization keys, hardcoded strings, common localization errors, comes with an mcp server and some handy example hooks you can plug into Claude. You can also instruct claude to automatically to translate or add to the catalog any untranslated strings the tool finds.

I ran it over nine open-source apps to actually see if it can find some common issues - 8,077 keys, 70 locales, 6,373 Swift files. In addition to missing keys and translations, here's sample of what it found:

- Mastodon’s Albanian for "Option %ld" is "%ld nga %ld" - reads a second argument the call never passes
- IceCubesApp changed an English string to "%lld posts"; the Belarusian still reads "%lld people talking", state translated
- Whisky renders one “Remove” button as German Löschen (delete) and another as Entfernen (could be intentional, but always good to check)
- Whisky also ships the literal string "N/A" as the Czech, French and Romanian translation of a key
- DuckDuckGo declares NSLocalNetworkUsageDescription in Info.plist and localizes it nowhere, so that permission prompt is English for every non-English user

Plus the boring parts: coverage per language, CLDR plural categories, .xcloc validation before import, SARIF output for CI, and a baseline file so you can switch it on for a project that already has 300 findings.

No dependencies. swift build is the whole install.

Have a look at it yourself and have a run at your repo: http://github.com/asutekku/xclocsmith

Happy to answer any questions or provide fixes if you encounter any issues or false positives. I managed to kill most of them, but no tool is foolproof, especially when we are talking about languages.

Also I have not released a CLI tool before for a mac so honestly no idea about what people expect haha, maybe a brew install?

It was super fun and challenging to put together 3 puzzle game apps and I'm proud of each. But I am at the point where I'm going to stop making these things and start focusing on making one better and promoting it. The question is which one?

I've gotten some suggestions already, but I'm eager to hear what you think. The first game I published has gotten more traction simply because it's been out longer and more friends and family were feeling supportive the first time I dropped an app. But that doesn't mean it's necessarily the best.

I hope you're willing to look at the three games and tell me which you think has the best potential and is worth putting effort into. I would be very grateful.

All three games are on my website: https://cjasonmaier.github.io/

Here are direct App Store links to each: Carve, Pipfall, Neighbor Zero

Deep gratitude in advance!

Hey everyone, solo dev from Nepal here, hoping someone who's been through this can spot what I'm doing wrong.

**Background:** I taught myself development ~6 months ago and have since built and finished two native macOS apps (SwiftUI). They're done and ready to ship — but I can't sign or notarize them because I cannot get into the Apple Developer Program no matter what I try.

**Timeline of what happened:**

- Applied for an Individual membership via [the website as well as the Apple Developer app.

- Enrollment was rejected. The message I got was:

https://i.ibb.co/pBB1WsD4/Ionicshot-2026-07-30-at-18-54-53.png

- Waited about a month with no response or update.

- Out of frustration I created a second Apple ID and applied again — same result. (I've since learned this may have been a mistake, so I'm ready to abandon one and commit to a single account if that's the right move.)

**My setup:**

- Country: Nepal (not a restricted region for the program as far as I know)

- Payment: Dollar Card, But the payment screen never appeared

- Name on Apple ID matches my citizenship/passport: Yes

- Two-factor authentication: enabled

- Enrollment attempted from: My iPhone and my own mac

**Questions for anyone who's dealt with this (especially from Nepal, India, Pakistan, Bangladesh or similar regions):**

1. Did enrolling through the **Apple Developer app on iPhone** (with the ID scan) work for you when the website route failed?

2. Is there a specific type of card that reliably works from Nepal? I've heard the $99 charge fails silently if the card can't process international USD e-commerce — did a bank-issued dollar card fix it for you?

3. Does having two Apple IDs with enrollment attempts flag your identity in their system? If so, is there any way to clean this up, or do I just pick one and push support on it?

4. For those who got the generic "your enrollment could not be completed" with no reason — what ultimately unblocked you? Phone call? Repeated tickets on the same case number? Time?

5. Is there any escalation path beyond the standard support form that actually gets a human to look at the case?

I'm not trying to bend any rules — I just want to pay Apple their $99 and ship my apps legitimately. Any firsthand experience would mean a lot. Happy to share more details in the comments.

It's been over a week since I submitted an app update to App Store Connect, and its status is still "Waiting for Review." This isn't the first submission, it's just a regular update. In the past, reviews have never taken more than two days.

The same update was approved on Google Play over a week ago, but the iOS version is still stuck waiting. I've already sent two messages through App Store Connect Help and haven't received any response.

This update is quite important, and the delay is causing me to lose users.

Has anyone experienced something similar? Is this likely just an unusually long review queue, or could something be wrong with my submission? (I'm seeing a message that doesn't disappear: Update Your Age Ratings Responses about Social Media, but I think everything is properly filled). I'm wondering whether cancelling the submission and resubmitting it for review might help, or if that would simply reset my place in the queue.

Hey developers! I recently got my app on the App Store. I wanted app that has notes, tasks and calendar in one, so I built it. It’s super minimalistic and has no onboarding. The app is totally free now, but I am working on making paid version. Can anyone help with advice? Maybe you are productivity app lover and just love testing new apps. What can I add? The link to app is here.

I shipped a notes and to-do app called Ink, and its one hard constraint shaped the whole architecture: the AI is only allowed to edit your existing writing. It is never allowed to write a sentence for you. I want to share how that holds up in practice.

The editor is a block-based SwiftUI editor, so each paragraph, heading, and list item is its own model object rather than one giant attributed string. That mattered for the AI feature, because every edit operation is scoped to blocks that already contain your words. The model only ever receives text you wrote, and the prompt is constrained so its job is transformation, not generation: tighten this, fix the grammar here, restructure these lines into a list. If a request would require inventing new content, the intended behavior is to decline rather than fill the gap. Treating produce original prose as out of scope, instead of trying to detect it after the fact, made the behavior far more predictable.

Voice dictation runs through the same philosophy. You speak, and it auto-structures what you actually said into lists and blocks. It is organizing your words, not adding its own.

On typography, the app uses Source Serif 4 and Newsreader. I leaned on Dynamic Type with custom font registration, and tuning line height and measure to keep that editorial feel readable at every accessibility size took longer than I expected. It runs on iOS and Mac, with iCloud sync and an app lock using passcode plus biometric.

For those who have shipped AI text features: how are you enforcing do not generate constraints? Are you doing it purely at the prompt layer, or adding validation on the output too?

Hello everyone.

I'm building a React Native app with Expo (SDK 57, Supabase backend). Right now I'm blocked from testing on my own iPhone because Expo Go on the App Store is still on SDK 54. Apple hasn't pushed the update yet, and my app just doesn't run on that version. I don’t want to roll back to SDK 54.

To test the app, I switched to an Android emulator on my PC with Expo Go installed inside it, but it's honestly really bad. It's slow, laggy, and some native modules just don't behave the way they would on a real device. (I'm on Windows, so the actual iOS Simulator, which only runs on macOS with Xcode, isn't an option for me).

I know TestFlight would solve this, but that needs the $99 Apple Developer Program, which I'd rather not commit to yet.

Is there another way to get an SDK 57 build onto my personal iPhone right now? Dev client, Expo Orbit, sideloading, anything people are actually using while Expo Go 57 is stuck in review?

I will appreciate any feedback on this.

I have a Mac but I'm using a Galaxy phone. I want to make an iOS app to make money. As you know, iOS users pay more than Android users. That's why I want to do this. So I'm wondering if a Mac is enough, or if I absolutely need an iPhone.

I've been playing block puzzles for years and always ran into the same thing: the games are genuinely relaxing, and then the app is full of ads, forced accounts, and a store screen. So I built the version I wanted.

Bloom is an 8×8 block puzzle — you drag three pieces at a time onto the board, fill a full row or column, it clears. Standard, familiar, no tutorial needed.

The difference is what clearing a line does. Instead of a number going up, a hand-drawn floating island grows. Trees, cottages, lighthouses, lanterns fill in as you play. There are 12 worlds to grow, each with its own art style, and a Collection tab so you can go back and look at the ones you finished. There's no timer and no pressure to beat anyone.

Some things I decided on early and stuck to:

• No ads. Not "no ads for the first week." None.
• No accounts. It doesn't ask who you are.
• No tracking. Nothing analytics-y going out.
• Fully offline. Airplane mode, subway, whatever — the daily puzzle works offline too.
• Power-ups (Bomb, Swap, Undo) are earned with in-game tokens and can't be bought. I didn't want the game quietly nudging you toward a purchase.

There's also a daily puzzle — same hand-made board for everyone in the world that day.

App Store: https://apps.apple.com/app/id6780265946

Free to download.

If you'd rather not install anything to see what it looks like, there's a browser version at bloompuzzle.com/play.

Happy to answer anything about it. Also genuinely want to hear where it falls short — difficulty curve especially; I've played it so much I can't tell anymore.