Let me preface this by saying that this app is IMAGE HEAVY. The graphics are an integral part of the experience. Here's the feedback I got for the rejection of the first version of the app: 10.1 We found that your app includes full screen transitions. The iOS Human Interface Guidelines state that individual views and objects should be transferred or animated instead of the entire screen. For more information, please review the section, "For iPad: Reduce Full-Screen Transitions" in the iOS Human Interface Guidelines. 10.6 We also found the following issues with the user interface of your app: - Portions of your app loaded, refreshed, ran, and responded very slowly. For example, when we tap on an option and return to the "Home" screen content takes time to load. The app is also generally slow to respond. - Did not include iOS features. For example, it would be appropriate to use native iOS buttons and iOS features other than just table views, and consumable content. I have been using image URLs instead of loading them into the system. I would like to know 1. if this is the most efficient way to display graphics in the app, and; 2. What other recommendations you have for making the app move faster? Thanks in advance!

Hey Mate! So there are a few options. Basically long story short. To make an app image appear faster it has to be embedded within the App. I assume you are using HTML pages here... if not, what is below, applies to the same for any image (if its embedded, its quicker to load) Options are (in terms of speed): 1. Embedded HTML Doc with embedded image 2. Custom HTML Doc with embedded image 3. Custom HTML Doc with online image So in your case you are referencing Image URL's. So this means it will depend on two things, the users internet connection (I believe apple test on WIFI so this isn't a problem) and also the speed of the server which you are retrieving from (i.e the URL). So basically, to have an image imbedded within the App means you have to have a copy of that image (I suggest using .PNG) in the BT_Images folder within xCode. Keep the naming simple. E.g. 'pictureone.png'. I assume you are using a Custom HTML page. This means the HTML which references the image is online but the image will be within the App. Custom HTML (online) is good if you will be updating this page often. If not, use a normal HTML page. To do this, create a HTML document and chuck it into BT_Documents folder in xCode. Within the HTML Page Plug in, just reference this document. Once again user lowercase naming conventions with no numbers. So this may seem like a bit of jumble... sorry to confuse. In my case (http://itunes.apple.com/app/aus-visa/id556424470?mt=8) - not trying to advertise here, just showing an example. Scroll to the screen shot with "Algeria". As you can see for this type of app the information can change at any time, but the image (unless an all out war occurs) the image will stay the same. So, for this I have used a Custom HTML with an embedded image. The code is: <h1 style="text-align: center; "> <font class="Apple-style-span" size="3"><img align="middle" alt="" src="CAlgeria.png" style="width: 150px; height: 150px; " />&nbsp;</font></h1> (Note inverted commas are removed on this forum) As you can see my image name in xCode is CAlgeria.png. Also to note, the online HTML editor will not display the image (as it doesnt have access to it) but if its chuck into xCode and compiled you should see it :). Likewise, with an embedded HTML document, all the same happens just it access the HTML code within the app and does not have to contact a server somewhere. If this is not for a HTML plug in (/sigh), then where you reference an image, simple use the same name. I.e. CAlgeria.png, within the field name in the control panel. ...phew. There is my spill! Any questions let me know.

holy s..., that what quite a chuck of text. Sorry!

Hi @tgnmpr Something else that might help. The rule is that the smaller the image file sizes, the faster they load. I don't know if you have optimised the images you use but if you make them about the size you need (e.g. 320x480 for iPhone and 768x1024 for iPad), that will help. Next, jpg files are compressed and probably faster to load than png, so make sure your images are in the most appropriate format.