Does anyone have any tips or general advice for things to check before submitting a game to the App store?
I guess the obvious one is that it is not buggy but wanted to see if there is a checklist as such to check against before submitting it to prevent waiting a couple of weeks and then being rejected.
Thanks
Paul [import]uid: 7863 topic_id: 6925 reply_id: 306925[/import]
-
Make sure your description of the App is long and detail enough so Apple won’t think your app has minor functionality.
-
Icon size should be correct. (though you cannot pass the Application Loader if they are not correct.)
-
For iPad App, if it is not a specific orientation game, it has to support both landscape and portrait.
-
Make sure your App won’t cause memory leak.
Let me think if there are something else… : ) [import]uid: 4992 topic_id: 6925 reply_id: 24293[/import]
Thank you fedesign - that is very helpful.
My game plays in portrait mode only - does that mean I need to support portrait and portraitUpsideDown if I create a Universal Build?
With regards memory leak, are there any tools to check this or is simply a case of playing like crazy and checking that the game doesn’t crash?
[import]uid: 7863 topic_id: 6925 reply_id: 24379[/import]
Hi,
It would be better if your app supports both portrait and portraitUpsideDown.
It is pretty simple. Just add this in build.setting:
orientation =
{
supported =
{
"portrait", "portraitUpsideDown",
},
},
There is no specific tool to check memory leak yet, but you can use FPS and getInfo(“textureMemoryUsed”) to check.
Here is a good example :
http://developer.anscamobile.com/code/output-fps-and-texture-memory-usage-your-app [import]uid: 4992 topic_id: 6925 reply_id: 24412[/import]
Thanks again fudesign
I did some tests with the fps code and my min FPS remained on 30 throughout. The memory usage was approx 5 during game play and 11 on my splash screen that has a scrolling banner.
When I jumped between screens (I am using Director Class), it maxed out at about 18 for memory but then returned to 11 or 5 depending on where I was navigating.
Played for a while and seems to stick with these values so looks pretty promising on the memory leak front.
Cheers
Paul [import]uid: 7863 topic_id: 6925 reply_id: 24420[/import]