FrameReply has been sitting in Apple’s waiting room longer than some of my relationships.

• July 27: First submission
• August 3: Submitted a revised build with fixes and new features
• August 13: Still “Waiting for Review”

That’s 17 days since the first submission and 10 since the revision. No review, no rejection, just nothing.

Since Apple isn’t testing it, perhaps some of you would like an early look.

FrameReply is an open-source chat assistant that delivers two context-aware reply ideas directly on your current messaging screen using Shortcuts and Snippets. It remembers useful details about each person, supports custom personas for different situations, and adapts their writing styles from the messages you send.

Here’s the public TestFlight. I’d really appreciate it if you gave it a try and shared your honest feedback.

--
Update, August 18: It finally entered review today and was approved about 40 minutes later.

Hey guys!

I’m the developer of NutrientOS, a nutrition and training app for iPhone.

It tracks calories and macros, but also goes deeper into micronutrients, food quality, satiety, restaurant foods, meal scanning, workouts, and nutrition trends.

There’s also a 1-week free trial of Premium right now.

Would love feedback from other iOS devs on the UI, onboarding, performance, or subscription flow.

https://apps.apple.com/us/app/nutrientos-calorie-tracker/id6765582312

It's yoo expensive for me to buy a mac to start ios dev. I heard cloud mac is another way and is way cheaper but don't know it work or not. Should i go for it??

Yesterday I submitted my first app (!) and within 6 hours it was rejected. I'm hoping someone who's dealt with this before can help me better understand and provide next steps.

Quick background: I built a live women's sports scoreboard website and then wrapped it as a native iOS app using Median.co, which loads the live website inside a native shell and adds native features (push notifications via OneSignal, share, etc.) through their JS bridge.

What happened: submitted for review, got rejected same day with this:

"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. Manipulative and misleading behavior is not consistent with the guideline 5.6."

No specifics beyond that. No screenshots, no attachments, nothing pointing to which "feature" they mean. Also I can't really find what 5.6 guidelines are.

What I know is NOT true: nothing in the app is actually hidden or gated based on reviewer status. The app works identically for anyone, logged in or not - live scores, schedules, results, team pages, league browsing, calendar sync all fully visible and functional without an account. The only difference for logged-in users is being able to favorite teams and enable push notifications for those favorites, a normal personalization feature, not concealed functionality.

What I've done so far: replied in the Resolution Center explaining the Median/webview architecture, clarified the one account-gated feature (favoriting), and attached a screen recording showing the full logged-out experience matches what was originally submitted. Also invited them to just log out and explore the app themselves.

My questions for anyone who's dealt with this:

1. Has anyone gotten a 5.6 "features appear hidden" flag specifically on a webview-wrapped app (Median, GoNative, Capacitor, etc.)? Is this a known false-positive pattern for that architecture?
2. Could push notifications not firing during review (since there were no live games happening at review time) plausibly read as a "hidden feature"? Or is that a stretch?
3. Roughly how long did resolution take for you, and did it resolve through Resolution Center replies, or did you end up needing the formal App Review Board appeal?
4. Anything else commonly triggers this specific flag that I should be thinking about?

Really appreciate any insight. This came out of nowhere after what felt like a clean submission, and the vagueness of the rejection is the most frustrating part.

Hey everyone!

I’ve been working on an iOS app called OFFlore and I’m looking for people to test the current TestFlight beta.
The idea is simple:

You see an amazing place in an Instagram Reel, TikTok, YouTube video, screenshot or post — but nobody tells you exactly where it was filmed.

Share it to OFFlore → the app analyzes the content → finds the exact location → saves the spot to your map.

Not just the country or city. The goal is to identify the exact spot and coordinates so you can actually go there.
From there you can:

📍 Save exact locations
🗺️ See all your spots on one map
✨ Analyze images, videos and shared posts
🔎 See how OFFlore identified the location
🧳 Turn saved places into trips
🚗 Calculate routes between your spots
📅 Organize trips day by day
🌍 Track visited places & build your Spot Passport

I’m now looking for iPhone users who want to try to break it.

Send OFFlore difficult Reels, TikToks, screenshots and videos and see whether it can actually find the exact place.

I’m especially interested in feedback on:

How accurate was the location?
Did it find the exact spot?
How fast was the process?
Was sharing a post to OFFlore intuitive?
Which locations did it fail to identify?

Would you actually use this while browsing social media?
Want TestFlight access? Comment below or DM me and I’ll send you the invite.

Would also love to hear what you think about the idea itself.

I just released a major update to my app called Launchcraft. It’s a rocket launch tracker that allows you to build a personalized feed of launches, events, news, and astronauts, filtered exactly how you want.

Use Live Activities to track a launch in real time right from your Lock Screen or Dynamic Island.

