– an open community project
Upcoming SlideShare
Loading in...5

Like this? Share it with your network

Share – an open community project



This presentation is about an open community project called which aims at becoming a central imformation hub for specific fragmentation related device information.

This presentation is about an open community project called which aims at becoming a central imformation hub for specific fragmentation related device information.



Total Views
Views on SlideShare
Embed Views



20 Embeds 1,080 487 350 74 56 30 29 25 6 3 3 3 2 2 2 2 2 1 1 1 1



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.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment – an open community project Presentation Transcript

  • 1. Android Fragmentation .com The Open Android Device Knowledge Base
  • 2. What is this all about?
    • Android is a great platform. But its growing fragmentation destroys value for developers, consumers and carriers.
    • This presentation introduces a community effort that enables developers to share knowledge about device specifics and address the problems before their apps hit the market
      • Open Source project android analyzer
  • 3. Friendly Reminder
    • Fragmentation isn‘t evil, it‘s the natural result of an open market place and diverse demand.
    • No reason to get emotional about it (like many people do)!
    • No reason to blame anyone.
    • No reason to deny its existance.
  • 4. The Problem Photo by Brantano Shoe City
  • 5. The Problem Theory:
  • 6. The Problem Theory: Practice:
  • 7. The Problem
    • The Android platform is fragmented
      • Different Android OS versions
      • Different form factors
      • Different UIs (and other OEM specifics)
      • Different device categories (mobiles, tablets, cars…)
  • 8. The Problem
    • Android apps don’t run on all devices
    • Higher development cost for developers
    • Possible reach goes down
      • Less “platform value” for end consumers
      • Less revenue for developers
      • Less selling points for carriers & OEMs
    • Higher customer care expenditures
  • 9. Fragmentation Examples
    • … our developer spent ~1hr on implementing a progress animation in a home screen widget, and another ~4hrs porting it and making it consistent across Archos 5IT, Google Nexus One, HTC Hero and G1
    • Blinkendroid project: Works fine on all phones except the Motorola Milestone. Some UDP related problem.
    • DroidSpray: Problems with touch events on GL surface over camera view. Device specific re-ordering of views required …
  • 10. Fragmentation Examples
    • Android platform API increments: basic APIs like Bluetooth added continuously to the platform
    • API behavior inconsistency: bug #4961 (File.getCanonicalPath throws exception) introduced in 2.x, but the same method works in previous versions
    • Screen size and resolution: apps should provide special layouts and drawables for different sizes/resolution combinations.
  • 11. Fragmentation Examples
    • OEM specifics:
      • receiving multicast messages over WiFi is disabled in the Linux kernel for most HTC devices, but is enabled on Archos 5IT
      • Supported file types and formats: Droid can record raw .aac audio files, but most Android phones don’t support this file type, although they support the codec (based on specs)
      • Devices come with different themes, which always eat a pixel here and there
  • 12. Fragmentation Examples
    • Issue 4739: 2.0 SDK breaks older contact apps. summary: 2.0 seems to require apps to set a newly defined field when adding a contact programmatically. thus, old apps that don't set it won't work properly
    What‘s your favorite example?
  • 13. Facts and Figures
  • 14. Android OS Lifeline 2008 2009 2010 2011 October ‘08: Android OSS Project, v1.0 launch, G1 on sale February ’09: v1.1 April ‘09: v1.5 September ‘09: v1.6 October ‘09: v2.0 December ‘09: v2.0.1 January ‘10: v2.1 May ‘10: v2.2 Q4 ‘10: v3.0
  • 15. Device Launches per OEM * Source: ** Source: Total: 194 Devices (as of July)
  • 16. Device Distribution per OS Version * Source: ** Source:
  • 17. Device Distribution per Screen Size * Source: ** Source:
  • 18. Device Distribution per Resolution * Source: ** Source:
  • 19. Device Types and Markets Mobile Phone TV Internet Tablet Telematics and Navigation Set-top Box
  • 20. Highlights
    • Huge amount of devices launched: 194 models in 23 months
    • Active OS versions & APIs on the market: 6 (out of 8)
    • On average, new OS release announced every ~ 4 months
    • Over 8 screen resolutions on the market, excluding orientation and resolution families
    • At least 20 different screen sizes , that affect the DPI
    • Variety of vertical markets with own specifics
  • 21. Bottom Line
    • Will fragmentation go away? No!
    • What can we do about it? Embrace it!
    • Let’s engage as a community and create a knowledge base about this problem!
  • 22. Solution?
  • 23.
    • Free hub for fragmentation knowledge
    • Purpose: discuss, learn, compare, share
    • Contents:
      • Database with device- and firmware-specific information, APIs, hardware & software capabilities, etc. (coming soon)
      • News Feed & Forum
      • Device search and comparison (coming soon)
    • Database fed by a client app developed by the sister project Android Analyzer hosted on Google Code
  • 24. Device Capability DB Web Server Website Webservice Tools Analyzer
  • 25. Enter
  • 26. Device Capability Database Preview
  • 27. Android Analyzer App
    • Open source client-side project on Google Code:
    • Collects data and sends to the server
    • Users can extend the report with their own findings
    • Will evolve as Android OS evolves
    • Will be published on the Market
    • !!! Everyone welcome to contribute !!!
  • 28. Android Analyzer App
  • 29. Android Analyzer: Plugins
  • 30. Coming Soon
    • Roadmap:
      • Q3/2010 : Forum, device database, reports, comparison, advanced search
      • Q4/2010 : UI enhancements, web-based data edit and comments
      • Idea: Ecplise plugin for auto validation of APIs used in your project
      • Idea: Open APIs for access to device capability database
    • Android Analyzer App Roadmap:
      • Q3/2010 : analyzer core, pluggable architecture, data collection based on available Android APIs, reporting to backend, user comments
      • Q4/2010 : enhanced user interface and reporting on the device, fine-grained data edit and comments
      • Q1/2011 : advanced capability detection, auto-testing (e.g. media formats), support for OEM-specific extensions
  • 31. Your Feedback Needed!
    • PLEASE tell us what you think!
    • Send us your suggestions about how to improve the site and what services to offer!
    • Any feedback is very much appreciated!
    • Feedback can be sent through web site or to
    • email address
  • 32. [email_address] Thanks Android Stammtisch Rheinland 15.09. Köln