Then documents and examples for content-based Android applications are currently being added, some more.
I have read all the documents till today, but the more general question I have heard from many people:
- Is 5.0 The application given below is Holo-istic Are the styles that are analogous, and use 5.0 material?
or
- Should the AppCompat use it to create as much system content as possible, and if so, 5.0 and above What's the negative impact on the version of the device?
My OCD developer will probably be the purest form of content in mind, though with Toolbar and other key factors it seems that to use AppCompat and modify the entire 4.0 application more understanding.
P>
Whether the application uses AppCompat as much as possible system content Should do it, and if so, what is the negative impact on the devices 5.0 and above?
You can use AppCompat while supporting pure content on Lollipop through alternate resources, so you do not really have to support one or the other. For developing the App Complate, so many To spend time Google has spent so much time that Dave can embrace the material design and still support heritage equipment.
My OCD developer brain will probably be the purest form of content as possible
This is actually a bit dangerous for example, if you have 5.0 Previously you want to use ripples / other animation on the device, which does not have a rendertread, it can affect performance on the device without a dedicated animation thread.
It really comes down, will I be able to give my users the same wonderful experience using app compettes because I will use native themes. Google has made an extraordinary job with AppCompat-v21 and other support libraries to enable content-ask design on pre-5.0 devices. So the answer is yes, use AppCompat to give your users an integrated, stable experience contained in content design.
Comments
Post a Comment