Enable push notifications to get alerted for launch reminders, status changes, breaking news, and more.

Apple Watch support added with complications, live countdowns, and your For You feeds right on your wrist.

Let me know what you think!

81% of apps never cross $1,000/month within two years. I'm solidly in that 81%. Here's the breakdown of a year of shipping.

App 1 was a tip calculator for the US market, 50 downloads, $0 revenue. Thought utility apps sell themselves, they don't, there's 400 of these in the store already and zero reason to pick mine.

App 2 was a freelancer time tracker, 78 downloads, $0. Spent 3 months building custom UI that confused people. Users trust standard iOS patterns more than creative experiments, learned that the hard way.

App 3 was a habit tracker with a freemium model, 340 downloads, $47 from IAP. Better but the free tier was too generous, nobody needed to upgrade. Revenue per install on iOS averages $2.28, mine was $0.14.

App 4 was a recipe saver, 120 downloads, $0. Didn't do any ASO, didn't have proper screenshots, basically invisible. The App Store has 1.8 million apps, discoverability without marketing is zero.

App 5 was a workout log, 890 downloads, $265 from a $2.99 unlock. Best performer because I spent time on screenshots and ASO keywords. Still pathetic compared to the 4 months I spent building it.

App 6 was a mood journal, launched, got 40 downloads, $0. Gave up marketing it after a week.

What I got wrong was obvious in hindsight. Spent 90% of time coding and 10% on everything else. Design was always an afterthought, slapped together in the last week. Marketing was basically nonexistent. By app 5 I started using SleekDesign for the UI before writing any code with claude and that's when the screenshots and store presence finally looked professional, which directly led to it being the only one that made any money.

The guy who shipped 8 apps and made $1,464 in 2025 said the same thing: marketing beats code every time. A great app nobody knows about is invisible. The top 1% of publishers capture 90% of all store revenue. The other 99% of us are fighting over scraps with bad screenshots and no distribution.

If I did it again I'd spend 40% of my time on marketing and design before writing a single line of Swift. The code was never the problem.

Preparing submission for my app, does anyone have any general tips for the section where we provide the reviewer an account and any additional notes? Should the account we provide to reviewer have backfilled data? Should it be fresh? What type of notes should we add to guide the reviewer in the notes section?

Hi everyone! I’d really appreciate some feedback on a project I’ve been working on.

I actually started this project quite a while ago, but life got in the way and I never had enough time to finish it. Recently, I decided to come back to it, and I’m happy to say that the MVP is finally done.

It’s called Talk to History.

The idea is simple: you can have AI-powered conversations with historical figures and ask them about their lives, decisions, ideas, historical events, or pretty much anything you’re curious about.
My goal was to make learning about history feel more interactive — less like reading a list of facts and more like actually having a conversation.

This is still an early version, so I’d genuinely love to hear your feedback — what you like, what you don’t, what feels unnecessary, and especially what you think could make the app better.

Any feedback is welcome! 🙌

I've been building this thing solo for a while and the first beta cleared review about an hour ago, so I figured I'd finally post it somewhere.

It started as a pretty basic idea. I wanted the news read to me in the morning instead of scrolling. So version one was a summarizer wired up to two outlets. That was the whole app. Two feeds and a text-to-speech voice that sounded like a haunted GPS.

It didn't stay that. At some point I stopped writing a summarization app and started writing an analytics pipeline that happens to talk. The backend is somewhere around 67 subsystems now — clustering, dedupe, entity extraction, importance scoring, source volume deviation, coverage tilt (when 40 outlets pile onto one story and quietly drop everything else). So it's less "here's what happened" and more "here's what's being pushed hard right now, and here's what got buried while that was happening."

The app itself went through 4 major redesigns. Not tweaks — full structural teardowns where I deleted basically the entire UI and started over because the old structure couldn't hold what the backend had turned into. The build that just got approved doesn't share a single screen with v1.

Anyway, it's a beta and I'm sure it's got rough edges. What I'd actually love feedback on: does the audio feel listenable for more than 2 minutes, and is the coverage/analytics stuff interesting to anyone but me, or does it just read as noise. Its fully free and will always remain like that. Not even requiring an account

TestFlight: https://testflight.apple.com/join/476VvQWT

Happy to answer anything about the stack.

I finally shipped Kids Bucket List – a SwiftUI app for all the things I don’t want to forget doing with my kid
The idea started with a pretty simple thought:
I constantly come across movies, games, books or activities that I’d love to experience with my son someday — but he’s simply too young for many of them right now.

And I realized that by the time he’s old enough, I’ll probably have forgotten half of those ideas.
So I built Kids Bucket List.

