Google I/O 2011: Designing and Implementing Android UIs for Phones and Tablets

What people said

Recommends adamp · 2011-05 · Stack Overflow · on “Layout breaking down - how to get it even/aligned?”

You might want to pass along these links to your designers, both are talks from Google I/O on Android UI design patterns. The first is from last year, the second is from this year: [LINK] [this video]

Recommends Blundell · 2011-10 · Stack Overflow · on “Fragments on Android 1.6 with compatability package”

You should use Fragments for all your classes including those that will be run on 1.6, that will help with the re-use. This video from Google IO 2011 will explain it for you: [this video]

Recommends Ferdau · 2012-03 · Stack Overflow · on “Android coding best practices/design patterns”

You should watch (from Google IO 2011): [this video] It's not about ICS but about honeycomb but it's still very interesting... You will see that the ActionBar (there are also some libraries that make you implement the ActionBar on older versions of android) is getting more important and can be found in most google apps for android... Also the ViewPager is used alot (for swiping horizontally between different tabs/views), like in the market... To keep your project clean, you could give every activity a separate xml file, recurring elements you use should be kept in a separate xml file that you can include in every other xml file (footers, headers, separators,...) Hope this helps you along!

Recommends zapl · 2012-04 · Stack Overflow · on “Having a handset and tablet layout”

The Google I/O app [LINK] is a good example. Basically you have different layouts that contain different Fragments for different devices. Since each Fragment manages itself like an Activity you don't have to do much beyond creating layouts of fragments. There is also a nice video [this video] that explains a lot about that app.

Cites jschmier · 2011-05 · Stack Overflow · on “Carousel view in Android”

You might peruse the CarouselView [LINK] example code mentioned in the " Designing Android UIs for Phones and Tablets [this video] " session at Google I/O 2011. The example makes heavy use of the Renderscript [LINK] framework, released with Android 3.0. Variations of the CarouselView component were used in several of the applications within Honeycomb including Books and YouTube when creating 3D carousel effects.

Cites jschmier · 2011-05 · Stack Overflow · on “3D Carousel for Android?”

As I mentioned in my answer [LINK] to a similar question [LINK] , you might peruse the CarouselView [LINK] example code mentioned in the " Designing Android UIs for Phones and Tablets [this video] " session at Google I/O 2011. The example makes heavy use of the Renderscript [LINK] framework, released with Android 3.0. As such, the example code is for API levels 11 and up. Variations of the CarouselView component were used in several of the applications within Honeycomb including Books and YouTube when creating 3D carousel effects.

Cites Blundell · 2011-05 · Stack Overflow · on “Google IO Sched App - Tablet Layout & Fragments”

Am I just being dumb or what. So checking out the IO Sched source I wanted to see how they got a different layout on the tablet home activity than the phone home activity. Am I looking at the latest source version? [LINK] So here is activity_home.xml: [LINK] And it basically is just describing the action bar and the dashboard layout. However on the tablet the home activity also shows a realtime stream fragment. On the IO video he is describing these screens with fragments here: [this video] I've also checked the HomeActivity class and this doesn't seem to do it: [LINK] so I cannot see how or were the layout for the Tablet is working and where the fragments have been declared. Could someone give m

Cites android developer · 2012-05 · Stack Overflow · on “Why fragments, and when to use fragments instead of activities?”

In Android API 11+, Google has released a new class called Fragment . In the videos, Google suggests that whenever possible ( link1 [this video] , link2 [LINK] ), we should use fragments instead of activities, but they didn't explain exactly why. What's the purpose of fragments and some possible uses of them (other than some UI examples that can be easily be achieved by simple views/layouts)? My question is about fragments: What are the purposes of using a fragment? What are the advantages and disadvantages of using fragments compared to using activities/views/layouts? Bonus questions: Can you give some really interesting uses for fragments? Things that Google didn't mention in their videos? What