I had a similar problem - At least on mine, the layout template is basically an approximation of the final product. The fonts on the layout preview display about 30% smaller than the app and the margins / paddings are nowhere close to the final app's display. I just kept using the live App to judge ...

Some extra details from Adobe Support:I have tested this several ways including directly in the desktop browser and it always loads the video with the "Auto" setting for quality. I'm not sure how that is selected by the youtube service (depending on browser/device or whatever parameters) but it alwa...

I am using HTML articles with youtube embeds. Overall, the videos work, but they are fixed on the default low def versions. As some of these are set to play full width in my App, they don't look as sharp at all. The original videos are full HD. • I have included the high rez parameters with the embe...

Rebuilt, downloaded and signed the new app, but It appears I never actually re-installed. it. *facepalm*

I have some custom fonts that aren't showing up in my display app. I have uploaded both WOFF and TTF versions through the AEMM interface. They show up in the font selection list and display in the layout/card construction area perfectly. But when I view the development app, I only get the default fo...

Oops - Yep - That was it - I had eliminated some older collections and forgotten that the top level wont display that view. Everything working as it should now. Thanks!

I should specify, The Collection lets me change to Browse Page, and saves, but the change never "takes" on the App.

I'm having a problem in the collection properties settings since the switch to AEM. Iam finishing up a development application - I just finished creating the layout, but I cant get the "Collection Open Default" to function as Browse Page (Show Cards. layouts etc). It remains forever stuck on Content...

The @font-face call from CSS worked just fine for offline reading when I linked to local font files  - which I included with the other assets when generating the HTML article.

Note: I meant "set to content page",  not browse page. Big difference there.