android - Should we expect the app in holo design or material design when using AppCompat -
i have app runs on android 2.3 , above.
recently, i'm in process of migrating sherlockactionbar, appcompat, following guideline what common issues when migrating actionbarsherlock actionbarcompat?
this had done far.
upgrade sdk version
change sdk from
<uses-sdk android:minsdkversion="10" android:targetsdkversion="21" />
to
<uses-sdk android:minsdkversion="10" android:targetsdkversion="22" />
theme upgrade
change theme from
theme.sherlock.light.darkactionbar
to
theme.appcompat.light.darkactionbar
code update
following code change guideline what common issues when migrating actionbarsherlock actionbarcompat?.
note, i'm still stick actionbar
instead of toolbar
. eventually, shall move code toolbar
. since migration huge project. rather done bit bit.
my expectation that
- app runs on android 2.3 till android 4, should have old school holo design. expect app same, 1 built using sherlockactionbar.
- app runs on android 5+, have new material design.
however, here's how app before & after migration, 2.3 app.
before migration
after migration
it seems after migration, can observe that
- action bar height higher.
- the dialog box ok cancel buttons, had changed 3d material flat.
i wondering, should correct expectation on old app (app runs on 2.3 till 4+), when built against appcompat, latest sdk 22 target? should material app, or holo app?
from support library features section appcompat:
this library adds support action bar user interface design pattern. library includes support material design user interface implementations.
so seeing expected behavior- appcompat designed bring actionbar , material devices api 7 , up.
prior release of version 21 of appcompat alongside android lollipop (api 21), appcompat did indeed provide actionbar holo theming. however, never styled other components, ever actionbar itself.
Comments
Post a Comment