Can you give some more details on what you mean by “advertising advertising advertising”? What part of the card or banner being HTML will you use for that?
If you want to message subscriptions, are you expecting the card to change state or visibility based on the reader’s subscription (or sign in) state? If so, how?
Looking to implement HTML banner ads, possibly video, and either cards or banners to work within browse pages. Things like Newsletter sign-up, bespoke events at short notice (eg: Check Out This Issue!), advertising, promotional content. Would like to show different content based on users' profiles - subscriber info, one time visit, previously bought an issue, new customer, etc. using the DPS token.
It should also support the API calls that are used in banners produced with the Store Configurator (open/buy issue, preview issue, open sign in dialog, subscribe, etc.)
Can you confirm if this has been actioned yet? I am looking to create a banner that displays to non-entitled users and a second that would only display to entitled users - can you advise if and when this might be possible?
The ability to create HTML based cards in AEM Mobile (formerly DPS 2015) is on the product roadmap. I can't provide a ETA, but the goal is to have something released by late Q3 or early Q4 2016. Of course this depends on a lot of factors and the release date is subject to change.
Neil, we (Bates Creative), are highly interested in this feature, primarily for our existing publication clients, who are looking to have dynamic browse pages that entice users to revisit the app more frequently. The use of HTML cards would enable us to keep a fresh look within a few cards on a browse page, ticker-tape type treatment to inform users of continuous updates, without the use of opt-in push notifications. They would truly help to maintain a fresh look on browse pages.
Another thing we'd like to do with HTML banners that came up in a strategy meeting today, is to be able to offer a latest social media feed on a card, to keep a browse page more dynamically updated, encouraging more frequent visits to the app. We could feature a tweet, pull and image and title from a latest blog post, or Facebook post... Just the use of social media would be HUGE on HTML Cards.
Also, w/ HTML cards, we could potentially offer rotating features by reading from a data table that could potentially allow us to specify the Image, Title, and (hopefully) Navto options on given card, so we could have rotating stories (date based???) on one card. That would be amazing!
These are good suggestions. I'll make sure to discuss these with the Engineering team that is developing the HTML Cards feature.