Android Overview for Panasonic
Total Page:16
File Type:pdf, Size:1020Kb
Android Overview for Panasonic Marko Gargenta marakana.com © 2011 About Marko Gargenta Founder, Marakana.com. Developer first Android Bootcamp. Instructor for 1,000s of developers on Android at Cisco, Qualcomm, Intel, DoD, etc. Author of Learning Android published by O’Reilly. Now in Chinese and German as well. Speaker at OSCON (3x), ACM, IEEE, SprintDevCon, AnDevCon. Co-Founder of SFAndroid.org Co-Chair of Android Open conference: AndroidOpen.com © 2011 Agenda • Android Then & Now • The Stack • Android at Work • Android Security • Operang System Features • Enterprise Soluons • Case Studies • Dangers, OpportuniBes, Strengths • Plaorm Comparisons This is your class! © 2011 ANDROID THEN & NOW © 2011 Vision for Android Our goal is not just a single device. Our vision is a mobile platform that runs on many many different devices. – Eric Schmidt © 2011 History 2005 Google buys Android, Inc. Work on Dalvik starts 2007 Open Handset Alliance announced Early SoQware Development Kit 2008 HTC G1 Announced SDK 1.0 Released 2009 G2 + 20 other phones released Cupcake, Donut, Éclair 2010 Zillion devices FroYo, Gingerbread, JIT 2011 Games, Tablets, TVs Future? Beyond phones © 2011 Today 45% 40% 35% 30% Android 25% Blackberry Apple iOS 20% Windows Palm 15% Symbian 10% 5% 0% Qtr2 2009 Qtr3 2009 Qtr4 2009 Qtr1 2010 Qtr2 2010 Android grows to 36% of US (Big 4) Smartphone Share, surpassing RIM – and growth will continue to accelerate over time © 2011 Android @Workplace © 2011 Plaorm Versions Version API Level Nickname Android 1.0 1 Android Android 1.1 2 Android Android 1.5 3 Cupcake Android 1.6 4 Donut Android 2.0 5 Éclair Android 2.01 6 Éclair Android 2.1 7 Éclair Android 2.2 8 FroYo Android 2.3 9 Gingerbread Android 2.3.3 10 Gingerbread Android 3.x 11, 12, 13 Honeycomb Android 4.0 14 Ice cream © 2011 Version DistribuBon Source: Android.com © 2011 Historical DistribuBon Source: Android.com © 2011 Add-Ons SenseUI TouchWiz MotoBlur © 2011 HTC Sense Much improved UI. Completely new apps and widgets. Overall different feel: Tasks before Apps. A smart way of innovating on top of Android Open Source project. © 2011 Motorola Motoblur New skin, new apps new widgets. All backed with an online service. Very social-centric. © 2011 Samsung TouchWiz More intuitive home screen, but real crown jewel is Swype. © 2011 “With Google” Devices that have “with Google” add-on feature a set of Google’s proprietary applications, such as Maps, Gmail, Gtalk, and many others. OEMs and carriers typically enter into a licensing agreement with Google in order to distribute Google version of Android. © 2011 Android Fragmentaon? Android Compatibility Test Suite: Defines “Android Compatible” Prevents incompatible releases Provides self testing Fragmentations lines include: - Versions of Android - Add-ons by OEMs/Carriers - Device capabilities Best practices in app development eliminate these issues. CTS ensures compliance. © 2011 Hardware Requirements • Must have a screen of any size. • Must have a soQ keyboard. Hardware keyword is opBonal. • Must support touch screen input • Should have the following sensors: Accelerometer, Magnetometer, GPS, Gyroscope. • Should include WiFi, Bluetooth. Telephony opBonal. © 2011 Hardware Requirements (cont’d) • Should include Near Field Communicaon. • Must have some network capability. • Should have rear-facing camera. Front camera is opBonal. • Memory must be: 125MB+ (system), 150MB+ (user data), 1GB+ (storage) • Must implement USB port. © 2011 FroYo: Speed with JIT • New User Features – Updated Home, Camera, Gallery, Portable hotspot – Support for Exchange (security, remote wipe, calendars, auto-discovery, global addresses) • New Plaorm Technologies – Media (hop/progressive streaming) and Bluetooth • New Developer Services and APIs – Cloud to Device Messaging – Apps on SDCard, media framework, graphics, backup, device manager, UI frameworks © 2011 Gingerbread: Gaming New User Features • Updated user interface • Power management, app control • Download manager for long downloads • Storage manager for private content on sdcard • Improved power management and app control • MulBple camera support • Copy-paste features • Redesigned keyboard © 2011 Gingerbread: Gaming New Developer Features • Performance improvements for gaming • Improved sensor support • Nave acBvity support • Near-Field Communicaon (NFC) • WebM/VP8 playback and AAC encoding • SIP VoIP support • Support for extra-large screen (WXGA++) • Ext4 instead of yaffs file system © 2011 HONEYCOMB © 2011 Honeycomb: Tablets • Honeycomb is Tablet-opBmized Android • As-is will not be supported on mobile phones • Currently two separate paths for Android • Source code likely won’t be available • Will merge in ice cream © 2011 ANDROID @WORK – A GOOGLE PERSPECTIVE © 2011 Security • Protect against loss or theQ • Protect against intercepBon • Employees are the weak link • Enforcement & crypto are key © 2011 Device Management • Onboard the users • Set up security and usage policies • Supporng users • Keep tabs on deployed devices © 2011 App Deployment & Management • Determine key mobile apps • Buy or Build • Distribute apps to devices • Manage updates • Set app usage policies © 2011 More Enterprise Support © 2011 THE MEANING OF OPEN © 2011 Open Source IniBave • Free redistribuBon • Source code • Derived works • Integrity of author’s source code • No discriminaon against person or groups • No discriminaon against field of endeavor • DistribuBon of license • License not specific to product • License must not restrict other soQware • License must be technology neutral © 2011 Andy Rubin: DefiniBon of Open © 2011 Meaning of Open, Jonathan Rosenberg • Open Technology – Open standards – Open source • Open Informaon – Valuable to users – Transparent about informaon – Control: user is in control • Open systems win http://googleblog.blogspot.com/2009/12/meaning-of-open.html © 2011 Open Android, according to Marko Open means:! ⸰ Open Source! ⸰ Open Standards! ⸰ Community Leadership! © 2011 OPEN SOURCE © 2011 Open Source Licenses http://opensource.org/licenses/ © 2011 Openness of The Stack Open, Apache 2 Open, Apache 2 Open, various licenses Dalvik is open, Apache 2 Mostly proprietary or (L)GPL © 2011 What about Honeycomb? No source for Honeycomb. But this seems to be an exception. “Our approach remains unchanged: there are no lock-downs or restrictions against customizing UIs. There are not, and never have been, any efforts to standardize the platform on any single chipset architecture. … As soon as this work is completed, we’ll publish the code. This temporary delay does not represent a change in strategy. We remain firmly committed to providing Android as an open source platform across many device types.” - Andy Rubin © 2011 Android and Linux Android's kernel is separate fork of Linux Linux community rejected Google's changes Linux changes still point of contention © 2011 OPEN STANDARDS © 2011 Android and Open Standards • Use open standards where possible • Leave slots where proprietary is beoer • Create new standards where needed © 2011 Example: Media Support Audio AAC LC/LTP, HE-AACv1 (AAC+), HE- AACv2, AMR-NB, AMR-WB, MP3, MIDI, RTTTL/RTX, Ogg, PCM/WAVE Video H.263, H.264, MPEG-4, VP8 Image JPEG, GIF, PNG, BMP Missing many codecs and native support. Expansion available via Khronos OpenMax IL © 2011 Example: VPN Support Support for VPN built-in: PPTP, L2TP, L2TP/IPSec PSK VPN, L2TP/IPsec CRT VPN But missing key enterprise VPNs, such as Cisco and Juniper. Solution via Raccoon “expansion slot”. © 2011 COMMUNITY LEADERSHIP © 2011 Open Handset Alliance From 34 to 80+ members Includes OEMs, chip vendors, operators, software companies. Still learning to work together. © 2011 Private Roadmap Not a public roadmap. Community input is observed, but no promises are made. This represents a problem for OEMs planning future device releases. © 2011 Bear Hugging Favorite OEM for each release. For G1/Dev1, Nexus One: HTC For Nexus S: Samsung For Xoom: Motorola Different terms for different OEMs? “We’re more like Apple than Microsoft” – Andy Rubin © 2011 Compability Test Suite Android Compatibility Test Suite: Defines “Android Compatible” Prevents incompatible releases Provides self testing Good for users. Good for developers. For Google, a leverage over OEMs. But also a crystal ball into Android’s roadmap. © 2011 WHAT DOES THIS MEAN TO YOU? © 2011 As User I can extensively customize the device.! I can make it “all about me”.! I can even change the flavor of Android.! © 2011 As Developer My app will run on any Android device, regardless of manufacturer.! I can see ins and outs of the platform source code and learn from studying the default apps.! My market is huge.! © 2011 As Manufacturer I may not get the latest code. I get a fully featured OS Nor know what’s coming out for free and can innovate at next. I may be months a higher level. behind competitors. Ugh! © 2011 As Carrier Users love Android!! Who exactly is to support it?! It’s an alternative to iPhone.! Can’t lock down the device – Got many OEMs and and my enterprise customers devices to choose from. what that! © 2011 As Enterprise Many productivity apps.! How do we lock it down?! Users have their own phones How do I create custom ROM?! already. Personals phones inside the company?? © 2011 Overall • Open Source: ★★★ • Most of code is open sourced, but not all • OEMs sBll keep drivers and extensions private • Open Standards: ★★★★ • Whenever license permits, open standards are used • Community Leadership: ★★ • Lack of public roadmap • No early access to code for all