• Save
MOTOROLA XOOM Meet-up March 1st
Upcoming SlideShare
Loading in...5
×
 

MOTOROLA XOOM Meet-up March 1st

on

  • 3,683 views

These are slides from the MOTOROLA XOOM meet-up on March 1st in San Francisco. http://developer.motorola.com

These are slides from the MOTOROLA XOOM meet-up on March 1st in San Francisco. http://developer.motorola.com

Statistics

Views

Total Views
3,683
Views on SlideShare
3,205
Embed Views
478

Actions

Likes
5
Downloads
0
Comments
0

8 Embeds 478

http://community.developer.motorola.com 468
https://fts7.mot-tools.co.uk 2
http://mtrl.lithium.com 2
http://developer.motorola.com 2
http://feeds2.feedburner.com 1
http://fanyi.youdao.com 1
http://framework1.onsitetechnical.com 1
http://webcache.googleusercontent.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Interconnectivity is creating new social behaviors and changing the way consumers interact with and share information.
  • Motorola XOOM and Atrix the first expressions of our push into new converged product categories.
  • Succeeding in this new landscape requires applications that enable new user experiences. We want to work closely with you through MOTODEV to create and delivers new types of apps that are relevant across multiple screens, sync across device types and drive interactions between devices. That is what tonight is all about so thank you for coming and let’s get started!
  • Dual-core 1.0 GHz NVIDIA Tegra 2 with ultra-low power NVIDIA GeForce GPU Android 2.2.1 (Froyo) 4 inch qHD pentile display (540x960) “ normal” screen size, “high” screen density (hdpi) Flash Player 10.1 Record and playback 720p HD video at 30 fps (decode 1080p video)
  • SOURCE: Gartner Research Article – Title - Gartner Says Worldwide Mobile Device Sales to End Users Reached 1.6 Billion Units in 2010; Smartphone Sales Grew 72 Percent in 2010 (2/9/2011) “ In the smartphone operating system (OS) market, ''Android grew 888.8 percent in 2010 and moved to the No. 2 position.” – (pg3 of 4) From Ingrid K.
  • Possible Replacement for Slide 7 with updated figures. Need to find out what the source is for this chart. SOURCE: From Consumer Insights Report (Motorola) CRMOTO Q4'10 USA Report.ppt
  • This is a typical Android smartphone. Across the top is your status bar where your status icons appear (battery, wifi, etc). This is also where your notifications can be found. Touching the status bar opens the notification panel. Moving to the bottom of the device, is where you’ll find buttons. Prehoneycomb devices were required to have 3 buttons – menu, home, and back. There’s usually a fourth button (in this case search). So that’s a typical smartphone.
  • When you’re talking about tablets things change. On the hardware side there are only three buttons on the device – volume up, volume down, and power.
  • Moving to the home screen it’s a very different UI. From an apps perspective there are a couple things you should be aware of. For instance… You have the system bar along the bottom. The back and home button on the lower left. There is NO menu button. Menus are now all in software and only available from within an application. On the lower right is where your status bar icons now appear as well as you notification panel. From a user perspective there’s much more to it but from a developer’s standpoint, those are the things you should be aware of. They won’t necessarily impact your application but it may change the way you think about things.
  • So lets talk about the writing apps. You can’t talk about the XOOM without talking about honeycomb. One of the biggest changes for applications is in the UI. This is a list of the additions and redesigns Google made to the UI. I’ll walk you through a handful of them.
  • Select a view that you want to associate the dimmer with (I have an id assigned to my root linearLayout) and set the visibility. You can attach the call to any view (including buttons) so may want to toggle the dimmer. If you touch the system bar the icons reappear. Touching the view dims the system bar. Book reader is a good example of dimming.
  • Replaces the title bar. This is the simplest form of an action bar. The Action Bar is included by default in all activities that target Android 3.0 or greater (setting minSdk or targetSdk = 11) Basic action bar with an overflow menu. The menu in the action bar replaces the hard menu button on the front of the device. The default behavior for the application icon is to do nothing. The title can be displayed or hidden.
  • Action bars get more feature rich from there. There are many extensions you can make to the action bar including -- actionable application icon with R.id.home in onOptionsMenuSelected -- adding tabs -- creating individual actionable items with or without text and titles -- Provide a drop-down list for navigation -- Provide interactive "action views" in place of action items (such as a search box).
  • One final note on menus. To support forward compatibility a soft menu button is provided along the system bar for pre-honeycomb apps. If you open the menu you can see where and what the menu items looks like.
  • Starting with 3.0 developers can divide the Activities of their applications into subcomponents called Fragments. Fragments -- can be added, removed, replaced, and animated inside an Activity dynamically -- are modular and reusable across multiple Activities. Here we’ve got the updated version of the contacts app showing the list of contacts in a fragment on the left and the details of the selected contact in a fragment on the right.
  • Fragments can not stand on their own. They must be included in an activity. However fragments are self contained in that they have their own life cycle as well as their own UI layout. One of the most common ways to use fragments is to associate a content fragment with an item in a list. There’s a separate type of fragment, called a ListFragment, that lets you do this. The content fragment can contain anything you would normally use in an activity – images, text, ui elements, etc.
  • (Nothing changes in the AndroidManifest file) Adding a fragment to an activity requires updates to the activity’s layout file. You must add the fragment to your Activity’s layout file with a tag. In the fragment tag you declare the class name of the fragment that’s defined usually in a separate .java file. Pay attention to the root layout or container you use. In this case I used LinearLayout which, by default has a top to bottom placement. So when I first did this app my fragments did not appear side-by-side, they appeared top-to-bottom. I needed to add orientation=horizontal in order to get the side-by-side. The device’s orientation is landscape by default so if you want a portrait version of the app to be top-to-bottom you’ll need to create another layout-port file specifying orientation=portrait.
  • Follow instructions for using Data Storage to external media http://developer.android.com/guide/topics/data/data-storage.html Every Android-compatible device supports a shared storage. Shared files: Music/ - Media scanner classifies all media found here as user music. Podcasts/ - Media scanner classifies all media found here as a podcast. Ringtones/ - Media scanner classifies all media found here as a ringtone. Alarms/ - Media scanner classifies all media found here as an alarm sound. Notifications/ - Media scanner classifies all media found here as a notification sound. Pictures/ - All photos (excluding those taken with the camera). Movies/ - All movies (excluding those taken with the camcorder). Download/ - Miscellaneous downloads. Private files can be placed in /android/data/ folder.
  • Apps are always forward compatible but……
  • Apps are always forward compatible but……
  • Test Criteria: App Behavior Is all functionality accessible, performing well, and fitting well on the device screen? Are all input methods properly supported? Are all strings spelled correctly and properly translated (if multiple languages are supported)? Stability Tests Does the app handle both app and system events correctly, including any errors / failures? XOOM Specific Does the app support the Tablet UI framework and are all stacks and activity frameworks properly maintained? Does the app leverage the new Action Bar API and do all controls respond properly?
  • Android Market filters Mismatched manifest.ini settings Layout issues specific to different sized displays Missing drawable resources Improperly localized apps Forbidden or dangerous permission

