The following answer is for the situation of downward unification to API Level 9:
I can only tell you that Android & Support cannot unify the styles. If you don’t believe me, you can check out Platform-Source and Platform-XML.
When implementing DatePickerDialog, each version basically uses some new APIs of the corresponding version, and the most important thing is that the specific implementation methods are different, which is destined to be impossible to unify. For example: the new version adds a new package: android.icu.*, all about time and date localization processing.
If you must unify, then rewrite DatePicker yourself. The workload is not small anyway. Otherwise, go to github to find the wheel.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
The following answer is for the situation of downward unification to API Level 9:
When implementing DatePickerDialog, each version basically uses some new APIs of the corresponding version, and the most important thing is that the specific implementation methods are different, which is destined to be impossible to unify. For example: the new version adds a new package:
android.icu.*, all about time and date localization processing.If you must unify, then rewrite DatePicker yourself. The workload is not small anyway. Otherwise, go to github to find the wheel.