On 13-08-09 8:48 AM, Richard Newman wrote:
A few additions to this. Apologies in advance for this sounding negative, but I
wanted to dump some of the non-obvious costs on the page.
I'll probably respond to your email in pieces.
But with FHR we ended up shuffling problems around. For example, building
mobile-friendly FHR jelly took about as long as building desktop-friendly FHR
jelly. There are UI issues -- we've had problems with font sizing, reflow and
zoom, event handling, AZPC scrolling inconsistencies, and misleading back
button handling on Android -- but my assertion is that these can be
satisfactorily addressed.
Part of this is that it's hard enough to get a good user experience across the
range of devices with a native Android UI, let alone from web content: four DPI
levels; a range of screen sizes; tablet, phone, phablet; different themes for
different combinations of device and OS (should your buttons be grey or white?).
I argue that web developers are better at getting a good user experience
across devices than Android developers are. If it's web content (shown
with an about:sync frame, at least temporarily), there's less
expectation to look like "native Android UI". (I leave the jokes about
bottom bars and vertical centering to the cognoscenti.) The web is the
platform!
Nick
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
