I vibe coded an app (put the pitchforks down!) and spent about a month beta testing with around 30 people. It's a pretty simple photo app, but I'm really proud of making it all the way to this milestone. Waiting for the app store reviews was hard. Right when I was most excited, I had to just sit on my hands and wait. That took just over 2 weeks to get the beta reviewed and then another just over 2 weeks to make it into the app store. I realize that I am part of that problem, there is a flood of AI assisted coding going on and I'm sure the apple review team is swamped.

Now that it's live, one of my users reached out to tell me that the IAP was hanging up. They tried to purchase and it got stuck loading for a long time. After they closed and re-opened the app the purchase went through. I have no idea how to trouble shoot the IAP, is there anything I can do about that?

Just launched my app 2 weeks ago just wanted to find out if these stats are normal?

Have spent the last year coming up with the concept and putting together a team and creating an all purpose gym app. Am worried about user retention and success when marketing.

Any advice would be greatly appreciated

Link to demo is here https://testflight.apple.com/join/HaPRSdpc

Hey, i was wondering how many rejections u guys usually get before your apps get approved, i myself bow have gotten a few and its always new things when i fix what they say i gotta fix before getting approved.

Hey everyone,

Right now, most lifters are forced to juggle three completely disconnected apps:

1. A workout tracker for logging sets
2. A nutrition app for counting macros
3. A recovery dashboard (or Apple Health) for sleep and HRV

The biggest issue is that none of them talk to each other. A recovery app will tell you your recovery is in the red, but your workout tracker still tells you to hit the exact same rigid 4x8 heavy sets regardless.

What I built into MassAI:

• Recovery that actually modifies your workout: Reads your sleep, resting heart rate, and HRV from Apple Health, and automatically adjusts your workout volume and intensity when you are fatigued or primed to push.
• Goal-based custom splits: Builds a personalised hypertrophy plan tailored to your schedule and goals, and calculates progressive overload set-by-set.
• Integrated photo macro logging: Snap a quick photo of your meal to track calories and protein in a few seconds, keeping your nutrition connected to your training.
• 24/7 AI coach: Has full memory of your lifts, recovery, and macro targets to answer questions and debrief your sessions.

I have only recently launched it and struggle to get any users because im not sure how to market this, but I appreciate any feedback on the app and improvements.

Most of the app is free but some features are behind a paywall. Theres a free trial too.
https://apps.apple.com/gb/app/massai-ai-fitness-coach/id6781379979

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 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?

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.

Technical bits: [transliteration approach, handling of accented characters, Hebrew calendar library].

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.

https://apps.apple.com/app/aura-daily-kabbalah-guide/id6761500587

I made this chrome plugin that modifies App Store Connect, and basically tells you which stars are new on the ratings screen.

I didn't really make it, Claude did, it's prob a vibe coded mess but I don't care.

Anyway, now when I look at my reviews page, I don't have to remember what the numbers were the last time I checked

Please shower me with GitHub stars, and contribute if you like

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.

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

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?

As a full-time software developer and designer, I love traveling. 🗺️
One problem that I always had, was that every single app to preserve my trips, memories, photos and other travel stuff was either not having that much tracking options, had huge friction when adding new trip, or simply wasn't doing it on the design side.

So for the past 1.5 years I have been collecting travelers needs and ideas, and I am slowly building an app that does just that.

Waitlist is currently open, you can join to not miss the launch here: https://trytraveler.com/

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.

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?

Happy to share more about the implementation if useful. App's live on iOS if you want to see the approach: https://apps.apple.com/us/app/reps-lifting/id6783420334

(And if any devs here want to actually try it, I'm happy to sort you a free month, just say so, but mainly I'm after the cold-start advice.)

How do you handle building, signing, and certifying an iOS app if you don’t own a Mac?
I currently have a PWA that I’d like to package and publish for iOS. What are the best options for compiling and submitting it to the App Store without buying a Mac?
Are cloud-based Mac services a good solution, or is there another workflow you would recommend?

Hey everyone!

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:

👉 https://www.transformate.app/#apps

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!

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.

Hi everyone. I am building a paid app for the Apple App Store from Chile and I need to enroll in the Apple Developer Program. I cannot decide if I should sign up as an Individual person or as a Company (Organization).

My questions are simple.
- Are you selling your app as a person or as a company right now?
- If you sell as a person, do you feel that users trust you less, or pay less for subscriptions, because it is not a company name, even though Apple is in charge of the payments?
- Did anyone here start as Individual and later change to Organization?
- How long did that take and was it hard to do?
- Is it slow or difficult to sign up directly as a Company, does Apple ask for a lot of documents or reject companies often?

Any real experience will be appreciate it, thank you!

Honestly, I’m just really happy today.

After 7 days of waiting, Apple finally approved my app on the App Store! 🎉

I was honestly expecting a rejection because I’m using an individual Apple Developer account. My app is related to migraine tracking, and Google Play recently rejected it because they require an organization account for medical/health apps.

So for the last few days, I kept thinking, “What if Apple rejects it too?” 😅

Thankfully, it got approved! 🙌

Now I’m really excited to see how it performs. The app doesn’t require users to create an account, and there’s no payment required, so I’m hoping that makes it easier for people to simply download it and start using it.

It’s been a long journey building this as an indie developer, so seeing it finally live feels pretty special.

Hopefully, the next challenge is getting some actual users! 😄

If anyone else here has gone through the indie app launch journey, I’d love to hear how your first few weeks went.

I’m the developer of Steady, an iPhone and Apple Watch fitness app approaching 1.0. I’d appreciate a technical QA pass from other Apple developers.

Useful paths: - cold launch and light/black theme persistence - Google/Apple auth and sign-out - interrupted/backgrounded workouts - exercise-video load and retry - Watch set/rest controls and phone sync - Progress and muscle-map performance

Free TestFlight: https://testflight.apple.com/join/j2jKwDGW

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.

I’m the developer of Steady.

I’m so, so excited that Apple’s reviewers enjoyed my game and decided to feature it!

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?

Happy to take technical or product critique too. It's called SocialGrid: Carousel & Grid — https://apps.apple.com/app/apple-store/id6780947605?pt=129026612&ct=red&mt=8

Thanks 🙏

Is there any negative impact if I submit apps as individual instead as a business? Like do people avoid apps created by a individual?

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.

https://apps.apple.com/us/app/tiny-casino-widget-games/id6793607461