Hey Steve;Bob and I took a look at this, tried to replicate it, but
didn't observe what we understand you're seeing.On an iPhone, an iPad,
and Android tablet -- all show similar interactions of transparency. The
notable differences have more to do with brightness of the
device.Something we're not completely clear on is where you expect to
see card transparency.Certain properties of a card can be transparent:
card background color, image tint, and text background color support
this.Text is opaque...
Read Bob's message again, carefully.If you intend to have different
articles and organization for phone and tablet, you'd want two
top-levels.If you're building different phone and tablet, pixel-perfect
content, you'd want two top-levels.If you want the same content and
organization on both phone and tablet, one top-level will make things
easier.If your content is HTML-based with good CSS, it can adapt to both
phone and tablet, and one top-level is great.If your content is
pixel-perfect and you ...
Hey Taina;I have engineering looking into this. They're trying to find
an S5 to test with, we tried a S6 and it received the phone rendition.
I'll let you know what I find out.BTW, your technique of adding a
collection and using different card designs calling different metadata
is quite clever. Nice technique.
All suggestions above are good, although some of the AirPlay-like will
require being on a common wifi network AND subnet. And that can be
challenging sometimes.OTOH, for the big screen you may have a switch for
inputs, then you could use an adapter that connects the iOS device to
the projection system. If you do that, I'd tape the adapter to the
device--wiggling wires can be an issue.
Taina -- thanks for splitting this question off.I did a really quick
test with my iPhone 5S and a Motorola that has dimensions that match the
Galaxy S5 -- they both see my phone layout rendition -- I think that's
what you expect.So you have two apps in one project -- cool, they both
see the same content.-- The card images will be the same since all
content is the same.-- May I assume you have one top-level?-- -- If you
have two-top level and different phone and tablet collection structures
Hey Bill;I think you're describing some of the navigation features we
had in the original DPS. The scrolling navigation through articles in a
folio isn't part of the newer product. I suspect it comes down to a
folio had information about all the articles that were in it, whereas a
collection is a more flexible container and doesn't carry the
information that would support scrolling with thumbnails of each
Taina;If I understand your situation correctly: you see the phone
rendition on iPhone and tablet rendition on the Samsung -- but they look
different... I think your issue is different that DPS Admin's in this
topic. If this is the case, would you start a new forum thread for your
topic? This would help engineering. Thanks.
Some devices and OSs do some interesting pixel-doubling, and I have a
hard time articulating exactly what goes on. OTOH, looks like you have a
value for the Layout Templates system that let's you emulate what you're
seeing on the device.
Device choice should be influenced by your expected audience (or maybe
you have data on your audience.)Is an iPad audience a primary user set?
Or is it phone based?Where are most of your users based? The North
American market is different than Europe or Asia.Is your app aimed more
at on-the-go consumption (phone) or not-as-mobile (tablet)?Old device
may use old OSs, so what should you support? HTH