This is my presentation file on Droidcon Paris 2013.

1. Multi-Versioning Android Apps
Droidcon Paris 2013
Kenichi Kambara (@korodroid)
June 18, 2013

2. l Kenichi Kambara (Twitter @korodroid)
l iplatform.org（http://www.iplatform.org/） (Personal)
l NTT Software Corporation (Official)
2
l Activity（iplatform.org as Personal）
9 10
Who am I?
- My Android Apps on Google Play （20+ Apps)
l Activity（NTT Software as Official）
- Technical Support for Developing

3. 3
l Kenichi Kambara (Twitter @korodroid)
l iplatform.org（http://www.iplatform.org/） (Personal)
l NTT Software Corporation (Official)
Who am I?
l Activity（iplatform.org as Personal）
9 10
“Sekai Phone”
lGoogle Developer Day 2011 Tokyo Keynote Demo
lMulti Screen UX Competition 2013 Excellence Awards
lMobile World Congress 2013 Exhibition

4. 4
l Kenichi Kambara (Twitter @korodroid)
l iplatform.org（http://www.iplatform.org/） (Personal)
l NTT Software Corporation (Official)
Who am I?
l Activity（iplatform.org as Personal）
New Sekai Phone
Available Today!!!
*Special Thanks: Kenichi Takahashi
lImproved UI / UX
lImproved Usability
lMultiVersions & Devices

5. 5
Agenda
•Introduction (+ Sekai Phone)
•Background
•Application Development Tips
Q. How to support Multiple Screens?
Q. How to support Multiple Versions?

6. 6
2.x 3.x 4.x
My session topics
Some tips on developing Apps
for multi versions and multi devices.
Handsets Tablets

7. 7
Introduction
(Sekai Phone)

8. 8
What is “Sekai Phone”?
Chinese
Japanese
French
Italian
○
English German
○ ○
○
○
Real time translation phone services
(Supports Android 2.x/3.x/4.x & multi devices)
Publish Date: Jan, 2010, over 20+ ver.up

9. 9
Use Case (1)
Phone mode
(Auto translating to receiver’s native language)
French Japanese

10. 9
Use Case (1)
Phone mode
(Auto translating to receiver’s native language)
Bonjour!
French Japanese

11. 9
Use Case (1)
Phone mode
(Auto translating to receiver’s native language)
Konnichiwa!Bonjour!
French Japanese

12. 9
Use Case (1)
Phone mode
(Auto translating to receiver’s native language)
Konnichiwa!
Arigatou!
Bonjour!
French Japanese

13. 9
Use Case (1)
Phone mode
(Auto translating to receiver’s native language)
Konnichiwa!
Merci! Arigatou!
Bonjour!
French Japanese

14. 10
App Demos (1.Phone mode)
N/A

15. 11
FrenchEnglish
Use Case (2)
Talk mode
(Auto translating on the spot)

16. 12
App Demos (2.Talk mode)

17. 13
App Screenshots on Android 2.x/3.x/4.x
2.x
3.x
4.x
Handsets Tablets

18. 14
Background

19. 15
Current Android Devices
2.x
3.x
4.x
Handsets
(Almost all)
Tablets
(All)
Handsets
& Tablets

20. 16
PlatformVersions?
This data by Google on Feb 1, 2013

21. 17
PlatformVersions?
In my App:
Main Target: Android 2.2+ (2.2,2.3,3.x,4.x)
This data by Google on June 3, 2013
ICS
JB
Eclair
Froyo
Gingerbread
Honeycomb

22. 18
Screen Sizes & Densities?
This data by Google on June 3, 2013
Normal
Small
Xlarge
Large
hdpi
xhdpi
ldpi
mdpi
xxhdpi
tvdpi

23. 19
Screen Sizes & Densities?
In my App:
My Target: (normal,large,xlarge)x(mdpi,hdpi,xhdpi,xxhdpi)
This data by Google on June 3, 2013

24. 20
Application Development Tips

