Yes, they need to EXACTLY the same...
The reason for this is to not create user confusion (as stated in the docs).
It's not best to make sure - they should be the same no matter what or else you will get rejected (if you're not extremely lucky)...
As for the release-date thing... You can choose to release whenever you want to (after you app been approved) but if you want to show up in the latest release date list you need to go for the date that apple approved your app...
That's not quite right actually, they don't need to be "EXACTLY" the same. The iPhone HIG (which of course everyone's read right??) has this to say about the icon:
When you submit your application, you must include a 512 x 512 pixel version of your application icon for display in the App Store. Although it’s important that this version be instantly recognizable as your application icon, it should be subtly richer and more detailed. In other words, you should not simply scale up your application icon to create an icon for the App Store.
Here's a link to the page - there's plenty of other useful information in there, definitely worth looking through...
That's not quite right actually, they don't need to be "EXACTLY" the same. The iPhone HIG (which of course everyone's read right??) has this to say about the icon:
When you submit your application, you must include a 512 x 512 pixel version of your application icon for display in the App Store. Although it’s important that this version be instantly recognizable as your application icon, it should be subtly richer and more detailed. In other words, you should not simply scale up your application icon to create an icon for the App Store.
Here's a link to the page - there's plenty of other useful information in there, definitely worth looking through...
And naturally when I say exactly the same I do not mean pixel by pixel (since the bigger one got a couple of more pixels to use) - so of course the bigger one will allow for more detail and will be richer...
But this is not the same as having different backgrounds in the icon itself...
In that sense they need to be the same - like you said, they should be instantly recognizable - they should be the same... If you for instance add a text to the large icon that you don't include on the small one (perhaps thinking it's to small and unreadable and therefore you remove it from that one) - then you will get rejected for that...
Just saying they need to be the same - to help people from getting unnecessary rejections since one can interpret the HIG differently... One could think that "recognizable" would allow for some leeway in the appearence of these two icons - and well, it doesn't...
Hence, they need to be exactly the same...
One of our apps has, just as you mention crabFish, the larger 512x512 icon with a little bit of text that the 57x57 one doesn't. However, it hasn't been rejected (although I'm aware it could be).
I think common sense prevails sometimes at ReviewHQ. If all the larger version says extra is a discreet 'v2 - Extra Effects', then they may let it go. They have with my last 3 updates anyway!
One of our apps has, just as you mention crabFish, the larger 512x512 icon with a little bit of text that the 57x57 one doesn't. However, it hasn't been rejected (although I'm aware it could be).
I think common sense prevails sometimes at ReviewHQ. If all the larger version says extra is a discreet 'v2 - Extra Effects', then they may let it go. They have with my last 3 updates anyway!
Well, I guess it's like everything else in the review-process... Sometimes some people get away with it while others don't - I've had a rejection based on the same scenario that you describe is working for you...
That said - you can always go in afterwards and change the large icon, so if someone doesn't want to risk having to wait an additional unkown time because they got rejected, I would suggest using that approach... Use the same icon when submitting the binary, change the large one after you get accepted...
It is better for all of us if people don't get rejected for small unnecessary things since each rejection adds upon the load of the queues - and thus the time we have to wait to get accepted (or rejected)...
And naturally when I say exactly the same I do not mean pixel by pixel (since the bigger one got a couple of more pixels to use) - so of course the bigger one will allow for more detail and will be richer...
eh??
Yes of course the bigger one will allow for more detail and will be richer which is why Apple clearly state it can be so in the HIG.
But I don't see how your comments:
Quote:
Originally Posted by crabFish
Yes, they need to EXACTLY the same...
and
Quote:
Originally Posted by crabFish
they should be the same no matter what or else you will get rejected (if you're not extremely lucky)...
in any way reflect that point, hence my previous post.
But in future, when I read the words "EXACTLY" (in caps) and "the same no matter what" I'll just assume it means "will allow for more detail and will be richer"...
But in future, when I read the words "EXACTLY" (in caps) and "the same no matter what" I'll just assume it means "will allow for more detail and will be richer"...
Good to know we got that one straightened out then
I've taken that to mean that one should scale the big icon down, and not scale the small icon up. Which is, of course, a bit condescending on Apple's part, but not out of character.
I'm still waiting for my Enrollment thing to be accepted, then my app will go up the same day i get it. So far enrollment has taken 3days, but should be complete in a couple of days.
My csBingo app has the whole stupid chicken for the 512 and just its head for the Icon but you can tell it's the same stupid chicken and they didn't reject it.
i have lite version of my app that uses a few sounds from my pro version, the funny thing is, they rejected the lite version for the following reason
Quote:
Thank you for submitting Sound Effects Lite to the App Store. We've reviewed Sound Effects Lite and determined that we cannot post your application because it appears to contain features, namely, sound clips, that bear a resemblance to a well-known third-party trademark.
Please remember that pursuant to your agreement with Apple, you represent and warrant that your application does not infringe the rights of another party, and that you are responsible for any liability to Apple because of a claim that your application infringes another party's rights. Moreover, we may reject or remove your application for any reason, in our sole discretion.
Please confirm that you are in compliance with the iPhone Developer Program License Agreement. Or, if your application may not be in compliance, and you are able to make the necessary changes, we encourage you to do so and let us know.
At long last I have my first app "Memory Commander" on the store. I submitted it on the 4th October and got approved on 16th October. Apple made it 12 days.
__________________ Top1000 Rankings for your App on - APPlyzer Daily Rankings now for FREE / Get now iPad daily and hourly rankings and app reviews from all app stores
Your app will be up until MGM or the estate of Stanley Kubrick notices it.
Hi,
It's been up for over a year & the app is free so I don't think anyone minds. Search the web for hal 9000 eye and you'll find it being used all over.
Of course if they have a problem with it I won't object.
Linear Mode
