This might be too much to bite off; however, I'm evaluating the feasibility of quick migration from DPS classic to AEM Mobile with the initial goal being a simple lift-and-shift to the new platform. This would provide quick migration now, while enabling expansion of AEM Mobile features in the future.
Creating an app and migrating content is quick - I end up with virtually the same layout as DPS classic storefront, being a collection of folio covers. This is perfect.
But where I could use some guidance is translation of custom storefronts. We have many apps which feature custom storefronts, where we have leveraged entitlement banner carousels, promotional content based on entitlement, subscriptions, and cross-sells within our store by using the Library and Store SDK.
It seems that AEM Mobile has two approaches for extensibility:
Custom content created as HTML articles in cards
Extending the AEM Mobile app using Cordova
As a mobile application developer, it's easier for me to wrap my head around extending the AEM Mobile platform through Cordova; however, it appears tutorials are geared towards customizing content.
Thanks, Ivan - this sounds like exactly what I was looking for.
So, using the Content Map, I would make the Top Level Collection an HTML Article that contains my custom code for carousels?
Not entirely sure I understand how a user would navigate to sub-collections. Using this approach, a user would have a promotional screen; then, have to switch to a different top-level collection to view articles, right?
Thanks for this insight, this approach is very feasible.