3 ms·
This pattern comes from the official Android Design recommendations for Android 4.0: http://developer.android.com/design/patterns/multi-pane-layouts.html http:/
by talklittle 14y ago
This pattern comes from the official Android Design recommendations for Android 4.0: http://developer.android.com/design/patterns/multi-pane-layouts.html http://developer.android.com/design/patterns/multi-pane-layo...
It's clearly a way to adapt the tablet multi-pane paradigm to fit on small screens. Based on my Android experience, this unified approach requires a lot less work than maintaining completely separate layouts (and Activity design) for tablet and phone.
- Zigurd 14y agoThe death of the dreaded dashboard is very welcome, but "side navigation" is nothing but a half-baked transformation of the same idea into a pseudo-fragment implementation. Google+ is a particularly bad example how to do this. The Google+ layout is much better than it used to be, but it needs a real two-fragment layout on large screens, which it still does not have. Why have a layout that is half-hidden on the right, especially on large screens when two fragments could easily be placed side by side? Is is possible, even easy, to do a single code-base that "auto-magically" adapts to one Fragment object visible, or two, depending on the platform's choice of layout.
- uwemaurer 14y agoLets hope there will be a good implementation which handles tablets and phone. According to the Android library stats this pattern is not widely used yet, or devs do their own implementation: http://www.appbrain.com/stats/libraries/dev http://www.appbrain.com/stats/libraries/dev