| ▲ | joenada 6 hours ago |
| Your assumptions are very outdated. App Store review times are typically < 24 hours and have been for the last couple of years. And KMP makes cross-platform a real thing now, rather than hacking a web view into a native shell, which was always the worst possible user experience. |
|
| ▲ | joshstrange 5 hours ago | parent | next [-] |
| I'm afraid you are the one out of date here. App Store Review times have ballooned in the last few months. Marco Arment talked about this publically (on the ATP podcast) about how his app was stuck in review for over 2 weeks IIRC and I've seen 2 days as the minimum review time in the last few months with some taking a week or more. Yes, for a while they were doing very well and I even once had an app reviewed in <1hr but the average has been creeping up. LLM/Vibe coding is what is often blamed for this increase though at the end of the day it's Apple's problem/fault for not staffing the review department better. |
| |
| ▲ | joenada 5 hours ago | parent [-] | | This is only anecdotal, but I had a review on a brand new app turned around in ~6 hours 2 days ago. A lot of it has always been luck of the draw, though, granted. | | |
| ▲ | joshstrange 5 hours ago | parent | next [-] | | I agree it's anecdotal but that's all I have to go off and global averages don't help me at all. The problem it's a complete crap-shoot. You have no way of knowing if you are going to get a quick turnaround or a long one, it has zero bearing on if it's a new app or update or the size of the update, it's completely random. I cannot plan around random which is why I've opted for web-tech-based apps (Capacitor) with OTA updates so I can get fixes out just as quick as I could get webapp updates out. I just ran an analysis of my apps and the fastest was 8hrs (June 20th) but since then it's been trending upwards with my last 3 updates coming in at 40hrs, 67hrs, and 98hrs. These are all my apps, the company I work for has at least 2 recent updates that took over a week. That's just absurd. If the App Store can commit to 24hrs being the max time then maybe I'd be interested but for the foreseeable future I'll "Settle" for instant updates when I have a fix ready instead of waiting on Apple. Especially with how random approvals are (not just the time, the approval itself), I'll ship a tiny fix and App Review will kick it back for some native API I've been using since version 1 that they now want more info about. I don't fancy having my businesses at the whim of Apple Review. | |
| ▲ | ceejayoz 2 hours ago | parent | prev [-] | | It's also dependent on when you file. My reviews seem to come back around 2-3 AM Eastern; I presume they're overseas contractors. |
|
|
|
| ▲ | ftchd 5 hours ago | parent | prev | next [-] |
| Apple has started automating them a while ago so a lot of them are indeed <24 hrs. I wouldn't say they are wrong though. Just this week I've had an app stay for 9 days in review and another one for 8 hours. Same dev account, same niche. |
| |
| ▲ | manmal 4 hours ago | parent [-] | | When it takes longer than 36h, just revoke and submit again. It's probably just stuck in some queue. | | |
|
|
| ▲ | paulryanrogers 5 hours ago | parent | prev [-] |
| Doesn't KMP assume your team is comfortable working in Kotlin? |
| |
| ▲ | joenada 5 hours ago | parent | next [-] | | Yes, that's fair. I'd argue, though, that the training required to get your team up and running should be fairly minimal - Kotlin is a very easy language to pick up, especially for people coming from TS - and will pay off dividends in the medium to long term. | |
| ▲ | mike_hearn 5 hours ago | parent | prev [-] | | Well, it assumes the model is. KMP can be seen as a token optimization at this point. Business logic is shared and doesn't have to be rewritten in Swift. |
|