I have received complaints about our last iPad 3 issue, which we created in PDF. It's about 600MB on the iPad 3 and users experience delays on swiping and page rendering. One user indicated that the folio is unreadable after a few minutes even following a reboot of the iPad and only opening the magazine.
Any clues here?
How are you creating the layouts for the folio? Are they blank InDesign documents where you are going and placing individual design elements? I realize this may sound like a silly question, but it helps us understand how the PDF folios were created.
Also, are you seeing this problem on your iPad? Or is it just from a handful of customers? Is it perhaps because users are swiping on interactive elements and that prevents navigation to the next stack?
Neil
We have the same problem. We normally start with iPad masterpages with basic information, like font formats. We see this only on one iPad3, but thats maybe because we just have one at the moment :-) It isn't because someone tries to swipe on interactive elements. it's for example on a picture and you like to swipe to the next page. If it's usefull we could provide the document or share the folio with you.
Hi Michael,
Yes, we've seen the video and we have a copy of the June issue (those planes are crazy cool!). I do see the occasional delay when swiping. I'm trying to understand how the files are created to see if we can make sense of what's causing the occasional delay. Thanks for the info, I'll chat with our engineering team.
Neil
Hi guys,
recently my friend has bought a new iPad 3 and has had a few problems with it which are discussed on many web sites these days. However, he asked me to try to find out something about one particular issue that is annoying for him. He is also having these problems with PDFs. They open/load up very slowly compared to the iPad 2. The problem occurs especially when he receives a PDF as an e-mail attachment. In my opinion it takes ages compared to the ussual speed at which apple products operate generally speaking. In the course of my investigation, I have stumbled accross this discussion. Obviously, this is the right place to talk about this issue.
Having said all this, I wanted to ask you wheteher there has been any progress in this matter (last post was on 20.6.12). Anything would be useful. Hints or directions as for how to overcome this problem (maybe Adobe isn't even supposed to make any changes) will be very much appreciated.
Many thanks in advance.
Marek
North America
Europe, Middle East and Africa
Asia Pacific