Hi Espen, thanks for the feedback. Note that the new DPS 2015 viewers take user into the article view right after tapping to view it, even if it hasn't been downloaded from the service, compared to the existing DPS product, which blocks access until some subset of articles have been fully downloaded to the device.
We have been making some performance and usability improvements to more effectively communicate progress to end users so it doesn't feel slower, and are also evaluating the explicit download feature (which is covered in other forum posts).
I have an idea that the custom Nav (that currently does not work in the publish environment) is causing an issue leading to excess render time (not loading time). I am planning to make a new version of the app that does not have this feature to see what impact that has on the speed. I cannot do that until Monday however when I am back in the office with my developers.
Because these are migrated folios and not folios created with the new set of API's for Publish then I know they may not be optimised as well as they can be. However for various reasons (namely cost and time) we are unable to integrate our CMS with new workflow for at least six months. The publishing plan for now is to continue to Publish via DPS classic and then migrate those folios into the new environment (does that make sense?).
Is it not possible to re-route some developer support through another office, Bucharest perhaps, I know they are mainly focused on the UI/UX but maybe they have limited dev support?
Considering we only have a few weeks left now until launch, waiting a week before a response (and expecting my team may have lots of work to do to fix any potential problems with migrated HTML) it is really eating into our timeframe.
We are using HTML articles rather than INDD based articles. These are created in a CMS (Umbraco) and then published via the DPS classic API. We then migrate this content into the new DPS Enviroment.
The pages are quite slow to load but worryingly the render time is even longer. Once the page has loaded the screen appears to be grey while the HTML renders. However its typical to wait between 7-20 seconds per article. For a 200+ article edition this is a huge problem.
I know you are constantly upgrading performance but we are still unable to test. Adobe have recommended we start to submit viewers soon to Apple for review but this will be impossible without prior testing. Do you have a definitive timeline for upgraded prior to launch?