Your SlideShare is downloading. ×
Android 3.1 - Portland Code Camp 2011
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Android 3.1 - Portland Code Camp 2011


Published on

Android 3.1 …

Android 3.1
Portland Code Camp
June 4, 2011
Portland, Oregon

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Android 3.1 Portland Code Camp Sean Sullivan June 4, 2011
  • 2. • Introduction• Android devices• Android 3.x• App development
  • 3. iPhone Android
  • 4. Mobile World Congress February 2011
  • 5. source: comScore
  • 6. Android phones
  • 7. 2008
  • 8. 2009
  • 9. 2010
  • 10. 2011
  • 11. Android tablets
  • 12. XOOM tech specs • Android 3.1 • 10.1 inch touchscreen display • 1280 x 800 • 160 dpi
  • 13. XOOM tech specs • NVIDIA Tegra 2 dual-core chipset • HDMI connector • two cameras • no physical keyboard
  • 14. What’s new in Android 3.x?
  • 15. • ‘holographic’ UI theme• Action Bar• Fragments• Drag and Drop• Digital Rights Management• and more...
  • 16. ‘holographic’ UI
  • 17. Action Bar
  • 18. “The Action Bar is a widget for activities thatreplaces the traditional title bar at the top ofthe screen.By default, the Action Bar includes theapplication logo on the left side, followed bythe activity title, and any available itemsfrom the Options Menu on the right side.”
  • 19. Action Bar
  • 20. Fragments
  • 21. “A Fragment represents a behavior or a portion of userinterface in an Activity. You can combine multiple fragmentsin a single activity to build a multi-pane UI and reuse afragment in multiple activities.You can think of a fragmentas a modular section of an activity, which has its ownlifecycle, receives its own input events, and which you canadd or remove while the activity is running.”
  • 22. • Fragments decompose application functionality and UI into reusable modules• Add multiple fragments to a screen to avoid switching activities• Fragments have their own lifecycle, state, and back stack• Fragments require API Level "Honeycomb" or greater
  • 23. <LinearLayout xmlns:android=""        android:orientation="horizontal"        android:layout_width="match_parent"        android:layout_height="match_parent">    <fragment class=""            android:id="@+id/titles" android:layout_weight="1"            android:layout_width="0px"            android:layout_height="match_parent" />    <FrameLayout android:id="@+id/details" android:layout_weight="1"            android:layout_width="0px"            android:layout_height="match_parent" />   </LinearLayout>
  • 24. public static class TitlesFragment extends ListFragment {    private boolean mDualPane;    private int mCurCheckPosition = 0;    @Override    public void onActivityCreated(Bundle savedState) {        super.onActivityCreated(savedState); // do something here    }    @Override    public void onSaveInstanceState(Bundle outState) {        super.onSaveInstanceState(outState);        outState.putInt("curChoice", mCurCheckPosition);    }    @Override    public void onListItemClick(ListView l, View v, int pos, long id) {        // do something here    }}
  • 25. Drag and drop
  • 26. Renderscript
  • 27. “The Renderscript rendering and computational APIsoffer a low-level, high performance means of carrying outmathematical calculations and 3D graphics rendering.”
  • 28. New animation API
  • 29. Digital Rights Management API
  • 30. The same security issues that have led to piracyconcerns on the Android platform have made itdifficult for us to secure a common Digital RightsManagement (DRM) system on these devices. [...]Although we don’t have a common platformsecurity mechanism and DRM, we are able to workwith individual handset manufacturers to addcontent protection to their devices. November 2010
  • 31. Unfortunately, this is a much slower approach and leads to a fragmented experience on Android, in which some handsets will have access to Netflix and others won’t.We will also continue to work with the Androidcommunity, handset manufacturers, carriers, andother service providers to develop a standard,platform-wide solution that allows content providersto deliver their services to all Android-based devices November 2010
  • 32. New in Android 3.1• Open Accessory API• USB Host API• Input from mice, joysticks, gamepads• Resizable home screen widgets• Media Transfer Protocol (MTP)• Real-time Transport Protocol (RTP)
  • 33. Application development
  • 34. Android emulator
  • 35. Emulator performance
  • 36. Because the Android emulator must simulate the ARM instruction seton your computer and the WXGA screen is significantly larger than atypical virtual device, emulator performance is much slower than a realdevice. source:
  • 37. In particular, initializing the emulator can be slow and can take severalminutes, depending on your hardware. When the emulator is booting,there is limited user feedback, so please be patient and wait until yousee the home screen (or lock screen) appear. source:
  • 38. However, you dont need to boot the emulator each time you rebuildyour application—typically you only need to boot at the start of asession and keep it running. Also see the tip below for informationabout using a snapshot to drastically reduce startup time after the firstinitialization.Were working hard to resolve the performance issues and it willimprove in future tools releases. source:
  • 39. Sample code
  • 40. API differences
  • 41.
  • 42. Best practices
  • 43.
  • 44. What’s next?
  • 45. Final thoughts• Android 3.1 is for tablets, not phones• XOOM and G-Slate are available now• More tablets coming to market• Learn the Fragments API
  • 46. Thank you