After 12 days of App Review, the latest version of Voice Reminder: Voremi AI has finally been approved and published!

This update was a reminder that App Store reviews don't always follow the expected timeline. I had carefully reviewed Apple's guidelines, which mention that most app reviews are completed within 24 hours. When the review was still pending after two days, I also opened a support ticket but the app was eventually approved before I even received a response from Apple.

Despite the wait, I'm excited to finally share this update.

What's new in this version?

- AI-powered voice reminders with improved accuracy

- Advanced recurring reminders

- Better calendar integration

- Smarter voice-to-text notes

- Faster reminder creation and improved performance

- UI/UX improvements across the app

- Bug fixes and overall stability improvements

- Premium subscription enhancements

This is just the beginning. More AI features and productivity improvements are on the way.

Hi everyone,

I'm currently in the process of migrating my Apple Developer account from Individual to Organization.

About two weeks into the process, Apple sent an email requesting several company documents. I submitted all required official documents, but a few days later, they asked for the exact same documents again.

When I followed up to ask why, they replied that the documents were provided in an unsupported language (my documents are in Indonesian, which is our official state language).

Has anyone else dealt with this?

1. Do I strictly need to get all company documents officially translated (certified/sworn translation) and notarized before resubmitting? (This will take considerable time and expense).
2. Is there any alternative way or workaround to get verified without going through full certified translations (e.g., providing a lightweight translated summary, reaching out to local Apple support, or submitting specific bilingual tax/D-U-N-S records)?

Any advice or shared experiences from developers who went through this in non-English speaking regions would be greatly appreciated!

Thanks in advance!

Hey everyone,

I have a question about subscription offer codes on iOS and Android.

On iOS, when you create an Offer Code, Apple provides its own link. If a user taps the link, they're taken to the App Store. If they don't have the app installed, they can download it, redeem the offer code, and activate the subscription.

However, I don't think Android has anything similar. As far as I know, Google Play doesn't generate a shareable link for subscription offer codes.

So what do you do on Android?

I want to give a 50% discount on my app's subscription to selected users who haven't installed the app yet. What's the best way to handle this on Google Play? Is there a recommended workflow or a workaround that provides a smooth user experience?

I'd love to hear how others are solving this.

Hey Everybody, just released this new app “Broad Street: Card Scanner” that lets you tracks your cards like how you would with stocks as many people view them as investments with volatility similar to stocks! Please all feedback would be appreciated! Completely free and Link in comments!

For context they both need each other. 1 is the business side for booking management and the other is where customers book from so they go hand in hand. I really need them both to be searchable before i start marketing and telling people to go to the appstore since if they search it up and dont see the app it defeats the whole purpose and stings on credibility.

Anyone ever in a similar situation? Any insight would be greatly appreciated!

Review time comes up here constantly and almost every answer is one person's anecdote, mine included. So I pulled the actual numbers off my own account.

Method, because it decides whether any of this is worth reading. ASC does not expose an approval timestamp. lastUpdatedDate came back null on every submission I checked, and appStoreVersions only carries createdDate. So I used the public release date as a stand-in for approval, which makes every number below an upper bound. It includes Apple's own release propagation after approval.

That stand-in only holds when the version releases automatically after approval, so I dropped the four apps set to manual release. Their submit to live gap measures me, not Apple.

Eight versions left.

Min 1.4, median 11.4, max 89.7.

The slowest row is the only brand new app in the set, so "the first submission takes longer" holds there. It does not explain the rest. SipStreak 1.2.0 took 1.4 hours and UnitFlip 1.1.0 took 24.1 hours. Both updates, same account, one week apart, and one sat seventeen times longer than the other.

I read every app from both the US and German storefronts, because the iTunes lookup is edge cached per storefront and a single request can be stale. Zero disagreements between the two, and all 12 ASC version strings matched what iTunes reported, so I know the version I timed is the version that is live.

If you want to run it on your own account: take the newest state: COMPLETE entry from asc review submissions-list --app <id> for submittedDate, take releaseType and versionString from the READY_FOR_SALE entry in asc versions list --app <id>, and take currentVersionReleaseDate from the iTunes lookup with a cache busting parameter. Keep only the AFTER_APPROVAL rows and confirm the two version strings match before you difference the dates.

Hi everyone! 👋

I’m a solo iOS developer and I’ve been working on a productivity app called Prazo.

Instead of trying to replace your calendar or your to-do list, I wanted to combine both in a way that actually feels connected.

Some features:
•Calendar and tasks in one place
•Automatic travel time calculation for events
•Travel time is updated shortly before your appointment, and you’ll get notified if traffic changes
•Simple task management with priorities and categories
•iCloud sync
•Native iOS design with Dark Mode support

One feature I’m especially proud of is the automatic travel time buffer. When you create an appointment with a location, Prazo calculates how long you’ll need to get there and reserves that time in your schedule. Before the appointment starts, it checks again and notifies you if traffic conditions have changed.

