Your SlideShare is downloading. ×
Mtc spring 2014 best practices to develop for different android device classifications
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

Mtc spring 2014 best practices to develop for different android device classifications

223

Published on

Here you can experience the learnings, which the presenter got during development of the ImmobilienScout24 Android application. The presentation doesn't cover Design, UX or Fragments, but it gives an …

Here you can experience the learnings, which the presenter got during development of the ImmobilienScout24 Android application. The presentation doesn't cover Design, UX or Fragments, but it gives an introduction and samples of using different resources, in special layouts. These folders can be used for filtering specific configurations, referencing other resources and using layout aliases. This session aims at people with knowledge of coding for Android.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
223
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Hasan Hosgel | ImmobilienScout24 Best Practices to develop for different Android Device Classifications
  • 2. About me • +HasanHosgel @alosdev alosdev hosgel CO-Organizer Developer
  • 3. ImmobilienScout24 Germany’s largest real estate listing company. > 10 Mio. Monthly unique users > 1.5 Mio. real estates > 300 Mio. detail views > 1500 Servers ~ 7.5 Mio. App downloads > 3 Mio. Android > 50% mobile traffic
  • 4. Fragmentation
  • 5. Fragmentation > 5000 Android Devices
  • 6. Here comes the Nightmare Image source: http://www.flickr.com/photos/boogeyman13/4553188509/
  • 7. Image source: http://www.flickr.com/photos/boogeyman13/4553188509/ Here comes the Nightmare For developers
  • 8. Let’s build the fundament Image source: http://www.flickr.com/photos/hertenberger/1434191066/
  • 9. Device Classification Image source: https://play.google.com/store/devices
  • 10. Image source: https://play.google.com/store/devices http://www.htc.com
  • 11. Image source: http://www.sony.de/hub/google-tv
  • 12. Image source: https://developer.ford.com/
  • 13. Open Automotive Alliance Starting 2014 several companies plan to bring Android platform to the cars. • Audi • GM • Google • Honda • Hyundai • Nvidia http://www.openautoalliance.net/
  • 14. Wearables
  • 15. Android Wear SDK
  • 16. Google Glass
  • 17. Hard Work Ahead Image source: http://www.flickr.com/photos/16210667@N02/9172895225
  • 18. Resource Folders You can use several qualifiers in the resource folders name for serving the best matching resource.
  • 19. Qualifiers • Language (-en) • Language & Region (-en-rUS) • Smallest Width (–sw600dp) • Screensize (-small, -normal, -large) • Screen Orientation (-port, -land) • Screen Pixel Densitiy (-hdpi, -xxhdpi,…) • Platform Version (-v11, -v13)
  • 20. Best Matching Resource Wins 1. res/values/strings.xml 2. res/values-en-rUS/strings.xml 3. res/values-large/strings.xml 4. res/values-sw600dp/strings.xml
  • 21. Best Matching Resource Wins 1. res/values/strings.xml 2. res/values-en-rUS/strings.xml 3. res/values-large/strings.xml 4. res/values-sw600dp/strings.xml The order of the qualifiers in the previous slides gives the ranking, if two resources have the same matching number of qualifiers.
  • 22. Image Resources • Use the different qualifiers for the screen pixel density (mdpi, hdpi, etc.) • If you are forced to use text on images use language and region (en, es-rUS, en-rUS, etc.) • Better approach is to use 9-patch drawables, which stretches automatically depending on the content inside. • You must provide different launcher icons for Froyo, Honeycomb and above? Use the platform version. (v4, v11, v14)
  • 23. Classifications for Layouts Platform version at least v13 (Honeycomb MR2)
  • 24. Classifications for Layouts Platform version at least v13 (Honeycomb MR2) project-folder/res/ layout/
  • 25. Classifications for Layouts Platform version at least v13 (Honeycomb MR2) project-folder/res/ layout/  small phones
  • 26. Classifications for Layouts Platform version at least v13 (Honeycomb MR2) project-folder/res/ layout/  small phones layout-sw320dp/  other phones
  • 27. Classifications for Layouts Platform version at least v13 (Honeycomb MR2) project-folder/res/ layout/  small phones layout-sw320dp/  other phones layout-sw600dp/  tablets 7”
  • 28. Classifications for Layouts Platform version at least v13 (Honeycomb MR2) project-folder/res/ layout/  small phones layout-sw320dp/  other phones layout-sw600dp/  tablets 7” layout-sw720dp/  tablets 10” * You should also use the orientation qualifier
  • 29. Platform version lower v11 project-folder/res/ layout/ layout-sw320dp/  other phones layout-sw600dp/  tablets 7” layout-sw720dp/  tablets 10”
  • 30. Platform version lower v11 project-folder/res/ layout/  phones layout-sw320dp/  other phones layout-sw600dp/  tablets 7” layout-sw720dp/  tablets 10”
  • 31. Platform version lower v11 project-folder/res/ layout/  phones layout-v11/  tablets 10” layout-sw320dp/  other phones layout-sw600dp/  tablets 7” layout-sw720dp/  tablets 10”
  • 32. Platform version lower v11 project-folder/res/ layout/  phones layout-v11/  tablets 10” layout-v13/  small phones layout-sw320dp/  other phones layout-sw600dp/  tablets 7” layout-sw720dp/  tablets 10”
  • 33. Hint The smallest width qualifier gets automatically platform version ”-v13” through the packager, for avoiding problems with the number of matching qualifiers.
  • 34. How to Classify In Code • Read configuration from the device
  • 35. How to Classify In Code • Read configuration from the device • Smarter approach is to use boolean resources
  • 36. project-folder/res/values/layouts.xml <resources> </resources>
  • 37. project-folder/res/values/layouts.xml <resources> <bool > </bool> </resources>
  • 38. project-folder/res/values/layouts.xml <resources> <bool name="is_phone_small"> </bool> </resources>
  • 39. project-folder/res/values/layouts.xml <resources> <bool name="is_phone_small">true</bool> </resources>
  • 40. project-folder/res/values/layouts.xml <resources> <bool name="is_phone_small">true</bool> <bool name="is_phone_other">false</bool> <bool name="is_tablet_7">false</bool> <bool name="is_tablet_10">false</bool> </resources>
  • 41. project-folder/res/values/layouts.xml <resources> <bool name="is_phone_small">true</bool> <bool name="is_phone_other">false</bool> <bool name="is_tablet_7">false</bool> <bool name="is_tablet_10">false</bool> </resources> Usage in code: getResources().getBoolean(R.bool.is_phone_small)
  • 42. Current Layout File Structure project-folder/res/ layout/main.xml layout-v11/main.xml layout-v13/main.xml layout-sw320dp/main.xml layout-sw600dp/main.xml layout-sw720dp/main.xml
  • 43. Current Layout File Structure project-folder/res/ layout/main.xml layout-v11/main.xml layout-v13/main.xml layout-sw320dp/main.xml layout-sw600dp/main.xml layout-sw720dp/main.xml Fixing one bug in the 10“ layout has to be done in two files.
  • 44. Current Layout File Structure project-folder/res/ layout/main.xml layout-v11/main.xml layout-v13/main.xml layout-sw320dp/main.xml layout-sw600dp/main.xml layout-sw720dp/main.xml Fixing one bug in the 10“ layout has to be done in two files.  error prone
  • 45. Resource Alias Put your layout files in the default folder. project-folder/res/ layout/main_phone_small.xml layout/main_phone_other.xml layout/main_tablet_7.xml layout/main_tablet_10.xml
  • 46. Create an item with the needed classification in the previously defined values folder. project-folder/res/values-sw720dp/layouts.xml <resources> </resources>
  • 47. Create an item with the needed classification in the previously defined values folder. project-folder/res/values-sw720dp/layouts.xml <resources> <item name="main" > </item> </resources>
  • 48. Create an item with the needed classification in the previously defined values folder. project-folder/res/values-sw720dp/layouts.xml <resources> <item name="main" type="layout"> </item> </resources>
  • 49. Create an item with the needed classification in the previously defined values folder. project-folder/res/values-sw720dp/layouts.xml <resources> <item name="main" type="layout"> @layout/main_tablet_10.xml </item> </resources>
  • 50. Scenario
  • 51. Use <includes>
  • 52. Usage include <LinearLayout … > … < /> … </LinearLayout>
  • 53. Usage include <LinearLayout … > … <include /> … </LinearLayout>
  • 54. Usage include <LinearLayout … > … <include layout="@layout/footer"/> … </LinearLayout>
  • 55. Use <includes>
  • 56. Use <includes>
  • 57. Custom View public class CustomView extends LinearLayout { … public CustomView(Context context, AttributeSet attrs) { … addView(createTextView(context, "label"), lp); addView(createTextView(context, "desc"), lp); if(getResources().getBoolean(R.bool.is_phone)){ setOrientation(VERTICAL); } else { setOrientation(HORIZONTAL); } } … }
  • 58. Usage In Layout Files <LinearLayout … > … <de.alosdev.CustomView android:layout_width="wrap_content" android:layout_height="wrap_content"/> … </LinearLayout>
  • 59. Use <includes> Create custom view
  • 60. Custom XML Attribute <resources> <resources>
  • 61. Custom XML Attribute <resources> <declare-styleable > </declare-styleable> <resources>
  • 62. Custom XML Attribute <resources> <declare-styleable name=”CustomView"> </declare-styleable> <resources>
  • 63. Custom XML Attribute <resources> <declare-styleable name=”CustomView"> <attr /> </declare-styleable> <resources>
  • 64. Custom XML Attribute <resources> <declare-styleable name=”CustomView"> <attr name="label" /> </declare-styleable> <resources>
  • 65. Custom XML Attribute <resources> <declare-styleable name=”CustomView"> <attr name="label" format="reference|string"/> </declare-styleable> <resources>
  • 66. Custom XML Attribute <resources> <declare-styleable name=”CustomView"> <attr name="label" format="reference|string"/> <attr name="value" format="reference|string"/> </declare-styleable> <resources>
  • 67. Custom XML Attribute <resources> <declare-styleable name=”CustomView"> <attr name="label" format="reference|string"/> <attr name="value" format="reference|string"/> <attr name="orientation" format="enum"> <enum name="horizontal" value="0"/> <enum name="vertical" value="1"/> </attr> </declare-styleable> <resources>
  • 68. Usage In Layout Files 1. Add to root XML node xmlns:app="http://schemas.android.com/apk/res- auto"
  • 69. Usage In Layout Files 1. Add to root XML node xmlns:app="http://schemas.android.com/apk/res- auto" 2. Usage in custom view <de.alosdev.CustomView android:id="@+id/customView" android:layout_width="wrap_content" android:layout_height="wrap_content" app:label="label 1" app:orientation="vertical" app:value="value 1" />
  • 70. public class CustomView extends LinearLayout { static final int[] ORIENTATION = new int[] { HORIZONTAL, VERTICAL }; public CustomView(Context context, AttributeSet attrs) { super(context, attrs); … TypedArray a = context.obtainStyledAttributes(attrs, R.styleable.CustomView) ; try { setOrientation(ORIENTATION[ a.getInt(R.styleable.CustomView_orientation, 0)]); } finally { a.recycle(); } } … }
  • 71. If custom view has much more business logic and need lifecycles  Create a Fragment
  • 72. Code
  • 73. Best Practices You have already an application  Remove orientation fixation and suppressing of orientation change from manifest to avoid long bug analyzing. You start from the scratch  Focus on main classification for faster time to market  But create an overall concept for better modularization
  • 74. If you support both orientations, save the instance state while orientation changes for more responsiveness Especially for states, that need a long computation for creation. Make the state object Parcelable for faster write & read and also to have a smaller memory footprint
  • 75. Developer Hints • You can start an activity for result from a fragment, so the response can be handled in the fragment. • If you want to register a special service on every onCreate method of an activity give the ActivityLivecycleCallbacks a try. You can register them in the onCreate method of the application. (minSDK -v14)
  • 76. If you get a BadParcelableException with the cause ClassNotFound-Exception, the source can be a NullPointerException during the read or write of the Parcelable. Exceptions are hidden during the parcel process.
  • 77. If you want to use “match_parent” or “wrap_content” in a dimension alias, you should use “-1px” or “-2px” project-folder/res/values/dimen.xml <resources> <dimen name="my_dimen>@dimen/match_parent</dimen> <dimen name="match_parent">-1px</dimen> <dimen name="wrap_content">-2px</dimen> </resources> project-folder/res/values-sw600dp/layout.xml <resources> <dimen name="my_dimen>300dp</dimen> </resources>
  • 78. Listener Hell If you have to many listeners or you think the programming model is old school like the “goto statements”. Give message/ event/ service bus a try. For Android: • Otto from Square • EventBus from greenrobot See also: Callbacks as our Generations' Go To Statement
  • 79. Custom Theme & Style Android Ui Utils
  • 80. ActionBar Style Generator
  • 81. Holo Color Generator
  • 82. Mission Accomplished? Image source: http://www.flickr.com/photos/ianaberle/5729561934/
  • 83. Mission Accomplished Image source: http://www.flickr.com/photos/ianaberle/5729561934/
  • 84. Q & A Image source: http://www.flickr.com/photos/21496790@N06/5065834411/
  • 85. www.immobilienscout24.dewww.immobilienscout24.de Thanks for your attention! Contact: +HasanHosgel @alosdev alosdev Best Practices to develop for different Android Device Classifications https://github.com/alosdev/multidevice-nightmare-demo http://www.slideshare.net/hosgel/mtc-spring-2014-best-practices-to-develop-for-different- android-device-classifications

×