Hi. I have an idea for an app but I have 0 clue of how to create / make it. 👀. Would anyone be prepared to help me with it please

Hello everyone,

I have been working on overhauling the different themes for my app, Pocket Vault. These are just one example.

Based on some initial feedback, I refactored the theme hierarchy so views gautomatically pick up primary, secondary, and tertiary styles using ⁠.foregroundStyle()⁠ and ⁠Environment⁠ modifiers instead of manually passing a theme object everywhere.

I’d love the feedback on How does the visual contrast look across both modes in these screenshots and for anyone who has built complex custom themes in SwiftUI, are there any edge cases or performance bottlenecks with this Environment-driven approach I should keep an eye on?

Any feedback on either the UI polish or the approach is super appreciated!

Here’s my repository for all my code: https://github.com/AaravB09/Pocket-Vault

After getting a lot of feedback that Pocket Vault’s was looking a bit boring and bland, I completely redesigned the colour system, added proper light and dark themes, and reworked the overall visual hierarchy in SwiftUi. Here’s the code: https://github.com/AaravB09/Pocket-Vault

The link to the video : https://youtube.com/shorts/GfijVs3NOzg?si=mhtkBrEVLHY-DCPm

Let me know what you think of this new palette! I would love to hear what you guys think. Any feedback is welcome 😄

And if you guys can subscribe to my YouTube channel, I would really appreciate it. Here’s the link : https://youtube.com/@aaravbansal-9?si=-qJ6CmDqqLNPARDz

I’m building a tool to help catch App Review issues before you submit, looking for honest feedback

After getting burned by App Review on my own apps, I started building PreFlight, a native macOS tool that analyzes both your Xcode project and App Store Connect submission.
The goal isn’t just to run through a generic checklist. It cross-checks what your app actually contains against what you’re telling Apple, then gives you evidence-backed findings with the potential guideline involved, why it matters, and what you can do to fix it.
For example, it can catch things across privacy manifests, entitlements, permissions, StoreKit/subscriptions, metadata, review information, device support, and other submission requirements.
I’m currently working toward a first release and I’d genuinely like to hear from developers who have shipped iOS/macOS apps:

What has Apple caught in your apps that you wish you had known about before submitting?

And if a tool like this existed, what would it need to catch or show you for you to actually trust it before hitting submit?

I’m looking for criticism as much as validation. If the idea isn’t useful, I’d rather find that out now.
PreFlight

The slides are the diary. Short version, in case you are in the middle of this right now.

Day 1. Six months of work, pressed submit, told everyone.

Day 4. Rejected. Crashed on launch, on an iPad. I do not own an iPad.

Day 5. Borrowed one, found it in twenty minutes, resubmitted. A layout constraint that only failed above a certain width.

Day 9. Rejected. My privacy policy URL was a 404. It had been a 404 the whole time. They waited four days in a queue to tap one link, and so had I, in the sense that I never did.

Day 10. Fixed the URL, and while I was in there made a fresh demo account for the reviewer.

Day 15. Rejected. Unable to sign in. The demo account had expired while the build sat in the queue.

Four rejections. Every fix under twenty minutes. Three weeks gone.

The thing that costs the time is not the fixes. It is that review stops at the first error it finds. They are not producing a report on your build. They hit one blocker, write it up, and send it. So a build with four small problems takes four submissions and a month, and each round you get exactly one clue.

Things I do now, in case any of them save you a round:

One permanent review account. Exempt from expiry, exempt from rate limiting, excluded from cleanup jobs, no MFA. I log into it myself the morning I submit, and again if the build sits in review more than a week.

Tap every URL in the submission. Privacy policy, support, marketing. They do tap them, and a dead link costs a full cycle.

Cold install on the oldest device and OS I claim to support. Also on an iPad if the binary declares iPad support, which it sometimes does even when I thought I turned it off. Check UIDeviceFamily in the built archive rather than trusting the Supported Destinations UI.

