As an iOS developer, what do you think about the Apple review process? Would you prefer to have no review and immediate submission of the app to the market (like Android), or you find the review useful?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple review process
- Thread starter parnian80
- Start date
- Sort by reaction score
I think it's overall a good thing, it keeps the worst of the crap out of the store.
On the other hand I don't like that there's a lot of stuff we can't do. And the delay is frustrating at times - especially if you discover a really nasty bug that's leading to lots of bad reviews, and it takes you about 30 seconds to fix it plus a week of waiting and watching your ratings drop!
I think they should have some kind of trust system or something. Devs that have released 5 apps get a fast track where they just check the basics (which are probably automated anyway).
On the other hand I don't like that there's a lot of stuff we can't do. And the delay is frustrating at times - especially if you discover a really nasty bug that's leading to lots of bad reviews, and it takes you about 30 seconds to fix it plus a week of waiting and watching your ratings drop!
I think they should have some kind of trust system or something. Devs that have released 5 apps get a fast track where they just check the basics (which are probably automated anyway).
Comeagain?
macrumors 68020
As an end user, I like it. I'd rather wait for the bug fix then get all the crap that would get through otherwise. Maybe if there was the option to mark the app as a critical bug fix that could be fast tracked, and put a limit on the number of times you could use that option.
As an 'end user' I guess you're rarely aware of the downside of apple's restrictions. Overall I do agree with them, but sometimes they do work as a bit of a roadblock.
An example from my own work: I write camera apps. Apple give us *very* limited access to the camera, and we can't do a lot of basic stuff as a result. Simple things like setting the exposure and ISO on the camera - this would be incredibly useful, and would mean we can write *much* better camera apps. But those apps can't be made, so they don't exist and you don't know what you're missing. 🙁
Well, actually I DID make an app with manual exposure control, and the improvements over the native camera app in low light are pretty spectacular. But I had to use a workaround to do this, and it's extremely limited. I could do so much more with direct access.
An example from my own work: I write camera apps. Apple give us *very* limited access to the camera, and we can't do a lot of basic stuff as a result. Simple things like setting the exposure and ISO on the camera - this would be incredibly useful, and would mean we can write *much* better camera apps. But those apps can't be made, so they don't exist and you don't know what you're missing. 🙁
Well, actually I DID make an app with manual exposure control, and the improvements over the native camera app in low light are pretty spectacular. But I had to use a workaround to do this, and it's extremely limited. I could do so much more with direct access.