MOTOROLA XOOM Meet-up March 1st MOTOROLA XOOM Meet-up March 1st Presentation Transcript

  • MOTOROLA and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC. All other trademarks are the property of their respective owners. © 2011 Motorola Mobility, Inc. All rights reserved. MOTOROLA XOOM MEET-UP March 1, 2011
  • MOTOROLA and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC. All other trademarks are the property of their respective owners. © 2011 Motorola Mobility, Inc. All rights reserved. Christy Wyatt Corporate VP – Software & Services Product Management
  • 27 Motorola Android Models 705 Launches Around the Globe Selling in 98 Countries View slide
  • Android Is #3 in the US… View slide
  • … But The Rate of Acceleration Has Overtaken Apple
  • Convergence Is Creating A More Mobile, Connected and Social Society
  • Convergence Wins MOTOROLA ATRIX ™ 4G BEST SMARTPHONE AWARD MOTOROLA XOOM ™ BEST OF SHOW AWARD BEST TABLET AWARD 2011 BEST OF CES AWARDS
  • Thriving Together in a Converged World
  • AGENDA
    • Android and Motorola Market Opportunity
    • MOTOROLA XOOM Demonstration
    • Designing Apps for the MOTOROLA XOOM
    • Panel: Development Experiences with MOTOROLA XOOM
    • Partnering with MOTODEV
    • Wrap-up and Device Giveaway
  • MOTOROLA and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC. All other trademarks are the property of their respective owners. © 2011 Motorola Mobility, Inc. All rights reserved. Lori Fraleigh Director, Developer Platforms, Tools, and Technical Services ANDROID AND THE MOTOROLA OPPORTUNITY
  • AGENDA
    • Android and Motorola Market Opportunity
    • MOTOROLA XOOM Demonstration
    • Designing Apps for the MOTOROLA XOOM
    • Panel: Development Experiences with MOTOROLA XOOM
    • Partnering with MOTODEV
    • Wrap-up and Device Giveaway
  •  
  • OUR STRATEGY
    • Only company that is “All-in” with Android
      • 1st Android Éclair device (original DROID)
      • 1st Android Honeycomb device (MOTOROLA XOOM)
      • Co-located in Silicon Valley + co-development at Google HQ
    • Investing and innovating in Android more than anyone else
      • 1st Android business device (DROID PRO)
      • Largest open source contribution to Android outside of Google
    • Commitment to full, rich web experience on mobile
      • 1 st device to preload Flash 10.1 (DROID 2)
      • HTML5 support
    • Well positioned to take advantage of convergence of media/mobile
      • Deep expertise in end-to-end video services
      • Developing next generation of converged devices (MOTOROLA ATRIX)
  • ANDROID MOMENTUM WORLDWIDE SMARTPHONE SALES BY OS 2009 Market Share 14.4% 3.9% 2010 Market Share 15.7% 22.7% Source: Gartner Research, Feb 2011
  • ANDROID TOPS IPHONE IN U.S. MOBILE WEB TRAFFIC Q4'09 Q2'10 Q4'10 0% 100% 31 17 13 21 25 21 8 5 28 34 30 13 5 8 26 Source: AdMob Mobile Metrics Report, December 2010 Windows Mobile/Phone 7 OS Symbian OS Apple iOS/iPhone OS Android/Google OS Linux OS Palm/WebOS BlackBerry OS Meego/Maemo Others
  • REVENUE POTENTIAL KEEPS CLIMBING
      • Mobile App Stores Revenue Opportunity Worldwide 2008–2013 ($B)
    Source: Gartner (December 2009) End-user spending Advertising revenue
      • 30
      • 25
      • 20
      • 15
      • 10
      • 5
      • 0
      • $35
    2008 2009 2010 2011 2012 2013
  • MOBILE IS THE INTERNET
      • 2000
      • 1600
      • 1200
      • 800
      • 400
      • 0
    Source: Morgan Stanley Research Desktop Internet Users Mobile Internet Users 2007E 2010E 2015E
      • Mobile Users > Desktop Internet Users Within 5 Years (MM)
  • HUGE MARKET SURGE PREDICTED FOR TABLETS BY 2015
      • Global Tablet Shipments Will Rise From 19.7 Million in 2010 to 242 Million in 2015
    iPad Other Media Tablets
      • 250,000
      • 200,000
      • 150,000
      • 100,000
      • 50,000
      • 0
      • $300,000
    2010 2011 2012 2013 2015 2014 PC-Type Tablets Source: HIS iSuppli Market Research, February 2011
  • MOTOROLA and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC. All other trademarks are the property of their respective owners. © 2011 Motorola Mobility, Inc. All rights reserved. Anna Schaller, Peter van der Linden Android Technology Evangelists DESIGNING APPS FOR THE MOTOROLA XOOM
  • INTRODUCING THE MOTOROLA XOOM
    • Screen : 10.1” diagonal (xlarge), WXGA (1280 x 800), 160 dpi
    • Memory : 32 GB flash storage
    • Processor : nVidia Tegra 2 dual core
    • Sensors : accelerometer, barometer, gyroscope, compass, ambient light, GPS, no proximity or vibration, 4-way rotation
    • Connectivity : 802.11 a/b/g/n, Bluetooth, HDMI
    • Camera : 2mp fixed focus front / 5mp auto focus rear
    • Media : 720p HD video recording, 1080p HD playback
    • External storage : 32 GB SD card post-launch
    • Platform : Android 3.0 (Honeycomb)
    • App Environments: Adobe AIR 2.6, Android, NDK, (Flash 10.1 coming)
    • Lots and lots of software changes……..
  • WHERE DID EVERYTHING GO? Status bar Menu Key Home Key Back Button Bonus Button (usually search) Volume Keys (up/down) Power Button
  • INTERACTING WITH THE TABLET Volume Keys (up/down) Power Button
  • INTERACTING WITH THE TABLET (CONT) System Bar Not a menu button
  • APPLICATION UI DESIGN CHANGES
    • Holographic Theme
    • System Bar Dimming
    • Action bar
    • Fragments
    • New widgets
    • Updated Notifications
    • System Clipboard
    • Drag-and-drop
  • HOLOGRAPHIC THEME
    • Inherited by all apps built against Android 3.0
      • minSdkVersion or targetSdkVersion = 11 * and * enable hardware acceleration ( android:hardwareAccelerated=“true” )
      • If SDK version <= 9 then your application uses the widget designs from Android 2.3 and does not inherit the holographic theme
    • Two versions exist
      • Default dark background with white letters @android:style/Theme.Holo
      • Inversed holographic white with dark letters @android:style/Theme.Holo.Light
  • DIMMING THE SYSTEM BAR
    • Lights out mode
      • Dims the system bar by replacing the icons with holographic “dots” (system bar is not removed)
    • View v = findViewById(R.id. view_id);
    • v.setSystemUiVisibility( View. STATUS_BAR_HIDDEN );
  • ACTION BAR - SIMPLE
    • Replaces traditional title bar at top of app
    • Application Icon with title
    • Overflow menu
      • Creating a menu has not changed
      • public boolean onCreateOptionsMenu(Menu menu) {…}
      • public boolean onOptionsItemSelected(MenuItem item) {
      • case R.id.menu_item …}
      • /res/menu/ menu_definitions.xml
  • ACTION BAR – TABBED WITH ACTION ITEMS
    • Application Icon can be made actionable
    • Tabbed interface on Action Bar
    • Individual action items rather than listed on overflow menu
      • With or without text; with or without icon
    • See android.app.actionbar
    “ Actionable” Icon Tabs Action Items
  • GOING FULL SCREEN – REMOVING THE ACTION BAR
    • You can hide the action bar *however* your application loses access to your menu
    • <activity android:theme= &quot;@android:style/Theme.NoTitleBar&quot; >
    • Another way to hide action bar is programmatically then allow user to toggle
    • A ctionBar bar = getActionBar();
    • if (bar != null) {
    • if (bar. isShowing() ) bar. hide() ;
    • else bar. show() ;
    • }
  • MENUS
    • To support forward compatibility added soft menu button along system bar
      • minSdkVersion and targetSdkVersion < 11
  • FRAGMENTS
    • Allows an application to be divided into subcomponents that can be individually managed and combined in various ways, such as creating a multi-pane UI.
  • FRAGMENTS (CONT)
    • A fragment must always be embedded in an Activity
    List Fragment Fragment Activity
  • FRAGMENTS (BASE FRAGMENT)
    • Create class that extends Fragment
    • Displays content similar to an Activity (images, text, application widgets)
    • Can be attached to another fragment or tab
    • Can add items to the Activity’s overflow menu (action bar)
    • Does not have to be visible (can operate behind the scenes)
    • If it is visible will require it’s own layout file
    (Base) Fragment
  • FRAGMENTS (ADDING TO ACTIVITY) XOOM_hc_app /res/layout/main.xml (List) Fragment Activity layout (Content) Fragment with embedded image PictureList.java ContentFragment.java
  • FRAGMENTS (CONT)
    • How-to information in 3.0 Developer Guide on Fragments
    • See 3.0 Reference for APIs
      • android.app.Fragment
      • android.app.ListFragment
        • Displays a list similar to ListActivity
      • android.app.DialogFragment
        • Displays a floating dialog
      • android.app.FragmentManager
        • Interface for interacting with the fragment ( findFragmentById )
      • android.app.FragmentTransaction
        • APIs for fragment operations (add, remove, replace, hide, show)
    • The Android 3.0 Fragments API blog post with more detail on what’s coming
  • NEW VIEWS
    • Application Widgets
      • PopupMenu ( android.widget.PopupMenu )
        • Menu is attached to a view (button for instance)
    • Home Screen Widgets
      • StackView ( android.widget.StackView )
        • A view that displays its children in a 3D stack and allows users to discretely swipe through the children.
    • Rich Notifications ( android.app.Notification.Builder )
      • build notification layouts
  • WORKING EXAMPLE
    • Honeycomb Gallery in SDK samples showcases…..
      • Action Bar with tabbed interface, action item menu, and overflow menu
      • FragmentList and fragment in portrait and landscape
      • New theme
      • Drag and drop
      • Animation
      • Hide/Show
      • Action Bar
      • Lights Out
      • Mode
  • GRAPHICS
      • Hardware acceleration for 2D Graphics
      • New animation framework
      • nVidia compression
      • Renderscript
  • HARDWARE ACCELERATION FOR 2D GRAPHICS Page Version 1.0
      • a new hardware-accelerated OpenGL renderer
      • performance boost to many common graphics operations
      • most operations in Canvas, Paint, Xfermode, ColorFilter, Shader, and
      • you control how hardware-acceleration is applied, at every level,
      • enable it globally in an application,
      • or enable it only for specific Activities or Views
  • HARDWARE ACCELERATION FOR 2D GRAPHICS
      • Apply for entire application or individual activity by setting appropriate node in manifest
        • android:hardwareAccelerated=“true”
      • Apply in code on an activity and/or window through WindowManager.LayoutParams
    • Window win = getWindow();
    • win.setFlags
    • (WindowManager.LayoutParams. FLAG_HARDWARE_ACCELERATED, mask );
      • Test to see if canvas is hw-accelerated with isHardwareAcclerated()
  • ANIMATION FRAMEWORKS
    • Now, two animation frameworks you can choose from:
      • View animations (older android.view.animation )
        • Tween animations
          • Performs a series of simple transformations on the contents of a View object.
          • Basic transitions include rotating, fading, moving, and stretching a graphic.
        • Frame animations
          • Frame-by-frame animation lets you load a series of Drawable resources, one after another to create an animation.
      • Property animations ( android.animation // new in honeycomb)
        • Can animate almost anything (not just drawable objects!)
        • Can change any object property over time
        • View animations are simpler & quicker, property animations do more
        • http://developer.android.com/guide/topics/graphics/animation.html
  • OPEN GL ES TEXTURE COMPRESSION FORMATS
      • new <support-gl-texture> tag for Android manifest
      • <supports-gl-texture android:name=&quot;string&quot; />
      • declares one GL texture compression format that is supported by the application
      • supported == “app provides texture images in that format” (could be from apk file; could be downloaded from server
      • Different hw supports different texture compression, enabling developers to target specific GPUs.
      • The Android market filters on this. The tag is now active for all Android API levels, not just Honeycomb! So update your apps, if you don’t support all formats
  • OPEN GL TEXTURE COMPRESSION FORMATS
      • MOTODEV Tech library has great article:
      • http:// developer.motorola.com/docstools/library/understanding-texture-compression/
      • Names at developer.android.com/guide/topics/manifest/supports-gl-texture-element.html E.g.
      • GL_EXT_texture_compression_s3tc = S3 compression, used on Tegra 2
      • … about 8 values in all
  • RENDERSCRIPT Page Version 1.0 © 2010 Motorola Mobility, Inc.
      • New, high performance 3D graphics API
      • Was used in Froyo for Live Wallpaper
      • Is used in Honeycomb for Books and YouTube app
      • Honeycomb introduces Renderscript as a public API
      • For performance critical code where the traditional Open GL ES framework APIs are not fast enough!
  • YOUTUBE AND RENDERSCRIPT Version 1.0 © 2010 Motorola Mobility, Inc.
  • GOOGLE BOOKS AND RENDERSCRIPT
  • RENDERSCRIPT API
      • A “computing” API for locating moving points in 3D
      • A “rendering” API for drawing textures over the points
      • A C-based scripting language to access this API
      • Only goal: squeeze last ounce of graphics performance!
      • Approach: API is a thin layer over features that are hardware-supported
      • http://community.developer.motorola.com/t5/MOTODEV-Blog/Introduction-to-Renderscript/ba-p/12136
  • RENDERSCRIPT API
      • Android build tools compile your Renderscript .rs file to intermediate bytecode
      • and package it inside your application's .apk file
      • On the device, the bytecode is compiled (just-in-time) to machine code that is optimized for the exact device that it is running on
      • Machine code is cached for future use
      • This eliminates the need to target a specific architecture during the development process. Excellent!
  • EXAMPLE .RS FILE (FROM ANDROID 3.0 SAMPLES)
      • #pragma rs java_package_name(com.android.rs.helloworld)
      • #include &quot;rs_graphics.rsh” // header with graphics API’s
      • // gTouchX and gTouchY are variables that will be reflected for use
      • // by the java API. We can use them to notify the script of touch events.
      • int gTouchX;
      • int gTouchY;
      • // This is invoked automatically when the script is created
      • void init() {
      • gTouchX = 50.0f;
      • gTouchY = 50.0f;
      • }
      • int root(int launchID) {
      • // Clear the background color
      • rsgClearColor(0.0f, 0.0f, 0.0f, 0.0f);
      • // Tell the runtime what the font color should be
      • rsgFontColor(1.0f, 1.0f, 1.0f, 1.0f);
      • // Introduce ourselves to the world by drawing a greeting
      • // at the position user touched on the screen
      • rsgDrawText(&quot;Hello World!&quot;, gTouchX, gTouchY);
      • // Return value tells RS roughly how often to redraw
      • // in this case 20 ms
      • return 20;
      • }
  • SENSORS Version 1.0 © 2010 Motorola Mobility, Inc.
      • Accelerometer, Gyroscope, Magnetometer, Barometer, Compass, Ambient Light, GPS, no proximity sensor
      • Device Orientation
        • Natural orientation is landscape with 4-way rotation
    -y e +y es +x -x +z +y e +y e -x +x -y e -y e +x -x Rotation 0 Rotation 0 Rotation 90
  • SENSORS
      • These came in Gingerbread, but Honeycomb has the first hardware
      • Gyroscope
      • measures rotation in 3 axes
      • unit is radians/sec
      • http://developer.android.com/reference/android/hardware/SensorEvent.html
      • Barometer
      • measures ambient air pressure
      • unit is millibars - equivalent to 1 hPa (hectopascal)
  • GYROSCOPE SENSOR android.hardware.SensorManager sm = (SensorManager) getSystemService(Context.SENSOR_SERVICE); Sensor gyro = sm. getDefaultSensor (Sensor.TYPE_GYROSCOPE); if (gyro != null) { // have got the gyroscope boolean active = sm.registerListener( this, gyro, sm.SENSOR_DELAY_NORMAL);
  • GYROSCOPE SENSOR READING public class main extends Activity implements SensorEventListener { public void onAccuracyChanged(Sensor s, int i) { } private float x,y,z; public void onSensorChanged(SensorEvent event) { switch (event.sensor.getType()) { case Sensor.TYPE_GYROSCOPE: x = event.values[0]; y = event.values[1]; z = event.values[2]; break; Minor “gotcha” – you don’t own the event, and can’t hold onto it.
  • BAROMETER SENSOR SensorManager sm = (SensorManager) getSystemService(Context.SENSOR_SERVICE); Sensor bar = sm. getDefaultSensor (Sensor.TYPE_PRESSURE); if (bar != null) { // have got the barometer boolean active = sm.registerListener( this, bar, sm.SENSOR_DELAY_NORMAL);
  • BAROMETER SENSOR READING public void onSensorChanged(SensorEvent event) { switch (event.sensor.getType()) { case Sensor.TYPE_PRESSURE: java.text.DecimalFormat df = new java.text.DecimalFormat(&quot;#.#&quot;); String reading = &quot;PRESSURE: &quot; + df.format( event.values[0] ) + &quot; millibars&quot;;  break;
  • BAROMETER SENSOR READING © 2010 Motorola Mobility, Inc. // www.engineeringtoolbox.com/air-altitude-pressure-d_462.html // lower by ~ 1.2 gm /cm2 for each 10 meter gain in elevation
  • MEDIA SUPPORT – GETTING CONTENT ON THE DEVICE
    • Digital media file transfer
      • Built in support for Media/Picture Transport Protocol (MTP/PTP).
      • User plugs USB cable in and the Android File Transfer application launches.
      • Users can copy pictures, movies, videos, ringtones, podcasts, and more to predefined folders, or create new folders for other content.
  • TEN THINGS YOU CAN DO RIGHT NOW
    • Download the Honeycomb SDK (and updated tools) and test drive your app on the emulator.
      • Note if you have the preview SDK replace it with the updated public SDK.
    • Change the targetSdkVersion to “ 11 ” and see what changes.
    • Add /res/layout-xlarge and /res/layout-xlarge-port folders to your project with layouts optimized for the larger screen.
    • Update error handling to exit gracefully rather than defaulting to ANRs or letting the user hang.
  • TEN THINGS YOU CAN DO RIGHT NOW
    • Revisit your graphics in /res/drawable-< density > .
      • Put background into ImageView and set scaleType=centerCrop
      • Patterned images can be tiled
      • Read into createScaledBitmap() using the dimensions from DisplayMetrics
  • TEN THINGS YOU CAN DO RIGHT NOW
    • Determine if you are going with one code base or two.
    • Build your app against Android 3.0 and install on the emulator.
    • Begin testing the features of the Action Bar.
    • Add a fragment to your activity.
    • Download the Honeycomb SDK (and updated tools) and test drive your app on the emulator.
  • MOTOROLA and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC. All other trademarks are the property of their respective owners. © 2011 Motorola Mobility, Inc. All rights reserved. Lori Fraleigh PARTNERING WITH MOTODEV
  •  
  • MOTOROLA MOBILITY DEVELOPER NETWORK
    • Detailed product specs
    • Practical advice, technical articles, and documentation
    • Expert support via forums
    • Community interaction via blogs, podcasts, and social media
    • Global news, events, and training
    • Web: developer.motorola.com
    • Twitter: @motodev
  • INTRODUCING TWO NEW OPTIMIZATION PROGRAMS
  • MOTODEV APPLICATION TESTING PROGRAM
    • Identifies applications which are compatible with and optimized for Motorola devices with an initial focus on tablet applications
    • Developers whose applications are deemed to be “Ready for MOTOROLA XOOM” can participate in a growing set of global application discovery and delivery channels.
  • MOTODEV APP VALIDATOR Drag. Drop. Get Results.
  • GET STARTED NOW!
    • Download MOTODEV Studio and the Android 3.0 SDK
    • Test your app with the MOTODEV App Validator
    • Upload your apps to Android Market
    • Submit your app to the MOTODEV Application Testing Program
    • Join our NEW online office hours
      • MOTOROLA XOOM office hours 3/16 at 2pm PST
    • Leverage other MOTODEV resources
      • Ask questions in our discussion boards
      • Sign-up for the MOTOROLA ATRIX webinar with AT&T on 3/29
  • LIFE. POWERED.
  • LEGAL
    • LICENSE NOTICES
    • Except where noted, sample source code written by Motorola Mobility Inc. and provided to you is licensed as described below.
    • Copyright © 2010-2011, Motorola, Inc. All rights reserved except as otherwise explicitly indicated.
    • Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
    • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
    • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
    • Neither the name of the Motorola, Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
    • THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS &quot;AS IS&quot; AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    • Other source code displayed in this presentation may be offered under other licenses. 

    • Apache 2.0
    • Copyright © 2010, Android Open Source Project. All rights reserved unless otherwise explicitly indicated.
    • Licensed under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 .
    • Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an &quot;AS IS&quot; BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
    • Creative Commons 3.0 Attribution License
    • Portions of this presentation are reproduced from work created and shared by Google (http://code.google.com/policies.html) and used according to terms described in the Creative Commons 3.0 Attribution License (http://creativecommons.org/licenses/by/3.0/).