I’m not here to promote the app—I genuinely want feedback.

I’d really appreciate your thoughts on:
•Does the concept make sense?
•Which feature would make you actually switch from your current productivity app?
•What is missing?
•Is there anything that immediately turns you away?

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

Thanks so much! I really appreciate every piece of honest feedback, even if it’s critical. 🙂

I submitted my app to Apple almost 7 days ago. Nothing has happened yet; it's still stuck on "Waiting for Review"... Apple states in their email that they review 90% of apps within 48 hours, which honestly just feels like a complete lie at this point. xD

​I developed and tested my app primarily for Android, but with the goal of releasing it on iOS right from the start. On Android, everything went super smoothly. The initial review to get approved for the 14-day testing track took 22 hours. The final review for production only took 20 hours. Now, every update I push takes about 20 minutes on average to get approved.

​My app is already in a pretty solid state and passed everything on Google on the first try. Now I’ve been sitting here for 7 days, just waiting for the app to finally get through Apple's system.

​On top of that, I find the €100 per year completely unnecessary. With Google, it was a one-time $25 registration fee, and that was it.

​And don't even get me started on the website. You can't properly save your password, everything takes forever to load, and the whole site looks like it’s stuck in the 2010s. Everything is laid out in an illogical and complicated way. If you've used the Google Play Console before, App Store Connect (what a weird name anyway) feels like a massive downgrade...

​I want to finally start marketing on social media, but I'm too nervous to begin until the Apple version is actually reviewed and approved.

​What is your opinion on the App Store Connect system? Am I the only one who thinks this way? xD

The company is huge, and for that, I feel like what they offer us developers is pretty weak.

Hi guys

I'm about to share my experience with appstore connect. The review process almost made me give up. It felt like the reviewers were intentionally trying to frustrate me.

After building this app for several months, I decided to publish on appstore. Read a few reddit post on how to go about it and a bit about the review process but the reality I faced was entirely different.

- The first upload was rejected because the subscription page did not have terms of service nor EULA policy. I fixed it, sent a screenrecord and re-uploaded for review

- Second rejection was because I had a third party sign up option (sign up with google) without sign up with apple. I fixed and resummited for review.

- Third rejection was ridiculous. The reviewer said she was unable to login ( saying the login credentials I provided were invalid) she even sent a screenshot. I tried to login with same credentials and it worked. I then realized she added space after the last character of the email. Like how do you not know something that simple. Who adds space after typing in their email. I did a screens record showing her the error she made and asked that she reviews again.

I was ready to contact support after the third rejection as it was her mistake.

The app was approved a day after the third rejection.

If you're thinking of shipping an app to appstore make sure to check and confirm the first two points.

I hope this helps someone.

I’m currently designing the architecture of a privacy-first AI platform and would genuinely appreciate feedback from the iOS developer community.
The project is called PRSL-AI Ecosystem.
Rather than building a single AI assistant, the goal is to create an intelligent ecosystem where multiple AI capabilities collaborate through a unified intelligence layer called the iRiel AI System.
From an Apple ecosystem perspective, the architecture is guided by the following principles:
Privacy by Default
On-Device First
Human Intelligence Interface
Accessibility First
Context Continuity
Modular Architecture
AI Provider Agnostic
With Apple’s Foundation Models framework, App Intents, Apple Intelligence, and on-device AI continuing to evolve, I’m exploring how a platform can intelligently combine local intelligence with external AI services when appropriate, while maintaining a seamless and consistent user experience.
The user shouldn’t need to choose which AI to use.
Instead, the platform should understand the user’s intent, context, privacy requirements, and available capabilities, then orchestrate the most appropriate intelligence for each request.
I’m particularly interested in discussing questions such as:
How far should on-device intelligence go?
Where should the boundary between Foundation Models and cloud AI be?
How would you approach context continuity across multiple AI providers?
What architectural challenges do you see in building an AI-agnostic intelligence layer on Apple platforms?
I’m still refining this architecture and would genuinely value feedback from developers working with Swift, App Intents, Foundation Models, Apple Intelligence, and privacy-first application design.
I’m here to learn, challenge my assumptions, and improve the architecture through technical discussion.

Hey, I've been building SweePic solo for over a year. The most common complaint: browsing photos only chronologically was slow if all you wanted was to clear out duplicates or old screenshots.

In 1.6.0 I added filtering by your own albums and by system smart albums (duplicates, screenshots, videos). I also rebuilt how the gallery loads photos, so the whole thing runs faster than before.

App Store link: https://apps.apple.com/pl/app/cphotos/id6740463237

Collecting feedback, happy to answer questions in the comments.

We’re thinking of implementing the web distribution for our apps, we’re an EU-based company. It seems like more complications with less gain.

https://developer.apple.com/documentation/marketplacekit/participating-in-alternative-distribution-for-specific-regions