Bob,

Other than technical, are there any "empirically" known limitations, a sort of "unofficial", that you are aware of, or at least suspect?

My team is working on a book (interactive encyclopedia), which has roughly 30 interactive objects: 3D images, short audio/video clips, slideshows, etc. The full size is 664 MB, and there is about 100 articles, 10 to 30 pages each. About 2-3 weeks ago it started causing Adobe Viewer (always updated to the latest) crash on load or while browsing. It happens "almost always" in iPad 1, "pretty often" in iPad 2, and "noticeably often" in iPad 3, even with the best running conditions. Sometimes the Viewer crashes so badly, that the book cannot be opened anymore, and only reinstall and re-download can help.

I am specifically asking you: how can I submit this work to Adobe experts for analysis and advice, what specifically in our design, layout or size is causing the problem? I don't see a point to look for Adobe's flaw, I think there's an invisible border that we crossed and now need to get back to a safe zone.

Help???

Bob,

We have creative cloud account, and it appears Adobe added Single edition there just in time when we finished and started testing. I am now setting everything up to generate an IPA, but if it has the same behavior (which I expect, after reading through this forum), what can be our next steps?

Is there a process to request support in cases when certain creative ideas are expected to work with DPS folios, but in fact they do not? When platform does not behave as expected from documentation?

I understand we may end up sacrificing iPad1 compatibility for our product. This is a pretty bad outcome, but not as bad as the failure of the whole concept of creating rich multimedia reference for iPad with DPS - that would be a real disaster.

I still need to understand how can we optimize our product to make it stable with iPad2. Is any help available for that? Is there anyone at support@adobe.com or elsewhere to take this case?

Still need help.

Bob,

We created .IPA files and it behaves pretty much the same as Content Viewer:

- With the small number of articles (about 30, some having up to 30 pages), it is stable even on iPad1, just a bit slow to render new pages with random browsing.

But once we added more articles (the target is 150+ as this is the size of content we publish), at some point the app started crashing on both iPad1 and iPad3. The same is for the Content Viewer on iOS.

I understand your concern as a reader, regarding lengthy articles (your earlier post in this thread). We created a secondary navigation UI to ensure every page in every article can be reached with no more than 3 taps, so it is supposed to be read in a WebSite-alike fashion.

But, technically speaking, there seems to be a barrier that we are not aware of. This barrier prevents from creating complex and content-rich folios, as good as books created with Apple's iBooks Author. and possibly better.

Given the lack of definite answers on this particular matter, I started to doubt: is Adobe really interested in supporting folks creating  publications like multimedia references with this product?

If it appears that DPS/Folio is only suitable for simulating printed glossy magazines and corporate catalogs, than we might have chosen a wrong tool for the job

But I still hope to get helped...

Anyone???