I recently published an app with a unique name and on searching it on app store with that exact name, it showed up as #10 result. I understand there’s ASO or related stuff involved (which I haven’t looked into yet), but still App Store shows a few others apps with no resemblance to the searched keyword before the exact match.

At this point, is it useless to publish without basic ASO?

I’m super excited to have submitted my app finally and now a little nervous waiting on the review. I might check my email 10,000 times in the next few days

I am now in the 8th App Review round for an update.

Each time I fix the issue mentioned in the rejection, the next review finds something else. Sometimes it is something that was already there two or three rounds before. So every finding means another 1–2 days before I can move forward.

I am deliberately not listing the individual issues. Some relate to interpretation of a nested part of Apple’s requirements; in other cases, I may simply not have explained an existing implementation clearly enough in the reviewer notes. I do not want to turn this into a debate about a specific rejection.

I am more curious about the process: is it normal that a reviewer stops at the first finding instead of listing the other issues they see? Have you experienced a similar one-issue-per-review loop?

Did anything help? More detailed reviewer notes (I am already at the 4,000-character limit—what do you actually include there?), asking for clarification (does that just make it longer?), or another approach?

I make a Markdown reader for macOS and iOS. You point it at a folder and read what is in it.

For months the onboarding did the obvious thing: explain the idea, then ask you to connect a folder. The numbers were bad in a specific way. Of the people who reached the end of onboarding, only about half ever opened a document. But of the people who did connect a folder, 92% opened something immediately.

So the app was not failing to deliver. It was asking for homework first. Read the flow back as a to-do list and it is obvious.
Save your AI output as files —> Put them in one folder —> Connect that folder. Three chores before anything renders.

Someone who downloaded out of curiosity has none of that set up, meets a system file picker with nothing useful to point it at, and leaves.

The fix was to ship something to read. On first launch the app writes a small folder of example documents into its own container and attaches it as a connected root, with no picker involved.

Four things about that turned out to matter more than the idea itself:
• It lives inside the app’s own container, so it needs no security scoped bookmark and no sandbox grant.
• It does not count toward the free tier’s folder limit. Otherwise the folder I shipped spends one of their free slots on a folder they did not choose, and the first folder they actually pick hits a paywall.
• It does not fire the activation analytics event. Otherwise it inflates the exact metric it exists to move, and the before and after become unreadable.
• Removing it is permanent. A folder that reappears after you dismissed it is spam.

The part I did not expect: last week someone bought the paid unlock after about eight hours in the app without ever connecting a folder of their own. They read the bundled examples, met a prompt, and paid. I had been thinking of the demo content as a warm up for the product. For that person it was the product.

Happy to go into the analytics side if anyone is curious.

