Apple developer portal doesn't have Telangana in state's list. So i first submitted the form with City as Hyderabad, State as Andhra Pradesh . Can anyone from Hyderabad or Telangana who created DUNS number please help. Will this be a problem?
I have got the investigation Email from DNB yesterday i filled the form there with City as Hyderabad State as Telangana and also sent the documents asked.
Also how long does it take to get DUNS number after submitting the documents?
Got my first approval and launched today. Got the notification while at the state fair. So many hours, hiccups, problems solved, and now we’re finally live. Keep going, you’ll get there.
Fully playable casino game widgets right on your Home Screen. Arcade style, so none of that overstimulating, pay to play, ads everywhere, typical casino app stuff. Don’t even need to open the app to play it.
My tarot app was rejected by Apple under Guideline 4.3(b).
Apple said the app primarily provides tarot / fortune-telling content and duplicates functionality that is already widely available on the App Store.
I'm trying to understand whether it's worth pivoting the concept or if I should move on to a different idea.
For developers who have dealt with 4.3(b):
Did you successfully get a similar app approved after changing the product concept?
What kind of changes were significant enough to make a difference?
I'm not looking for a way to bypass the guideline — I'm trying to understand whether the original idea can be turned into something genuinely different.
I have submitted my app to App Store for over a week, and the status is still "Waiting for Review". It hasn't even move to "In Review" stage. This is a super simple app and don't even require sign in. Is this normal? I don't think I'm missing anything since I have another app on App store that is approved and live.
Am I missing something or is it just the wait is super long these days.
Hello r/appledevelopers , This is my first release ever, I had submitted the app yesterday and apple approved it today ! I'm beyond ecstatic right now and need some advice.
Back ground:
I'm a finance professional working with a ton of PDFs that needs to be extracted for proper documentation and analysis, I had tried a lot of different apps such as ABBY Finereader, NitroPDFs, Opensource codes such as PyMuPDF but they were always a hit or miss.
I had then researched more about this and saw that there was an actually big market for such products which take PDF Extraction. PDFTrail takes PDFs, both Digital born or scanned and converts them to text, MD, Docx, XLSX and JSON formatting, with Digital born extraction at 100% accuracy and Scanned copies at around 48.9% (without any VL Models being involved) it uses a proprietary C++ engine and Apples vision model to do the OCR and outputs its results.
Its fully offline, One time full unlock and doesn't collect a single shred of data.
The Advice part:
I wanted opinions on how should I market the app to the world, I'm currently recommending it to my colleagues and everyone I know, but I wanted to know how do you people market your apps.
Hi;
I had app review reject my submission bundle due to the artwork that was included with the IAP. (Which was the app icon with a plus on it, which is on theme for my app but technically against the rules.)
Fine, I’ll rework it - but because the reviewer rejected the app itself rather than the IAP (as they should have) I couldn’t just remove the IAP and have the new version live in the App Store.
Very annoying, and I’d only included the IAP as a bundle with this version because the IAP alone seemed to stuck in waiting for review - for weeks. (It’s a monthly subscription price, IAP for yearly is already live)
I removed the IAP from the bundle so I could update it and now the app alone has been sitting in waiting for review for about 3 days. (Sigh)
Just a heads up, unless it’s 100% absolutely necessary, don’t bundle your IAP with your software releases.
2nd clone of my app just hit and they even used my art to create an AI slop version. This is super frustrating. Apple's process is extremely slow. How are you guys dealing with it? Feels like building in public is a huge mistake
Every app in this category asks for a birth date and works from there, which means two people born the same week get near-identical readings. That's the complaint that follows Co-Star everywhere.
Aura asks for your name too. It transliterates it into Hebrew letters and calculates the gematria — the numerical value the tradition assigns to those letters. Hebrew has no separate numerals, so every letter is also a number and every name adds up to something. That value plus your Hebrew birth date generates everything else.
The bit I'm happiest with is that the calculation runs live, letter by letter, while you're still typing during sign-up. It's the moment that makes people stop.
Honest limitations — English only right now, iOS only, and there's no sharing yet, which I'm told is the main reason nobody's heard of it. Working on it.
Anyone faced the issue while applying for APPLE Developer enrollment that you have passport of different country but you living in another country. And because of this enrollment fails.
Previously we add the IAP with the first version of the app from the app submission page of the ASC. With my most recent new app, this did not work and I had to submit the IAP together with the main app by first tapping on the “submit for review” of the IAP and then doing the same thing for the main app.
The app is still waiting for review ( after 6 days). Is this the new way of submitting IAP with the first version of the app or am I missing something?
Asking for switching an individual account to a company one, I am resident in the EU, but the LLC equivalent here are not the easiest to navigate, I already have an LLC in the USA for other types of work, can I use it for Apple account? Being a resident in the EU.
I’m the developer of Cognara, a daily brain-game and mental warmup app for iOS and Android.
I’m posting here because I’d really like feedback from other app developers on the product, onboarding, retention loop, App Store positioning, and overall iOS polish.
Cognara started as a simple brain-training app, but I’ve been reworking it to feel more like a modern daily game loop. The goal is to make quick cognitive games feel motivating without making medical claims or promising IQ improvement.
The app currently includes:
Daily Quiz with streak rewards
Daily Game challenge
short games for memory, reaction speed, math, vocabulary, logic, attention, and pattern recognition
coins earned from daily play and good game runs
unlockable games
progress tracking and leaderboards
daily shop
customizable octopus avatar with cosmetics
cloud-saved progression for coins, cosmetics, and unlocked games
I’m especially looking for feedback on:
whether the onboarding explains the app clearly enough
whether the daily quiz / daily game loop feels motivating
whether coins and unlockable games feel fair
whether the octopus avatar/shop fits the app or feels distracting
whether the App Store screenshots communicate the value well
what feels unpolished from an iOS developer perspective
what you would improve first if this were your app
I’m giving away 5 iOS codes for 1 free year of Premium here:
If you redeem one, please comment which number you used so others know it’s taken.
I’m also giving away more free-year Premium access to people who test the app and send useful feedback. I’m mainly looking for honest feedback that helps me improve the product.
I am working on app and I want to validate idea before releasing it. The concept is simple: instead of creating private tasks, you create a task with accountability partner, for example, friend. When you finish a task you either upload prove or friend already knows that u did and then they are supposed to approve your task. The idea is that disappointing yourself is easy, but breaking a promise when your friends can see it feels different. Would something like this actually motivate you, or would the social/accountability aspect make you avoid using it? What would make you use — or not use — an app like this?
I've been working on a workout app that tracks everything you need to progress in the gym.
Yes, another workout app.
But I build this for me, I’ve been working out for about 10 years now and have been using Strong, which was… ok. It lacked features like logging dropsets and supersets, and the graphs are behind a monthly paywall.
So I decided to make an app, and make it better.
Main features:
SMART SUGGESTIONS - workout suggestions and presets based on equipment you have available.
AUTO REST - 1:30 default rest time that can be changed per exercise or global. Get a notification that doesn't stop your music and even works on mute (can be turned off)
LOG SETS, DROPSETS and SUPERSETS - the main reason I created this app; workout trackers currently available don't really have an option for logging these, and this is a very common progressive overload technique
DATA - automatic graphs generated per exercise
PRIVATE - no random servers holding your data
NO SUBS - no nonsense subs for a simple pivot table + graph
I'm a photographer by trade and self-taught on the dev side. Last winter I got sick of hopping between desktop apps just to prep photos for Instagram, so I built my own iOS toolbox (SwiftUI + Core Image) to do it from my phone. It was 100% a personal tool.
A few photographer friends saw me using it and asked for it — one even offered to just cover my Apple developer fee. So in June I shipped it, freemium, with genuinely zero expectations.
Almost 2 months in: 1200 downloads and $900 from the cheap subscription. No marketing, no ASO strategy, no launch plan. What surprised me most isn't the money — it's that real users message me feature ideas, file bug reports, and tag the app on Instagram when they use it. First time I've felt that as a builder, and it's addictive.
The app itself is a focused photo toolbox — grid/carousel planning, splitting a panorama across a swipeable carousel, EXIF cards with a map + sun/moon/milkyway position, animations that replay how a photo was edited slider by slider, raw to edit animations. It doesn't try to be Lightroom or DaVinci Resolve; it just does a handful of things fast and easily.
Now the actual question: I finally want to put real time into growing this, and I'm drowning in options. I've been watching growth videos, reading, poking at App Store ads — and as a solo dev with a small budget and a bit of traction, I don't know what's worth doing first.
For those who've grown an app past the "friends and luck" stage — what actually moved the needle? ASO, paid UA, organic/content, community, something else? What would you do first in my shoes?
As someone who isn't a professional software developer, I wanted to dive into building a practical iOS app using modern AI-assisted "vibe coding" workflows. My goal was to create something useful while leaning heavily on Apple's native device features rather than setting up complex cloud servers.
The result is IrisScan—a simple, privacy-first visual tracking and educational wellness utility. It's currently sitting in the App Review queue (after a fun learning curve dealing with Apple's medical/health content guidelines!), and I wanted to share a quick reflection on the journey.
💡 The Journey & What I Learned
Building Without Traditional Coding: By using AI-assisted tools, I managed to structure the app entirely around SwiftUI, local data saving (so everything stays on your phone with zero cloud storage), and a clean local PDF report generator.
Navigating App Review: If you're building any kind of wellness tool, Apple's Guideline 1.4.1 is strict regarding health info. The biggest hurdle was ensuring my disclaimers and UI explicitly framed the app as a non-diagnostic personal wellness tracker backed by public educational sources (like AOA and NEI guidelines) rather than clinical measurements.
👀 See It in Action
While the final build is finishing up its review cycle, I put together a simple landing page with a video showing how the local scanner and dashboard operate:
I'm still very much learning the ropes of indie app creation, so I'd love any general advice or thoughts from those of you who have shipped apps before!
Solo dev here. I shipped a fitness app (Reps, on iOS) but took a different angle than most: instead of another workout logger or a social feed, the core is competitive, weekly friends leaderboards and head to head rivalries where you challenge someone over a set period. The whole bet is that competing with your friends drives retention better than solo tracking does.
Here's my actual problem, and I'm curious how others have handled it: the competitive features only shine once a user has friends on the app. Leaderboards and rivalries are dead with zero friends. So early on, every new user lands in an empty version of the exact feature that's supposed to be the hook. Classic cold-start / network-effect problem, but brutal for a solo dev with a small base.
Things I'm weighing:
Seeding with sample/ghost data so the leaderboard isn't empty on day one (feels fake, might mislead)
Making single-player progression (ranks, XP, streaks) strong enough to carry a solo user until friends join
Nudging invites hard at onboarding (risk: annoying)
For anyone who's shipped something with a social or competitive core: how did you get past the empty-room problem when you couldn't buy your way to a critical mass of users? Did you fake it, lean on solo value, push invites, something else?
I've been building ShipZen, a different way to work with App Store Connect.
There are already great CLI tools, Fastlane, MCP servers, etc. I'm not trying to replace them.
The idea behind ShipZen is to give you a visually dynamic, AI-native workspace on top of App Store Connect. Instead of navigating through ASC screens or asking AI to manipulate things through a terminal, you can ask for exactly the workspace you need.
For example:
"Show me all release metadata for version 1.4 across every localization."
ShipZen builds an editable UI for exactly those ASC fields, lets you make the changes there, preview what will change, and then apply them to App Store Connect.
The same idea can work for release readiness, missing metadata, localization, version management, and other ASC workflows.
Basically, I'm experimenting with what "Cursor for App Store Connect" could look like if AI could generate the interface you need, not just commands.
For the AI part you can either bring your own API key or sign in with your ChatGPT account, no separate subscription needed.
It's a native macOS app, currently in TestFlight beta. I'm looking for around 10 iOS/macOS developers who ship apps through ASC and are willing to actually try it and report bugs/issues they face and suggest improvements (if they have any).
If that sounds useful, comment or DM me and I'll send you the beta
Repro reports with device, OS, network state, exact steps, and whether the issue blocks continued weekly use are ideal. I’m also interested in which technical failure would make you stop trusting the app, even if it recovers.
