Can I upgrade a current DPS app to DPS 2015 once it launches? | Community
Skip to main content
W
Whylimes
July 9, 2015
Solved

Can I upgrade a current DPS app to DPS 2015 once it launches?

  • July 9, 2015
  • 2 replies
  • 1367 views

I have a few questions relating to the new DPS 2015:

1) Once DPS 2015 launches, would it be possible to take an existing DPS app and start using DPS 2015 for the next issue or do you have to make a new app from scratch? I have a few apps that I think would benefit from the new article-based publishing, but I don't want to lose the current readership in the apps.

2) Is there a Library in DPS 2015 or when you open the app are the cards the first thing a reader sees?

3) how does this affect the analytics with articles vs issues?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Neil_Enns_-_Ado

Hi Emily,

It depends on how you want to handle the existing app in the store. If you want to replace your existing app then you can use the folio migration tool in DPS 2015 to migrate all your old content over, create a new app, and submit that new app to the store to replace your old one. Your readers will get the new DPS 2015 experience but will still be able to access the old content (now as collections migrated to DPS 2015, rather than folios in the old app). This option is available for iOS at launch, and will work with Android and Windows shortly after.

2) There is no library anymore. Instead the reader sees browse pages and cards. You get to decide the structure of your app using browse pages and cards. If you want a simple view of what you used to have as folios, you just build a collection that has your back issues in it and do a layout/card you like to display them.

3) The analytics systems are separate. The new app will be a new analytics instance and will not have the data from your legacy app in it.

Hope this helps,

Neil

2 replies

BobLevine
BobLevine
Level 6
July 9, 2015

Moved to DP Solution forum.

Neil_Enns_-_Ado
Adobe Employee
Neil_Enns_-_AdoAdobe EmployeeAccepted solution
Adobe Employee
July 9, 2015

Hi Emily,

It depends on how you want to handle the existing app in the store. If you want to replace your existing app then you can use the folio migration tool in DPS 2015 to migrate all your old content over, create a new app, and submit that new app to the store to replace your old one. Your readers will get the new DPS 2015 experience but will still be able to access the old content (now as collections migrated to DPS 2015, rather than folios in the old app). This option is available for iOS at launch, and will work with Android and Windows shortly after.

2) There is no library anymore. Instead the reader sees browse pages and cards. You get to decide the structure of your app using browse pages and cards. If you want a simple view of what you used to have as folios, you just build a collection that has your back issues in it and do a layout/card you like to display them.

3) The analytics systems are separate. The new app will be a new analytics instance and will not have the data from your legacy app in it.

Hope this helps,

Neil

Terms & ConditionsAccessibility statement

Loading footer...