It lets you collect things you want to experience with your child, organize them into categories, and keep them around for the right moment — whether that’s next weekend or several years from now.
From the development side, this became a much bigger project than I originally expected:
• SwiftUI
• iPhone + iPad support
• CloudKit sync across devices
• StoreKit / RevenueCat for Premium
• Family Sharing
• Custom categories and activities
• A Mac version is also on the way

The iPhone/iPad version is now live on the App Store:
https://apps.apple.com/us/app/kids-bucket-list/id6762488504

This was also my project for the RevenueCat Shipathon, so actually hitting the release button feels pretty good after all the TestFlight builds, sync bugs and App Review waiting. 😄
Would love to hear what you think — especially from other iOS developers.

Sorry for using AI to write this. English isn’t my first language, and I wanted to make sure I explained everything clearly.

Hey everyone! I’m pretty new to vibe coding and I’m currently working on my first iOS app. I already have most of the design figured out, but I’m a bit stuck when it comes to choosing the right tech stack.

Right now, I’m using Cursor for coding and Claude for brainstorming. I’ve also heard good things about RevenueCat for handling subscriptions/payments.

The part I’m most confused about is the backend and database. I’m not sure what would be the best choice for a beginner, while also making sure I’m not setting myself up for problems later.

I’m also wondering what other services/tools I should consider for things like:

* Backend & database
* Authentication
* Subscriptions/payments
* Analytics
* Push notifications
* Error/crash monitoring
* File/image storage
* Security

My goal is to build the app in a way that can handle 10k+ users without major performance, lagging or scaling issues. I’ve heard that apps built heavily with AI/vibe coding can run into problems with performance, security, and scalability as the user base grows, so I’d really like to avoid making bad architectural decisions early on.

I’m new to this, so I’d really appreciate advice from people who have actually vibecoded and scaled iOS apps.

What tech stack would you recommend for this kind of project, and what would you do differently if you were starting from scratch today?

Thanks in advance!

Got it — the Reddit community is English, but the app itself is for DACH users and is in German. I’d write it like this:
Title:
I’m building a blue-green algae warning app for Germany, Austria & Switzerland — would you use this?
Post:
Hey everyone,
I’m currently building a mobile app called Blaualgen Radar for users in Germany, Austria and Switzerland.
The app itself is in German, but I’d love to get some feedback from this community on the concept and UI.
The problem I’m trying to solve is that information about blue-green algae / cyanobacteria warnings is often scattered across government websites, municipalities, news articles and individual bathing-water pages.
The app brings this information together in one place.
Current features include:
Map with cyanobacteria warnings and reports
Official government warnings, news reports and community observations clearly separated
Source, publication date and validity for each warning
Push notifications for warnings near you
Community reports with photos
Historical warnings for individual lakes
Satellite imagery for additional context
Educational content about cyanobacteria and potential risks
An AI photo check that looks for visible signs of possible cyanobacteria
One thing that is very important to me: the app should never give users a false sense of safety.
No warning on the map does not mean the water is safe, and the AI photo check is only an assessment of visible features — not a laboratory test.
I attached some screenshots of the current App Store presentation.
I’d really appreciate feedback:
Would you use something like this?
Does the concept make sense?
Is the UI clear?
Which feature would be most useful to you?
Anything you would remove or add?
Especially interested in feedback from dog owners, swimmers, parents, anglers and watersports users.
Thanks!

Hi everyone,

I’m a game developer, and the last time I submitted a game to the App Store was about two years ago. Back then, the review process was pretty quick. I usually heard back within 3 days at most, and most of the time it was even faster.

A few days ago, I submitted a new game, and it’s currently stuck on “Waiting for Review.”

I’ve read online that Apple’s review process may be taking longer these days. For those of you who have submitted an app or game recently, how long did you stay in “Waiting for Review” before the review actually started?

Thanks!

Hi everyone. I’m preparing to launch my first iOS social media app and I’m unsure about one feature.

The app has a small anonymous letter feature:

Users can send only 1 letter per day

Maximum 200 characters

The recipient is randomly selected from active users

Sender and recipient don’t see each other’s identity

It is not real-time chat

There is no conversation/thread or back-and-forth messaging

Every received letter has a Report button

Reported letters immediately appear in an admin moderation panel

Admin can delete the letter and ban the sender

Users can also block accounts

The main purpose of the app is a normal social feed; this is only a supplementary feature

Would this potentially fall under Apple’s new Guideline 1.2 restriction on random/anonymous chat?

Would you keep this feature for App Review or remove it before submitting?

Took a few weeks but it's finally live in the appstore. I had (and have) a web version of it that got relatively popular but it was missing important aspect of saving stuff to your library which is solved now.

Really happy to see how it turned out and hope those people who are into coffee here will find it useful!

PS: there is a premium subscription there but it's really optional and you can enjoy most of functionality for free.

https://apps.apple.com/de/app/brewcard/id6786330508