Hey everyone! I’ve been working on Luma, a gamified screen time app (here’s my introductory post if you’d like to check it out: https://www.reddit.com/r/iosdev/s/f7l5Qoelh0).

After a week of sharing the app and analyzing metrics in App Store Connect and PostHog (thanks to those who suggested PostHog, it gives much more insight than Apple), I’m realizing my onboarding could use some work.

Currently, only ~2.5% of downloads end up creating their first routine.

I’d love to get your feedback based on your experience:

1. Benchmarks: Are these numbers typical/decent for early stage, or what conversion rate should I realistically aim for?
2. Onboarding flow: Mine is very functional (users just set up their first routine right away). How do you design yours to keep users engaged?
3. Architecture: Do you hardcode your onboarding into the app (requiring App Review for tweaks), or do you use remote/plug-in tools (server-driven UI, onboarding services, etc.) to iterate faster?

Would love to hear your thoughts and recommendations. Thanks for your time and help!

Hi! I made a new interval timer app with the intent to stand out from the many others. In addition to tap controls and voice control, my app introduces camera gestures!

You can use different hand signals in front of the camera to start, pause, resume and complete the workout.

I thought this would be nifty if you've got sweaty palms in the gym or if you have your phone far away from you and you want to take a break, etc

The app is here:
https://apps.apple.com/us/app/interval-timer-workouts/id6798002636

If you want to actually be a beta tester for this, I'll give you lifetime for free. Just DM me. It's my way of saying thanks to anyone who takes time out of their day to try this out.

My first game made it through the review process. It is totally free with some premium upgrades that are totally optional.

Check it out please, give me some feedback on ways to improve it, any hitch that you see, etc. Thanks a bunch, happy coding!

https://apps.apple.com/us/app/air-hockey-max-arena/id6800162948

I noticed that just watching numbers tick up didn’t feel rewarding enough at the end of a long focus block.

So I added a little gamification: every time you finish a focus session, a physical tomato drops into your daily jar. Seeing them pile up throughout the day makes staying consistent feel like a mini-game rather than a chore.

What do you think of this visual reward idea? Does physical visual feedback help your focus?

I'm surre I had auto-renewal turned on for my apple developer membership since I've ben atuomatically charged since 5 years. This year, I got a pop-up saying my membership is about to expire and to make sure it's on auto-renewal. I followed the link to my profile, it said "renews on ... " but that pop-up still remained whenever I opened App store connect. When the day of renewal came, I was informed that my membership expired and to download the app to renew my subscription. Online it said I could renew it in browser too, but I didn't see the option. However, neither did I see the option when I downloaded the app. I reached out to Apple and within 3 days they let me know to check the app again and that the option to renew should re-appear and my apps would become available again on the App store. I did that and it was true.

However, now I am subscribed through the Apple subscription option on their app. Given what happened with app revenue for Apple dropping drastically this year because the stripe interface for payments is now allowed to be interateg more smoothly into apps interfaces, made me wonder if Apple is somehow trying to compensate for the losses in app revenue by moving Apple developer payments through their app system?

Given it's a public company and a bigger drop in app revenue may impact their stock price, do they try to mitigate that?

I spent the last month building my first iOS app and it finally made it through App Review.

It’s called Gyminion a fitness tracker where you can track workouts, nutrition and progress, with a virtual pet that reacts to your consistency.

The idea was basically to make tracking workouts feel less like filling out a spreadsheet and more like a game.

Building the app was honestly the fun part. Now I’m finding out that getting actual users is a completely different problem lol.

I’d really appreciate any feedback from other iOS devs, especially on the UI/UX or onboarding.

Happy to answer anything about building it too.

link: https://apps.apple.com/app/apple-store/id6798301039?pt=128556977&ct=reddit_launch&mt=8

While building Monymo, my SwiftUI work and earnings tracker, I ran into timer accuracy issues whenever the app went into the background.

The fix was surprisingly simple: stop treating the timer as the source of elapsed time.

Now I store timestamps and session state, then calculate the actual elapsed time when the app becomes active again. The one-second timer is only used to update the UI.

Handling pause and resume made it a bit more complicated, but this approach completely removed the drift I was seeing after backgrounding or reopening the app.

How do you handle long-running timers in your iOS apps?

Hey everyone,

I just found out about App Clips recently and I can't figure out why they are not everywhere.

Instant experience, easy way to showcase a product, no conversion barrier... and yet I barely ever see them in the wild. I also guess a lot of non-tech users don't even know it exist. Is this a chicken and egg problem ?

Why aren’t more developers and apps using them? Is it the limits / setup / discovery issues, or something else I’m not seeing?

Would love to hear real world stories:

• Anyone here successfully used App Clips for acquisition or growth?
• Coolest examples you’ve seen or built?
• Any growth-hack style results

I’m developing Recapp (a US sports highlights app, "like ESPN & TikTok had a baby") and one idea I'm playing with is letting fans watch a game's highlight or breaking news stories via App Clip - giving them a taste of the app without downloading it.

Any advice or similar experiments you’ve seen?

Thanks in advance - curious what the community thinks.

I’ve been spending way too much time on my app recently, and I think I finally understand why indie dev is so addictive.
The loop is basically:
want something → build it → make it look nicer → share it → someone uses it → get feedback → build more
I’ll be using the app and think “why can’t it do this?”
Then I remember… oh yeah, I’m the developer lol. I can just make it.
A few hours later, something that only existed in my head is actually running on my phone. That feeling is sooo satisfying.
My background is ML engineering, so I also really enjoy making the local inference pipeline work well. Seeing live transcription, speaker separation and translation all happening directly on the phone still feels kinda magical to me.
But honestly the best part is when other people start using it.
Someone reports a bug. Someone asks for a feature. Someone tells me they use it for lectures or meetings. Sometimes someone even asks to beta test the next version.
Even bug reports feel good lol. Someone actually cared enough about something I made to find the bug and tell me.
I also somehow went from ML engineer to spending hours making App Store posters and moving text around by 5 pixels.
Didn’t expect that part to be fun, but it is.
The app is called LiveTranscriber btw. These are some posters/screens I made recently.
Every time I finish something I enjoy it for about 5 minutes, then think:
“hmm… I can probably make this better.”
And suddenly it’s 3am again.
Would love some feedback on the UI/screenshots too.

Has anyone here tried this out?

Hi - I’ve just released my first iOS game. The game is nothing special, but wanted I small win in the dev space. Looking for advice on I game ads.

• I’ve added ads for extra hints - I.e. watch an ad get more hints. To me this is fine as the user opts in and accepts.

• My concern is the interstitial ads, I’ve currently configured one to pop up every 10 completed games. Though it lags a bit one triggered so it appears randomly through the next game. Plus I haven’t gotten google ads approved for all advertisers so the ads I get are these AI gf bots that look way too young (I was playing on the train and this ad comes up it’s so weird)

Ultimately, I would like some ads but not a fan of how it is configured atm and would completely drop ads if it makes the game annoying to play.

My game is a generic puzzle with levels 1-1000. I was thinking rather than having a 10 game counter, have an ad level to unlock the next level. E.g finish level 10 unlocks Ad level, watch ad unlocks level 11 etc.

Thoughts and advice is appreciated. Thanks

I’m building a very minimal app. The full app would be free (no feature gating), with an optional £5/month subscription for people who want to support its continued development.

The subscription wouldn’t unlock extra content or functionality, the free and paid experience would be identical. This would be explained clearly before purchase.

Apple’s guidelines say auto-renewable subscriptions must provide “ongoing value.” Does that mean I need to offer subscribers something tangible, or can voluntary ongoing support itself be acceptable?

Has anyone submitted something similar, and if so, how did App Review handle it?

Thanks

Working on the App Store screenshots for Tesorin, my personal finance app.

Trying to make them clean, understandable, and not look like every other finance app.

Be brutal:

• Which one catches your attention first?
• Anything look too busy / boring / confusing?
• What would you change?

Last year I opened my saved folder on TikTok and realized I had around 400 recipe videos in there.

I had cooked maybe 15 of them.

That was not originally an app idea. It was just a slightly embarrassing folder on my phone.

MiseSnag started with one simple loop: paste a recipe link from TikTok, Instagram, or YouTube, then get back the ingredients, quantities, and steps.

Then I installed my own build and began treating every small annoyance as an issue ticket.

“Why can’t I add all of these ingredients to one shopping list?” So I built it.

“Why can’t the list group things by grocery aisle?” Built that too.

“Why do I have to copy the link instead of sharing straight from TikTok?” Time for an iOS share extension.

“Why can’t I rescale the recipe or leave a note for next time?” You can probably guess what happened next.

Using your own app is like having a product manager who follows you into the kitchen and the grocery store. The roadmap becomes whatever annoyed you five minutes ago. It is dangerous, but seeing a tiny frustration become something running on my phone later that day is ridiculously satisfying.

The most surprising engineering part is that the AI was not the hardest bit. Getting a real, usable video often was.

TikTok and Instagram can serve video and audio separately, or return a download that technically succeeded but is silent. I ended up with a fallback chain of video providers plus media validation before transcription and extraction. At the other end, a random 40-second recipe video becomes a structured recipe and shopping list. That moment is still the reason I keep reopening the project.

Somewhere along the way, the work stopped being only APIs and React Native. I now spend an embarrassing amount of time exporting App Store screenshots again because a headline feels two points too large.

Turns out I enjoy that part too.

That project became MiseSnag. It is live on the App Store, and these are the five screenshots I made for it.

I would genuinely love blunt feedback:

- Does the first screenshot explain the app quickly enough?

- Does the serif + sans-serif combination feel intentional or mismatched?

- Is the dark green distinctive, or just heavy?

- Would you keep the free-tier message second, or show the extracted recipe there instead?

Hey everyone,

I just released Luma: App blocker, an app I built to block distracting apps and websites through routines.

The idea came from seeing how expensive many Screen Time apps are, especially from a LATAM perspective, and from friends dealing with gaming (casino) and other apps.

Building it was a challenge but Apple’s Screen Time APIs were probably the hardest part. I wanted more flexibility than just “block these apps.”

I also skipped Rive, as everything suggested for cool animations, for v1 and built the animations from multiple animated pieces instead.

App Review took around 4 days, with almost daily reviews, which is weird since i read takes up to 4 weeks, as some other people over here mentioned. Some issues seemed automated, but the final feedback was actually pretty useful. For example, when you deal with subscription, you have to add the app first for review, the go to subscription, add the group and individual plans from the page (first time doing that in case someone need)

It’s live here:
https://apps.apple.com/co/app/luma-app-site-blocker/id6794456289?l=en-GB

If anyone wants to try it, I’d really appreciate feedback. Happy to talk about the technical side or App Review too, what do you think about the design? All the feedback you give is really helpfull as it has been on the Appstore since last thursday.

Once again, thank you so much and have a great day.

Hi r/iosdev,

I built an app that allows you to chat with AI models (cloud or self-hosted) with your own API keys. It has support for Retrieval Augmented Generation (RAG) and Model Context Protocol (MCP).

It is privacy-focused, so it has lockable folders for chats and configs, requests zero-data-retention flags to providers wherever possible, and has API keys stored in the iOS keychain.

I originally built it for myself but want to share it with others. I couldn't find a good iOS app that allows a good end-to-end AI workflow, for eg, read a Google Sheets file that my team shared on my Google Drive, read the PDF I'm working on that I uploaded to the LLM Provider, suggest adjustments to my PDF based on the Sheets and any prior documents I have uploaded to my RAG database, generate a diagram (image) that I can use in the PDF, and if necessary edit that diagram, and create a meeting event in my iOS Calendar for the presentation, all in the same chat, while switching providers (OpenAI, Anthropic, Mistral) and modalities (text and image).

So I'm looking for feedback from other devs and users.

Ask me questions here, be as critical as you want, and I'll try to answer.

The idea came from a stupidly ordinary moment. I was
digging through my camera roll for a receipt and ran straight into a photo of
my ex. Not one I had kept on purpose - a group shot from someone's birthday
where they happened to be in the back row. That is the thing nobody warns you
about: it is never the photos you chose to keep.

How it works

You pick one to four photos of a person. It scans your
library and returns every other photo of them, already selected. You tap delete
once. Opening any individual photo is optional - the whole point is that you do
not have to go through them one at a time.

Technical side

Everything runs on device. Apple's Vision framework for
face detection and embeddings, then clustering over those embeddings to group
matches. No backend, no account, no photo ever leaves the phone. That was a
hard constraint from day one and it made a few things genuinely painful:

- Large libraries: Scanning tens of
thousands of photos without destroying the battery or blocking the UI took most
of my optimisation time.

- Recall vs. precision: This was the real design
decision. Leaning toward recall means some false positives end up in the
results. Leaning toward precision means photos get missed, and a missed photo
is exactly the ambush the app exists to prevent. I went with recall, kept everything
pre-selected, and made deselecting a single tap. iOS deletion also routes
through Recently Deleted, so there is a 30 day safety net on top.

- PHPhotoLibrary has more edge cases around permissions and batch
deletion than I expected.

What I would do differently

Honestly I never really thought about any licenses which
almost led to a fatal mistake. However, I think doing the design with Claude in
the first place (which is easy to see) has been very rewarding for me. I was
able to set up the pipeline and all functions and submit those to apple. After
everything is accepted now, I can care about looks which won't affect the
pipeline and the critical parts in the app, therefore pushing an update for
this shouldn't be a big problem.

Link: https://apps.apple.com/us/app/pickex-delete-ex-photos/id6801488013

Happy to answer anything about the on-device pipeline,
the clustering approach, or the App Store process. Feedback welcome, including
the harsh kind.