25. 21
l How to support Multiple Screens
Support multi versions and multi devices?
1.Designing User Interface
2.Using APIs
l How to support Multiple Versions

26. 22
1. Designing User Interface
[Some Approaches]
Handsets Tablet (‘’7) Tablet (‘’10)

27. 23
[UI]1st Approach
Using layout-small/normal/large/xlarge
l Supports Android 1.6+
l Some Problem
Screen Size
Classification

28. 24
[UI]Introduction of 2nd Approach
Remarking “dp(Density-Independent pixel)”
Handsets
Typically, Width & Height ≥ 600dp
Tablet (‘’7)

29. 25
[UI]Introduction of 2nd Approach
Using “dp(Density-Independent pixel)”
Handsets Tablet (‘’7)
Typically, Width & Height ≥ 600dp
layout/
main.xml
layout-sw600dp/
main.xml

30. 26
[UI]2nd Approach
Using sw<N>dp,w<N>dp,h<N>dp
l Recommended by Google
l Supports only Android 3.2+
layout/
main.xml
Handsets Tablet (‘’7) Tablet (‘’10)
layout-sw600dp/
main.xml
layout-sw720dp/
main.xml

31. 27
[UI]3rd Approach
Combination of 1st and 2nd
l Supports Android 1.6
l Supports many devices (compared to 1st or 2nd)
l Any Problem?
l res/layout-sw600dp/main.xml <- 3.2+ tablets
l res/layout-xlarge/main.xml <- 3.0/3.1 tablets
l res/layout/main.xml <- The others (Handsets)

32. 28
[UI]3rd Approach
It looks good but…
l res/layout-sw600dp/main.xml <- 3.2+ tablets
l res/layout-xlarge/main.xml <- 3.0/3.1 tablets
l res/layout/main.xml <- The others (Handsets)
• Needs to put the same file for tablets.
(Maintenance headache…)

33. 29
[UI]3rd Approach
It looks good but…
if ([Size is xlarge] or [width & height is at least 600dp])
// codes for tablets
}else{
// codes for others
}
• Complicated Java codes
(Development is complicated…)

34. 30
The better Approach

35. 31
[UI]4th Approach
Based on 3rd , plus some tips
l main_1pane.xml <- Handsets
l main_2panes.xml <- Tablets
layout
Put minimum requirement
layout files

36. 32
[UI]4th Approach
l main_1pane.xml
l main_2panes.xml
layout
l layout_main.xml
values
l layout_main.xml
values-sw600dp
l layout_main.xml
values-xlarge
// for Tablets
<resources>
<item name "main_layout" type="layout">
@layout/main_2panes
</item>
<bool name="has2panes">
true
</bool>
</resources>

37. 33
[UI]4th Approach
// for Tablets
<resources>
<item name "main_layout" type="layout">
@layout/main_2panes
</item>
<bool name="has2panes">
true
</bool>
</resources>
boolean hasTwoPanes =getResources().
getBoolean(R.bool.has2panes);
if (hasTwoPanes)
…
• Simple Java codes

38. 34
Another Approach

39. 35
[UI]Flexible Layout
• Same Layout
for Handsets & Tablets
Handsets Tablets
No-Using Fragment

40. 36
Additional Tips

41. <resources>
<dimen name="titleSize">24sp</dimen>
</resources>
<resources>
<dimen name="titleSize">12sp</dimen>
</resources>
37
[UI]Customize font size for different screen
• Applying appropriate font size
Handsets Tablet (‘’7)
Hello
Hello
android:textSize=”@dimen/titleSize”
Layout XML
values/
dimens.xml
values-sw600dp/
dimens.xml

42. 38
2.Using APIs?
[Some Points]
Android
2.x
Android
3.x
Android
4.x

43. 39
[API]Fragment
2.x 3.x 4.x
Without
Support Library
With
Support Library
Using Support Library?

44. 40
[API]Fragment
Comparing Using with No-Using
With
Support Library
Without
Support Library
Class
•android.support.v4.Fragment
•android.support.v4.FragmentActivity
…
•android.app.Fragment
•android.app.Activity
…
Method
•getSupportFragmentManager()
(FragmentActivity)
…
•getFragmentManager()
(Activity)
…