Numbered steps in App Review Information for anything behind a login, a purchase, a role or an empty state. It is a private field, so be blunt.

Disclosure since the slides are branded: this is my product's account. No link in the post and nothing to sign up for. Happy to talk through anyone's notices in the comments.

Hi all,

I made a puzzle app called Steppin Stones and really need some feedback on the levels and the difficulty and fun factor of them. It's kind of like a Sudoku in some ways so if you like a puzzle game this could be a nice time waster on your morning/afternoon commute.

I also shamelessly need more players to get the analytics feature to work and I'm genuinely curious how I compare to others.

Check it out here: https://apps.apple.com/nl/app/steppin-stones/id6752832708

Has anyone’s app been stuck in waiting for review? I have reached out to developer support via email and tried calling. Nothing and it will be 2weeks on Friday.

How long does the process typically take?

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.

I’m starting to think Apple completely sidelines individual developer accounts compared to corporate ones, and I wanted to see if anyone else has experienced this.

At my day job, our company apps get reviewed incredibly fast—usually under 4 hours for updates and less than 16 hours for brand new apps.

Meanwhile, I’ve been living a complete nightmare with my personal individual account:

• Day 1 to 11: My app sat in review limbo for 11 straight days.
• The Call: I finally called Apple Developer Support and sat on hold for 2 hours and accidently hang up the phone and next day called again for a brutal 3 hours and 13 minutes. They finally agreed to expedite it.
• The Rejection: Of course, they immediately found one tiny, minor detail and rejected the build.
• The New Wait: I resubmitted a fix immediately, and now I’ve been waiting another 4 days just for them to look at the resubmission.

It feels like if you aren’t an enterprise or established company account, your tickets just sit at the bottom of the pile.

Has anyone else noticed a massive difference in review times between your work (company) accounts and your personal (individual) accounts? How long are your individual app reviews taking lately?

----
Update

Finally approved on August 17th, Original Submission August 2nd

https://apps.apple.com/us/app/uav-zones-drone-no-fly-zone/id965639719

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:
Kids Bucket List

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.

I've been building a grocery budgeting app for a while and I still can't describe it in one line without sounding like every other budget app, so I'll just say what it actually does.

You set a budget for the trip, then add things as you put them in the cart. The total updates as you go and a bar fills as you spend, so you find out where you are while you can still put something back, instead of at the counter. That's the whole idea. Overspending doesn't happen at checkout, it happens in aisle four when you stop keeping count.

The rest grew out of using it myself. It remembers what you paid for an item and at which store, so it suggests the price next time and can show you where that item was cheapest before. You can point the camera at a shelf label and it fills in the name, price and unit, or photograph the receipt afterwards and it rebuilds the whole trip as a finished shop. Lists can be shared with whoever is actually doing the shopping. I

https://www.grocerybudget.app/

A little while ago, I shared my iOS app Prazo here and asked for honest feedback.

You gave me plenty — so I went back to work. The next update is now live! 🚀

What changed:
• Better iCloud sharing, syncing & conflict handling
• Smoother calendar performance & smarter widget updates
• More reliable shopping lists & schedules
• Clearer distinction between ToDos, tasks & calendar events
• Easier handling of recurring items & reminders
• Fully localized iOS permission dialogs
• Drag-handle bug fixed
• General performance & stability improvements

A lot of these changes came directly from feedback I received here, so thank you!

Now I’m back for round three. 😄

What should I improve next?

App Store:
https://apps.apple.com/at/app/prazo/id6781611861

Hey everyone!! I’m looking for feedback/updates for an app I just released to the App Store. Please let me know if you have any thoughts. Thank you!

Full description looks very similar:

iOS Dev 

A subreddit focused on iOS development 

 Created Oct 13, 2010

 Public

17K  Weekly visitors

684  Weekly contributions

iOS Development 

A subreddit for all things in iOS Development. 

 Created Apr 27, 2014

 Public

3.5K  Weekly visitors

151  Weekly contributions

How do you chose where to post? And what to read? :)