45. 41
[API]Options Menu vs Action Bar
Action Bar is good…
2.x 3.x 4.x
Options Menu
Action Bar
2.x 3.x
4.x

46. 42
[API]Supporting Daydream
Daydream is attractive, but 4.2 API
Your App
• 4.2+ devices can run Daydream
Older devices can run normally
except Daydream
XXClass
extends
DreamService
Android
Manifest.xml
add
modify

47. 43
[API]Multi-Versioning
Development?, Management?, APK Size?
Single APK Multiple APK
In my App:
Developed by Single APK
2.x
3.x
4.x
2.x
3.x
4.x

48. 44
[API]Multi-Versioning
How to use the newest API on Single APK
Well known approachReflection
One of design patterns
•SuppressLint("NewApi")
•@TargetApi(n)
Configuring Lint
Lazy Loading

49. 45
[API]Multi-Versioning
Code Examples of “Configuring Lint”
@SuppressLint("NewApi")
private void setActionBarStyle() {
if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.HONEYCOMB) {
ActionBar actionBar = this.getActionBar();
actionBar.setDisplayHomeAsUpEnabled(true);
}else{
...
}
}
@TargetApi(11)
private void setActionBarStyle() {
if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.HONEYCOMB) {
ActionBar actionBar = this.getActionBar();
actionBar.setDisplayHomeAsUpEnabled(true);
}else{
...
}
}
Almost Compatible

50. 46
[API]Multi-Versioning
Code Examples of “Lazy loading”
public
abstract
class
NotificationUtilAbstract
{
public
static
NotificationUtilAbstract
newInstance()
{
NotificationUtilAbstract
instance
=
null;
if
(Integer.parseInt(Build.VERSION.SDK)>=
16)
{
instance
=
new
NotificationUtilJB();
}
else
{
instance
=
new
NotificationUtilDefault();
}
return
instance;
}
public
abstract
void
showCaller;
}
1st step

51. 47
[API]Multi-Versioning
public
class
NotificationUtilJB
extends
NotificationUtilAbstract{
@Override
public
void
showCaller(){
//
Code
by
Jelly
Bean
(API
16)
}
}
public
class
NotificationUtilDefault
extends
NotificationUtilAbstract{
@Override
public
void
showCaller(){
//
Code
by
Old
API
}
}
Compatible
2nd step

52. 48
[API]Multi-Versioning
How to use the newest API on Single APK
Well known approachReflection
In my App:
Compatibility with Lazy loading & Configuring Lint
One of design patterns
•SuppressLint("NewApi")
•@TargetApi(11)
Configuring Lint
Lazy Loading

53. 49
Appendix
1. Use “wrap_content”/“match_parent”,”sp”/”dp”
2. Supply alternative drawables / Use 9-patch
3. Using or No-Using Fragment
4. Use “Dimension (dimens.xml)”
5. Consider either “1 apk” or “multiple apk”

54. 50
References
•Supporting Tablets and Handsets
http://developer.android.com/guide/practices/tablets-and-handsets.html
•Supporting Multiple Screens
http://developer.android.com/guide/practices/screens_support.html
•Supporting Different Screen Sizes
http://developer.android.com/training/multiscreen/screensizes.html
Android Developers Site

55. Thank you!
•Facebook:http://fb.com/kanbara.kenichi
•Google+:+Kenichi Kambara
•LinkedIn:http://www.linkedin.com/in/korodroid
•Twitter:@korodroid

56. 52
Appendix.
Android Fundamentals

57. 53
Activity?
Handset Tablet
Activity A Activity B Activity A

58. 54
Fragment?
Handset Tablet
Activity A Activity B Activity A
FragmentYFragment X Fragment X FragmentY

59. 55
Menu?
Options Menu
(2.x)
Action Bar
(3.0+)
Old Sekai Phone Screenshots